Back to Seed Clases

GObject


Classes

Interfaces

Structs

Unions

Enums

Interface GObject.TypePlugin

Import line: GObject = imports.gi.GObject;
GIR File: GObject-2.0.gir
C documentation: GTypePlugin
Interface : TypePlugin
Implementations: GObject.TypeModule
The GObject type system supports dynamic loading of types. The
GTypePlugin interface is used to handle the lifecycle of
dynamically loaded types. It goes as follows:


The type is initially introduced (usually upon loading the module
the first time, or by your main application that knows what modules
introduces what types), like this:
|[
new_type_id = g_type_register_dynamic (parent_type_id,
"TypeName",
new_type_plugin,
type_flags);
]|
where new_type_plugin is an implementation of the
GTypePlugin interface.


The type's implementation is referenced, e.g. through
g_type_class_ref() or through g_type_create_instance() (this is
being called by g_object_new()) or through one of the above done on
a type derived from new_type_id.


This causes the type system to load the type's implementation by calling
g_type_plugin_use() and g_type_plugin_complete_type_info() on
new_type_plugin.


At some point the type's implementation isn't required anymore, e.g. after
g_type_class_unref() or g_type_free_instance() (called when the reference
count of an instance drops to zero).


This causes the type system to throw away the information retrieved from
g_type_plugin_complete_type_info() and then it calls
g_type_plugin_unuse() on new_type_plugin.


Things may repeat from the second step.


So basically, you need to implement a GTypePlugin type that
carries a use_count, once use_count goes from zero to one, you need
to load the implementation to successfully handle the upcoming
g_type_plugin_complete_type_info() call. Later, maybe after
succeeding use/unuse calls, once use_count drops to zero, you can
unload the implementation again. The type system makes sure to call
g_type_plugin_use() and g_type_plugin_complete_type_info() again
when the type is needed again.
GTypeModule is an implementation of GTypePlugin that already
implements most of this except for the actual module loading and
unloading. It even handles multiple registered types per module.
Properties
None
Methods / Constructors
Method / Constructor Defined By
Events
None
Used by These Methods / Signals / Properties
Class / Namespace Method / Signal / Properties
GObject
Method
GObject.type_add_interface_dynamic (Number instance_type, Number interface_type, TypePlugin plugin) : none
Adds the dynamic interface_type to instantiable_type.
GObject
Method
GObject.type_get_plugin (Number type) : GObject.TypePlugin
Returns the GTypePlugin structure for type or
NULL if type does not have a GTypePlugin structure.
GObject
Method
GObject.type_interface_get_plugin (Number instance_type, Number interface_type) : GObject.TypePlugin
Returns the GTypePlugin structure for the dynamic interface
have a GTypePlugin structure.
GObject
Method
GObject.type_register_dynamic (Number parent_type, String type_name, TypePlugin plugin, TypeFlags flags) : Number
Registers type_name as the name of a new dynamic type derived from
GTypePlugin structure pointed to by plugin to manage the type and its
instances (if not abstract).
Documentation generated by Introspection Doc Generator Loosely Based on JsDoc Toolkit on Sat Apr 16 2011 17:10:42 GMT+0800 (HKT)