Good news...
I just succeed to make a PPA for Soren's dbus branch, too.
Now I have successfully install it on my ubuntu qemu and works.
Here is the Ubuntu Links:
This binary contains both Soren's and my work of dbus implementation.
So, there will be two dbus interface after launching inkscape
( can use some dbus debugger like d-feet )
I put my script and patch here:
:-)
sincerely, Mat.
On Fri, Aug 21, 2009 at 12:31 PM, Mat<matlinuxer2@...400...> wrote:
On Fri, Aug 21, 2009 at 12:59 AM, Glimmer
Labs<glimmer07@...400...> wrote:
> That is very odd. I could have sworn I added pytester.py and even
> made a few revisions...
>
> Anyway I svn added it and it didn't say it was already under version
> control, so it should be there now.
>
> Sorry for the confusion.
>
> PPA:
>
> I never got a PPA working because I was busy getting the wrapper
> library up and running. Any help is appreciated and if you have a
> specific thing you'd like to work on I can get you pointed in the
> right direction. Otherwise the Notes.txt file is a good place to get
> started as it gives an overview of the system.
I got it.
I can help to do PPA :-)
I succeed once for my branch. I am going to help yours works, too.
Some links about my current works,
https://launchpad.net/~matlinuxer2/+archive/ppa
( on merging with gsoc's dbus branch, sometimes is broken... )
http://code.google.com/p/inkboardng/source/browse/trunk/scripts/ubuntu/pp...
sincerely, Mat.
>
> On Tue, Aug 18, 2009 at 2:24 PM, Kent Tenney<ktenney@...400...> wrote:
>> On Sat, Aug 15, 2009 at 2:03 PM, Glimmer Labs<glimmer07@...400...> wrote:
>>> On Fri, Aug 14, 2009 at 9:36 AM, Kent Tenney<ktenney@...400...> wrote:
>>>> I see mention of pytester.py in
src/inkscape/src/extension/dbus/Notes.txt
>>>> but haven't found the file.
>>>>
>>>> Thanks,
>>>> Kent
>>>
>>> Update to the latest SVN and it should be in the dbus folder.
>>
>> I'm looking at r22127 of
>>
https://inkscape.svn.sourceforge.net/svnroot/inkscape/inkscape/branches/g...
>>
>> I don't see it.
>>
>> Thanks,
>> Kent
>>
>>>
>>> I didn't add it at first because it was just for testing, but now I
>>> realize it serves as a fairly good example script as well.
>>>
>>> The reason it creates two documents is to make sure functions work
>>> even if they are called on an inactive document. This can be changed
>>> if you don't want to be opening lots of extra windows. (or use
>>> document_0 if you don't want to open any extra windows.)
>>>
>>
>