- was the dbus code merged?

- if not, where is dbus capable code?

> Just as an FYI, all of the Inkscape branches that Launchpad knows about > will be on this page: > > https://code.launchpad.net/inkscape > > We should clean that listing up a little, as I believe some have been > merged (and we should change their state to reflect that). But, in > general, if they're > 4 weeks old, no one has touched them since the SVN > migration. I have gone in and set all the release branches to mature. And the few branches I'm sure have been merged have been marked as such. Unless I hear otherwise I'm going to mark projects untouched in a year as abandoned tomorrow or the next day. If you have merged a branch please mark in as merged, or at least let me know soon so I can mark it appropriately.

On Tue, 2009-12-29 at 13:45 -0600, Kent Tenney wrote: > - was the dbus code merged? No.  I'm trying to do a few clean ups to the autotools portions of it before doing that.  I'm hoping to find some time this week to do that (as I don't have work, but those kids are so much dang fun ;) ) > - if not, where is dbus capable code?  https://code.launchpad.net/~inkscape.dev/inkscape/gsoc2009_api Just as an FYI, all of the Inkscape branches that Launchpad knows about will be on this page:  https://code.launchpad.net/inkscape We should clean that listing up a little, as I believe some have been merged (and we should change their state to reflect that).  But, in general, if they're > 4 weeks old, no one has touched them since the SVN migration.                --Ted

On Tue, 21 Sep 2010 08:32:08 -0500 Kent Tenney <ktenney@...400...> wrote: > I've just built trunk > bzr+ssh://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/ > > I see dbus in src/extensions/dbus > > I'm unable to connect to Inkscape via Python->dbus > per doc via src/extensions/dbus/builddocs.sh > > what am I missing? Hi Kent, I was trying to get that going too.  With all reasonable seeming dbus-dev packages and ./configure --enable-dbusapi I was not able to get "Enable DBUS:  yes" on the summary printed at the end of the ./configure output.

No sign of inkscape in bus.list_activatable_names() Cheers -Terry > =============================================================== > I get the following: > dbus.exceptions.DBusException: > org.freedesktop.DBus.Error.ServiceUnknown: The name org.inkscape was > not provided by any .service files > > when running: > =============================================================== > import dbus > > #get the session bus. > bus = dbus.SessionBus() > > #get the object for the application. > inkapp = bus.get_object('org.inkscape', >                        '/org/inkscape/application') > > #request a new desktop. > desk2 = inkapp.desktop_new(dbus_interface='org.inkscape.application') > > #get the object for that desktop. > inkdoc1 = bus.get_object('org.inkscape', desk2) > =============================================================== > > > On Tue, Dec 29, 2009 at 4:35 PM, Ted Gould <ted@...11...> wrote: > > On Tue, 2009-12-29 at 13:45 -0600, Kent Tenney wrote: > >> - was the dbus code merged? > > > > No.  I'm trying to do a few clean ups to the autotools portions of it > > before doing that.  I'm hoping to find some time this week to do that > > (as I don't have work, but those kids are so much dang fun ;) ) > > > >> - if not, where is dbus capable code? > > > >  https://code.launchpad.net/~inkscape.dev/inkscape/gsoc2009_api > > > > Just as an FYI, all of the Inkscape branches that Launchpad knows about > > will be on this page: > > > >  https://code.launchpad.net/inkscape > > > > We should clean that listing up a little, as I believe some have been > > merged (and we should change their state to reflect that).  But, in > > general, if they're > 4 weeks old, no one has touched them since the SVN > > migration. > > > >                --Ted > > > > > > ------------------------------------------------------------------------------ > Start uncovering the many advantages of virtual appliances > and start using them to simplify application deployment and > accelerate your shift to cloud computing. > http://p.sf.net/sfu/novell-sfdev2dev > _______________________________________________ > Inkscape-devel mailing list > Inkscape-devel(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/inkscape-devel > ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ Inkscape-devel mailing list Inkscape-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel

I'm getting no mention of dbus in the ./configure report. I attributed this to it's location in the src tree, under extension/ That signaled to me that it's not in core, but needs some extension magic to bring it to life.

2010/9/21 Kent Tenney <ktenney@...400...>: > I'm getting no mention of dbus in the ./configure report. > > I attributed this to it's location in the src tree, under extension/ > > That signaled to me that it's not in core, but needs some extension > magic to bring it to life. The DBus "extension" is very much in the core. The code is in the wrong directory, because DBus support is not an extension. The configuration problem should be fixed in revision 9773. You need the libdbus-glib-1-dev package (in Debian).