On Mon, 2008-09-08 at 23:26 +0200, ext Tim Teulings wrote: > Hello! > > >> The problem is, that I'm not an Gtk application. So there are IMHO two > >> possibilities: > > > > I assume you mean you don't use the Glib main loop. Gtk is not needed > > for D-Bus communication. > > Correct. That was inprecise wording > > >> * Generate a separate thread that uses a glib main event loop and try to > >> get libosso and libconic to run using this event loop - communication > >> with the rest of my application using thread synchronisations. Would > >> that work? > > > Maybe that would work, but it's certainly a horrible hack. > > Why? Glib allows to create additional main event loops, libosso > explicitely allows to set an event loop. If this is a hack, why this APIs?
I meant the multi-threading, but if you like it... > > I think the simplest solution is to use Glib main loop in your program. > > Otherwise you would need to hack the libraries to work with your non- > > Glib main loop (which is not impossible, but quite a lot of work). Glib > > main loop is like the GPL, it contaminates your program :) > > I don't want to. I'm having my own GUI library, why should I use > GlibMain loop? Glib is not a GUI library. It is used in many non-UI programs. > And finally, if I would be writing an QT application, would you force me > to use GlibMainLoop, too ;-)? What is the masterplan for future OS > versions that will integrate QT better? You can use Glib main loop with QT, too. I'm sure there is some QT documentation about it. > That does not sound reasonable. There must/should be another way. IMHO > the dbus is a perfect platform and language neutral way to communicate > between processes, why should I forced to use a wrapper library that > restricts me in my choice of tools? Why do not publish the dbus > interfaces, and instead write wrapper librarys instead (of course it is > OK to have both. I have no problem with having additional efforts If I > do not use Gtk). Usually the reason is that the interface is not meant for public use and can change anytime. (You need change management for public APIs but not for private ones.) > What about testing any of the dbus interfaces under scratchbox. Is there > a way? Libosso works, but I don't know about others. -Kimmo > _______________________________________________ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
