Hi all,
A week ago, I had post a message about adding a dock item with Python script in Inkscape window. Actually, I had embedded Python script engine to Inkscape successfully in our Inkscape branch (pybind). It works with low latency compared to the extension interface provided by Inkscape now. It is also more powerful than what the extension interface is now. We make it for another project. With this Inkscape branch (pybind), we can add a dock item, or any widget around canvas. We even create a timeline GTK widget with Python and pack it just under the SVG canvas. With this branch, some functions, of Inkscape, that is not CPU-intensive can be implemented with Python script. So, I want to know if it is possible to merge our Inkscape branch (pybind) back to the trunk.
On Nov 21, 2010, at 9:10 AM, Thinker K.F. Li wrote:
Hi all,
A week ago, I had post a message about adding a dock item with Python script in Inkscape window. Actually, I had embedded Python script engine to Inkscape successfully in our Inkscape branch (pybind). It works with low latency compared to the extension interface provided by Inkscape now. It is also more powerful than what the extension interface is now. We make it for another project. With this Inkscape branch (pybind), we can add a dock item, or any widget around canvas. We even create a timeline GTK widget with Python and pack it just under the SVG canvas. With this branch, some functions, of Inkscape, that is not CPU-intensive can be implemented with Python script. So, I want to know if it is possible to merge our Inkscape branch (pybind) back to the trunk.
There are a few problems with this approach. For anyone who's worked with Gtk plug or the tray icon API these become appearant. We also have had the scribus team warn us off of this approach, as that is what they implemented (in general) and have many problems with.
I'll list out a few more details on this in the wiki, so that the reoccurring discussion can be captured.
Give us a link to the page when you've done it, thanks!
Be disappointing to turn away something that works just because of potential problems (though I can understand there might be a need, depending on the issues). I've been really looking forward to some more interactive python stuff. The DBus API was a tantalizing start.
Anyway, perhaps better save that discussion for after we've seen the issues on the wiki.
- Bryan
On Mon, Nov 22, 2010 at 08:19, Jon Cruz <jon@...18...> wrote:
On Nov 21, 2010, at 9:10 AM, Thinker K.F. Li wrote:
Hi all,
A week ago, I had post a message about adding a dock item with Python script in Inkscape window. Actually, I had embedded Python script engine to Inkscape successfully in our Inkscape branch (pybind). It works with low latency compared to the extension interface provided by Inkscape now. It is also more powerful than what the extension interface is now. We make it for another project. With this Inkscape branch (pybind), we can add a dock item, or any widget around canvas. We even create a timeline GTK widget with Python and pack it just under the SVG canvas. With this branch, some functions, of Inkscape, that is not CPU-intensive can be implemented with Python script. So, I want to know if it is possible to merge our Inkscape branch (pybind) back to the trunk.
There are a few problems with this approach. For anyone who's worked with Gtk plug or the tray icon API these become appearant. We also have had the scribus team warn us off of this approach, as that is what they implemented (in general) and have many problems with.
I'll list out a few more details on this in the wiki, so that the reoccurring discussion can be captured.
Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today http://p.sf.net/sfu/msIE9-sfdev2dev _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
On Nov 21, 2010, at 11:26 AM, Bryan Hoyt | Brush Technology wrote:
Be disappointing to turn away something that works just because of potential problems (though I can understand there might be a need, depending on the issues). I've been really looking forward to some more interactive python stuff. The DBus API was a tantalizing start.
Yes, the DBus API has some interesting potential. However, it was not actually designed for this UI purpose, and does need some major rework to be able to support it. The student adding it in as a Google Summer of Code project had to make certain choices, and focused on getting some base DBus functionality solid and did not have time to look at the higher-level calls that might be needed for certain things in the long run.
What we need to focus on is getting the replacement for the extensions API done. If we have people working on the extension side of things, this can be done much more quickly. The key here, I think, is to focus on getting good interactive python stuff going... but in a manner so that the hooks python use can be used by any other approach to scripting (C++, other scripting, D-Bus, etc). Then all can benefit from that single implementation instead of needing to do a one-off development effort for Python, a separate one-off development effort for Perl, etc.
Hi Jon, hi Thinker,
What is the difference in the python embedding way that Thinker done and the used by Blender? Blender is a good example about embedded python to give power to the user.
Must we to work on the perfect infrastructure to all languages? We allow extensions on any language today, but we deal that all extensions must be done in python, and we only provide the python interpreter on windows package. I also only learn python to contribute directly to Inkscape, because my previous extensions was in Bash, Perl and Ruby.
Scribus had some problems embedding python. Knowing the possible problems don't we can escape this?
A interesting solution may be: We work internally only with python (like Blender) and let the current extension model to any other language. We already like Python more then any other.
...
Some day we will must to support javascript inside inkscape... in that day will we embed a javascript interpreter like Thinker did or in other way?
...
Thinker i must to pay you a beer! :-) Your contribution is opening a new way for great features on Inkscape!
Aurium
On Sun, Nov 21, 2010 at 4:44 PM, Jon Cruz <jon@...18...> wrote:
On Nov 21, 2010, at 11:26 AM, Bryan Hoyt | Brush Technology wrote:
Be disappointing to turn away something that works just because of potential problems (though I can understand there might be a need, depending on the issues). I've been really looking forward to some more interactive python stuff. The DBus API was a tantalizing start.
Yes, the DBus API has some interesting potential. However, it was not actually designed for this UI purpose, and does need some major rework to be able to support it. The student adding it in as a Google Summer of Code project had to make certain choices, and focused on getting some base DBus functionality solid and did not have time to look at the higher-level calls that might be needed for certain things in the long run.
What we need to focus on is getting the replacement for the extensions API done. If we have people working on the extension side of things, this can be done much more quickly. The key here, I think, is to focus on getting good interactive python stuff going... but in a manner so that the hooks python use can be used by any other approach to scripting (C++, other scripting, D-Bus, etc). Then all can benefit from that single implementation instead of needing to do a one-off development effort for Python, a separate one-off development effort for Perl, etc.
Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today http://p.sf.net/sfu/msIE9-sfdev2dev _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
From: Thinker K.F. Li <thinker@...2485...> Subject: Embed Python script engine Date: Mon, 22 Nov 2010 01:10:49 +0800 (CST)
Hi all,
A week ago, I had post a message about adding a dock item with Python script in Inkscape window. Actually, I had embedded Python script engine to Inkscape successfully in our Inkscape branch (pybind). It works with low latency compared to the extension interface provided by Inkscape now. It is also more powerful than what the extension interface is now. We make it for another project. With this Inkscape branch (pybind), we can add a dock item, or any widget around canvas. We even create a timeline GTK widget with Python and pack it just under the SVG canvas. With this branch, some functions, of Inkscape, that is not CPU-intensive can be implemented with Python script. So, I want to know if it is possible to merge our Inkscape branch (pybind) back to the trunk.
I forget to give the URL of the branch,
From: Thinker K.F. Li <thinker@...2485...> Subject: Re: Embed Python script engine Date: Mon, 22 Nov 2010 09:03:48 +0800 (CST)
From: Thinker K.F. Li <thinker@...2485...> Subject: Embed Python script engine Date: Mon, 22 Nov 2010 01:10:49 +0800 (CST)
Hi all,
A week ago, I had post a message about adding a dock item with Python script in Inkscape window. Actually, I had embedded Python script engine to Inkscape successfully in our Inkscape branch (pybind). It works with low latency compared to the extension interface provided by Inkscape now. It is also more powerful than what the extension interface is now. We make it for another project. With this Inkscape branch (pybind), we can add a dock item, or any widget around canvas. We even create a timeline GTK widget with Python and pack it just under the SVG canvas. With this branch, some functions, of Inkscape, that is not CPU-intensive can be implemented with Python script. So, I want to know if it is possible to merge our Inkscape branch (pybind) back to the trunk.
I forget to give the URL of the branch,
http://www.youtube.com/watch?v=bwzBQdruZJo
This is the video to show our latest status. The video was made by my partner.
participants (4)
-
Aurélio A. Heckert -
Bryan Hoyt | Brush Technology -
Jon Cruz -
Thinker K.F. Li