Heavy operations with Inkscape

Hi list,
I'm part of the team that's building up Libre Graphics Magazine (http://libregraphicsmag.com). We're using Inkscape to create the cover, as well as some illustrations inside.
There's an issue that has been bothering me for a while. For some purposes, we need to operate on a huge number of paths -- e.g., combining
2000 paths or applying path operations (union, intersect, etc) to a very
large number of paths. Inkscape, of course, takes quite some time to execute these, and there's no way that I've found to see the progress of the operation.
Now, I can understand that it would be a big feature request to have progress feedback on heavy operations like these. However, something that I would *love* to have is some kind of feedback when the operation is completed, so that i can work on other programs while Inkscape does its thing.
Right now, I'm keeping a terminal window with 'top' running, so I can keep tabs on Inkscape's CPU usage -- when it drops, the operation's probably done. However, I can imagine there would be an easier and more straightforward way to know when Inkscape's done with crunching paths.
Do any of you fellow Inkscape users have any tips or hacks that can help with this issue?
Also, should i pester inkscape-devel or file a feature request to have notifications (bell sound or notify popup) when a long operation is finished?
Cheers!

On Nov 5, 2010, at 4:52 AM, ricardo lafuente wrote:
Right now, I'm keeping a terminal window with 'top' running, so I can keep tabs on Inkscape's CPU usage -- when it drops, the operation's probably done. However, I can imagine there would be an easier and more straightforward way to know when Inkscape's done with crunching paths.
Do any of you fellow Inkscape users have any tips or hacks that can help with this issue?
Also, should i pester inkscape-devel or file a feature request to have notifications (bell sound or notify popup) when a long operation is finished?
Be sure that there is a Launchpad bug entered to track this. That is the first step to ensure that it will not get forgotten or overlooked.

On 6/11/10 02:41, Jon Cruz wrote:
On Nov 5, 2010, at 4:52 AM, ricardo lafuente wrote:
Right now, I'm keeping a terminal window with 'top' running, so I can keep tabs on Inkscape's CPU usage -- when it drops, the operation's probably done. However, I can imagine there would be an easier and more straightforward way to know when Inkscape's done with crunching paths.
Do any of you fellow Inkscape users have any tips or hacks that can help with this issue?
Also, should i pester inkscape-devel or file a feature request to have notifications (bell sound or notify popup) when a long operation is finished?
Be sure that there is a Launchpad bug entered to track this. That is the first step to ensure that it will not get forgotten or overlooked.
related:
Bug #171435 “Progress bar for time-intensive operations” https://bugs.launchpad.net/inkscape/+bug/171435
and the blueprint "Time-intensive operations management" https://blueprints.launchpad.net/inkscape/+spec/intensive-operations-management
hth, ~suv
participants (3)
-
Jon Cruz
-
ricardo lafuente
-
~suv