diff options
author | Matthew Barnes <mbarnes@redhat.com> | 2012-12-08 05:30:18 +0800 |
---|---|---|
committer | Matthew Barnes <mbarnes@redhat.com> | 2012-12-08 06:40:28 +0800 |
commit | bf30024dd7973006bf99d0ae509a7f0022368a41 (patch) | |
tree | d6ce797885082ba6ee3878db5054bdbaa6d691f4 /em-format/Makefile.am | |
parent | 7c656866a2a3cf9110a8db5d57a156638c8c3fe0 (diff) | |
download | gsoc2013-evolution-bf30024dd7973006bf99d0ae509a7f0022368a41.tar.gz gsoc2013-evolution-bf30024dd7973006bf99d0ae509a7f0022368a41.tar.zst gsoc2013-evolution-bf30024dd7973006bf99d0ae509a7f0022368a41.zip |
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().
Diffstat (limited to 'em-format/Makefile.am')
-rw-r--r-- | em-format/Makefile.am | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/em-format/Makefile.am b/em-format/Makefile.am index 6e45b0f6f1..164f3004b5 100644 --- a/em-format/Makefile.am +++ b/em-format/Makefile.am @@ -40,8 +40,6 @@ libemformat_la_SOURCES = \ $(emformatinclude_HEADERS) \ e-mail-extension-registry.c \ e-mail-inline-filter.c \ - e-mail-format-extensions.c \ - e-mail-format-extensions.h \ e-mail-formatter.c \ e-mail-formatter-print.c \ e-mail-formatter-quote.c \ |