On Thu, 2009-07-16 at 09:59 -0700, Glimmer Labs wrote:
On Tue, Jul 14, 2009 at 7:50 PM, Bob Jamison<ishmalius@...400...> wrote:
On 7/14/2009 9:34 PM, Ted Gould wrote: I was bouncing my poor ideas off of Peter (a forgiving soul, to be sure), and my thought on the subject would be to have a launcher app that would:
- Sense if a Dbus framework is already running
- If not, start a user-level dbus daemon
- Run Inkscape, use your scripting and extensions
- When closing Inkscape, if you started your own daemon, close it, too.
This could be done but I don't know how often it would be used. Most systems with DBus installed (i.e. any modern Gnome) will have a session daemon running for each session. It could be useful for people who install DBus just to try out this API, though, and I'd certainly want to support those users, so I'll check it out.
I think that he is meaning only for Windows. At least I hope so. Please Bob correct me if I'm wrong there.
Also I'll have to make sure that a user level DBus daemon could provide the default session bus. Otherwise users would have to look for the interface on two separate buses (The session bus, or our own private bus if that's not running.)
I think the only application for having a private bus is for testing. There has been some discussion for security issues, but I think that it's not really supported.
My plan was to have it be Unix only at first and add windows support when windows DBus has been hammered out a bit more. It may always take a little effort to get DBus running on Windows, so I doubt that this API will ever be the default on that platform, but it should work in native Windows eventually.
I think that there's no reason though to not help people who want to get it on Windows :) Though, we haven't made it a requirement of the GSoC project because it was a little nebulous. I'm not sure how other windows apps would find the DBus that's running. Probably the best thing is to make it so that if the code can't connect to a bus, it just silently moves on.
--Ted