On Fri, 2005-02-18 at 14:31 -0500, Havoc Pennington wrote:
>
> I propose that we move DBusGObjectInfo and code that uses it entirely
> inside the generated code, rather than having it in our headers/library.
>
> When glib has built-in introspection, we'll change dbus-binding-tool to
> use that if possible, and this interim approach will magically vanish.
>
I think this doesn't really work:
- when we have native introspection, we still only want to export stuff
selectively.
So unless we add a "remote proxy" flag to glib native introspection
(probably a good idea) we would still need our own introspection
stuff
(maybe have "annotation" support in glib introspection?)
- the code related to GObjectInfo is really in register_g_object
conceptually, so can't be moved out of libdbus-glib
What we can do instead when GObject is introspectable is change our
DBusGObjectInfo to be much smaller and just chain to glib.
Havoc
|
