gsoc2013-evolution - Google Summer of Code 2013 - GNOME

	Commit message (Collapse)	Author	Age	Files	Lines
*	The EExtension framework is now in libebackend.	Matthew Barnes	2011-09-26	1	-72/+0
\| \| \| \| \| \| \| \|	The EModule, EExtensible and EExtension classes as well as the e_type_traverse() function have been moved to Evolution-Data-Server's libebackend library to replace e-data-server-module.c. Now Evolution-Data-Server modules use the same framework as Evolution.
*	Including <glib-object.h> directly is rarely needed.	Matthew Barnes	2011-05-28	1	-1/+0
\|
*	Document EExtensible and EExtension.	Matthew Barnes	2010-03-22	1	-0/+6
\| \| \| \| \| \|	The mechanism here is simple but hard to explain without leaning heavily on object-oriented jargon. Consider this a rough draft. Illustrations would certainly help clarify.
*	Introduce a simple extension system for objects.	Matthew Barnes	2010-03-20	1	-0/+67
	This introduces a simple means of extending Evolution objects. Any GObject subclass wishing to be extensible need only call g_type_add_interface_static (type, E_TYPE_EXTENSIBLE, NULL); when registering its GType, and then at some point during initialization call e_extensible_load_extensions() to load extensions for that subclass. Extensions are implemented by subclassing EExtension, setting the GType being extended in EExtensionClass, and making sure its own GType gets registered at startup. This usually done while loading a GTypeModule. e_extension_get_extensible() provides extensions access to the object being extended.