Teach EMailExtensionRegistry to find extensions.

Now we have the following extension points in the GType hierarchy:

   E_TYPE_MAIL_FORMATTER_EXTENSION
   E_TYPE_MAIL_FORMATTER_PRINT_EXTENSION
   E_TYPE_MAIL_FORMATTER_QUOTE_EXTENSION
   E_TYPE_MAIL_PARSER_EXTENSION

A registry just needs to be given one of these extension points, and it
can use g_type_children() to find and load all registered extensions.

This eliminates e-mail-format-extensions.[ch] as well as the dynamic
loaders I added a few commits back.  Dynamically loaded extensions are
now easier to register, at the cost of internal extensions being a tad
more cumbersome to register.  Fair tradeoff, imo.

This also makes e_mail_extension_registry_add_extension() a private
function used only by e_mail_formatter_extension_registry_load() and
e_mail_parser_extension_registry_load().

1 files changed, 3 insertions, 2 deletions

diff --git a/em-format/e-mail-formatter.c b/em-format/e-mail-formatter.c
index 5ab7f5c2dc..bc671b8072 100644
--- a/em-format/e-mail-formatter.c
+++ b/em-format/e-mail-formatter.c
@@ -528,8 +528,9 @@ e_mail_formatter_base_init (EMailFormatterClass *class)
 	class->extension_registry = g_object_new (
 		E_TYPE_MAIL_FORMATTER_EXTENSION_REGISTRY, NULL);
 
-	e_mail_formatter_internal_extensions_load (
-		E_MAIL_EXTENSION_REGISTRY (class->extension_registry));
+	e_mail_formatter_extension_registry_load (
+		class->extension_registry,
+		E_TYPE_MAIL_FORMATTER_EXTENSION);
 
 	e_extensible_load_extensions (
 		E_EXTENSIBLE (class->extension_registry));