The model of gobject.type_module.TypeModule is a dynamically loaded module which
implements some number of types and interface implementations.
When the module is loaded, it registers its types and interfaces
using gobject.type_module.TypeModule.registerType and
gobject.type_module.TypeModule.addInterface.
As long as any instances of these types and interface implementations
are in use, the module is kept loaded. When the types and interfaces
are gone, the module may be unloaded. If the types and interfaces
become used again, the module will be reloaded. Note that the last
reference cannot be released from within the module code, since that
would lead to the caller's code being unloaded before [gobject.object.ObjectG.unref]
returns to it.
Keeping track of whether the module should be loaded or not is done by
using a use count - it starts at zero, and whenever it is greater than
zero, the module is loaded. The use count is maintained internally by
the type system, but also can be explicitly controlled by
gobject.type_module.TypeModule.use and gobject.type_module.TypeModule.unuse.
Typically, when loading a module for the first type, [gobject.type_module.TypeModule.use]
will be used to load it so that it can initialize its types. At some later
point, when the module no longer needs to be loaded except for the type
implementations it contains, [gobject.type_module.TypeModule.unuse] is called.
gobject.type_module.TypeModule provides a simple implementation of the gobject.type_plugin.TypePlugin interface.
The model of gobject.type_module.TypeModule is a dynamically loaded module which implements some number of types and interface implementations.
When the module is loaded, it registers its types and interfaces using gobject.type_module.TypeModule.registerType and gobject.type_module.TypeModule.addInterface. As long as any instances of these types and interface implementations are in use, the module is kept loaded. When the types and interfaces are gone, the module may be unloaded. If the types and interfaces become used again, the module will be reloaded. Note that the last reference cannot be released from within the module code, since that would lead to the caller's code being unloaded before [gobject.object.ObjectG.unref] returns to it.
Keeping track of whether the module should be loaded or not is done by using a use count - it starts at zero, and whenever it is greater than zero, the module is loaded. The use count is maintained internally by the type system, but also can be explicitly controlled by gobject.type_module.TypeModule.use and gobject.type_module.TypeModule.unuse. Typically, when loading a module for the first type, [gobject.type_module.TypeModule.use] will be used to load it so that it can initialize its types. At some later point, when the module no longer needs to be loaded except for the type implementations it contains, [gobject.type_module.TypeModule.unuse] is called.
gobject.type_module.TypeModule does not actually provide any implementation of module loading and unloading. To create a particular module type you must derive from gobject.type_module.TypeModule and implement the load and unload functions in gobject.type_module_class.TypeModuleClass.