Re: gEDA-dev: DBUS in external hid?

[Igor2 <igor2-at-NOSPAMinno_dot_bme_dot_hu>]

On Sat, 7 Oct 2006, DJ Delorie wrote:

>
>> For those who need it it's mostly transparent, for those who don't
>> need it easy to avoid.
>
>The problem with a dbus hid is that it needs to be able to respond to
>events even when the GUI isn't expecting them.  That usually means the
>GUI needs to somehow poll for those events as part of its event loop.
>Thus, the gui needs to know at least *something* about the way the
>protocol works.
>
>Although, we could add something like Xt's api for listening on
>sockets - you register a file descriptor and a callback with Xt, and
>when there's data to be read on the file descriptor, the callback is
>called.  We could probably hook that into all the guis somehow.
>
>Of course, whether that's useful or not now depends on dbus being able
>to work with that kind of callback.
>

What about adding more general callbacks, not keeping dbus in mind, but
keeping PCB in mind, then use the external dbus hid as the converter
layer between PCB and DBUS? This way DBUS is only one of the solutions,
someone else can write and/or use another lib or home grown code for
similar things. After all this is what makes a software modular :)
 



_______________________________________________
geda-dev mailing list
geda-dev@moria.seul.org
http://www.seul.org/cgi-bin/mailman/listinfo/geda-dev