BonoboXObject provides an easy to use way of writing CORBA servers. It
strongly deprecates BonoboObject ( with which it is compatible ). It
drastically simplifies the issues of epv and vepv construction by
automating these, and automatically instantiates a CORBA_Object on
gtk_type_new. This removes clutter from construction time.
The CORBA methods are associated with a Gtk class in the same
way that standard Gtk+ methods and signals are. We insert the
CORBA generated Entry Point Vector (epv) struct as the first
element of the derived class eg.
The POA_Bonobo_Control__init function is used to construct the CORBA object
and the GTK_STRUCT_OFFSET tells Bonobo where your epv structure is
in the Class data, so it can build your epv for you.
The fini_fn function is not used in ORBit, so it is faster to use NULL here.
After registering the type in the class initialization function, we
must fill out the epv with our entry points, similar to the way we
hook up virtual class functions. It may also be necessary to override
the parent's epv's; this can be done by accessing the epv pointer for
the parent class.
This function is the main entry point for deriving bonobo
server interfaces.
parent_type :
the parent Gtk Type
init_fn :
a POA initialization function
fini_fn :
a POA finialization function or NULL
epv_struct_offset :
the offset into the struct that the epv
commences at, or 0 if we are inheriting a plain Gtk Object
from a BonoboXObject, adding no new CORBA interfaces
This function initializes a type derived from BonoboXObject, such that
when you instantiate a new object of this type with gtk_type_new the
CORBA object will be correctly created and embedded.
type :
The type to initialize
init_fn :
the POA_init function for the CORBA interface or NULL
fini_fn :
NULL or a custom POA free fn.
epv_struct_offset :
the offset in the class structure where the epv is or 0