On Wed, 2006-10-11 at 17:36 -0400, Dan McMahill wrote: > DJ Delorie wrote: > >>If PCB can support LessTif, GTK, and postscript, why can't it support > >>both DBus and XML-PRC? > > > > > > The fundamental problem is that both DBUS and the GUI are > > asynchronous. Thus, when the GUI is waiting for a user event, it > > needs to also watch for data on the DBUS connection, and tell DBUS > > when it happens. > > > > The easy-to-use DBUS wrapper supports Gtk, but not Lesstif. > > I guess it would be good if a motivated individual could see (and maybe > Peter can already answer this) what it might take to just hook dbus into > the lesstif HID via XtAppAddInput().
The problem is that the glib bindings can't be hooked in this manner. This leaves you with the (very) raw C API to libdbus. The stuff we've done can be implemented using libdbus, its just not as neat. Currently, we define the DBUS objects / methods in a DBUS Introspection XML file (yuck indeed), then during configure, a dbus-glue.h file is generated, which defines a lot of the stuff needed for dbus.c to work. We don't hand-write very much dbus code, only the stuff to initialise dbus-glib bindings, and for the methods themselves. I wonder if I can knock up a script, or helper program which autogenerates raw libdbus code based on a similar input XML? Peter C. _______________________________________________ geda-dev mailing list [email protected] http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev
