On Tue, 2013-02-05 at 17:22 +0900, Tristan Van Berkom wrote: > Would it make sense to include some property on the base > ESourceExtension class ? > > For instance, an api such as 'e_source_extension_claim()' could > be introduced and called by the consumer of the given extensions. > > I.e. the file addressbook backend would "claim" the > ESourceBackendSummarySetup extension... clients (those clients > which actually created the backend), would then be able > to read this "claimed" property back after creating the addressbook.
That seems to me like an awfully obscure corner case to justify adding APIs to the base ESourceExtension class. Maybe I don't understand what problem this is trying to solve. Matthew Barnes _______________________________________________ evolution-hackers mailing list [email protected] To change your list options or unsubscribe, visit ... https://mail.gnome.org/mailman/listinfo/evolution-hackers
