6:36 a.m.
On 9/5/07, Diederik van Lierop <mail@...1689...> wrote:
The last few days I've spent on improving the performance of the
object
snapper. It used to take ages (e.g about 6 seconds on my machine) to
move a simple rectangle over a large text box, but I've managed to
reduce this significantly (i.e. < 1 sec.!). This was with both snapping
to paths and snapping to nodes turned on. For this I had to refactor the
object snapper code significantly, so I might have introduced new bugs
or regressions. Please be aware of this and report any suspicious
behavior, so we can have both fast and robust snapping in v0.46!
Thanks, great news! Please add a note about that in the "speed and
interactivity" section of the release notes as well.
Please note that the performance has only increased when using the
selector tool for transforming a number of points, e.g. when dragging a
selection. Using the node tool to drag a single node will not benefit
from this.
I just tried to test this: opened new document, drew a spiral and a
small rect, then opened doc prefs and turned on "snapping of: bbox
corners" and "snapping to objects: snap to paths". But when I drag the
rect it does not snap to the spiral. What am I doing wrong?
Before, for _every_ point in the selection being transformed (using
the
selector tool), Inkscape would search for snapping candidates, build a
list of nodes and paths, and finally call convertWithBackData(). Only
then would it snap this single point and start all over again for the
next point in the selection. Now we only do this collecting and
converting stuff once, store the results, and then snap all points in
the selection (using the stored data). Not having to call
convertWithBackData really helps a lot! I think that in many common
cases this improves the performance dramatically.
Yes, this is approximately how I imagined that. The
convertWithBackData, as all livarot functions, is very slow. Hopefully
we'll be able to use 2geom for that task one day.
--
bulia byak
Inkscape. Draw Freely.
http://www.inkscape.org
3:26 a.m.
New subject: [Inkscape-user] Improved performance of the object snapper
On Sep 6, 2007 12:36 AM, bulia byak wrote:
On 9/5/07, Diederik van Lierop wrote:
> The last few days I've spent on improving the performance of the object
> snapper. It used to take ages (e.g about 6 seconds on my machine) to
> move a simple rectangle over a large text box, but I've managed to
> reduce this significantly (i.e. < 1 sec.!). This was with both snapping
> to paths and snapping to nodes turned on. For this I had to refactor the
> object snapper code significantly, so I might have introduced new bugs
> or regressions. Please be aware of this and report any suspicious
> behavior, so we can have both fast and robust snapping in v0.46!
I wonder if within current snapping framework the so called Smart
Guides are possible. That is -- snapping without touching.
Description for AI is here:
http://livedocs.adobe.com/en_US/Illustrator/13.0/help.html?content=WS714a...
Among open source applications only Kivio (flowcharting and
diagramming tool from KOffice) has smart guides, to the best of my
knowledge.
Alexandre
5:01 a.m.
New subject: [Inkscape-user] Improved performance of the object snapper
On 2007-November-15 , at 19:26 , Alexandre Prokoudine wrote:
On Sep 6, 2007 12:36 AM, bulia byak wrote:
> On 9/5/07, Diederik van Lierop wrote:
>> The last few days I've spent on improving the performance of the
>> object
>> snapper. It used to take ages (e.g about 6 seconds on my machine) to
>> move a simple rectangle over a large text box, but I've managed to
>> reduce this significantly (i.e. < 1 sec.!). This was with both
>> snapping
>> to paths and snapping to nodes turned on. For this I had to
>> refactor the
>> object snapper code significantly, so I might have introduced new
>> bugs
>> or regressions. Please be aware of this and report any suspicious
>> behavior, so we can have both fast and robust snapping in v0.46!
I wonder if within current snapping framework the so called Smart
Guides are possible. That is -- snapping without touching.
Description for AI is here:
http://livedocs.adobe.com/en_US/Illustrator/13.0/help.html?
content=WS714a382cdf7d304e7e07d0100196cbc5f-6314.html
These are kind of all around in Apple apps but their absolute best
incarnation is in OmniGraffle, a vector drawing tool more flowchart
oriented than Inkscape is. I did not find a screencast of this
feature proper, but by the third of this one
http://downloads.extremesims.com/omnigroup/software/MacOSX/movies/
OmniGraffle/tutorials/part1.mov
there is a small description of it. I guess that the only way to
truly see how good they are is by testing it. If you've got a friend
with a mac around, OmniGraffle is usually given as a gift with the
OS. If Inkscape could acquire such flowcharting capacities (basically
that and a magnet system) it would make it a great replacement for
this (given for free but still shareware app). Furthermore,
Inkscape's connector tool by itself is still underused though it
already has features that Omnigraffle does not. With these additional
feature, Inkscape would become a flowcharting heaven ;)
Among open source applications only Kivio (flowcharting and
diagramming tool from KOffice) has smart guides, to the best of my
knowledge.
JiHO
---
http://jo.irisson.free.fr/
5678
days inactive
5749
days old
inkscape-devel@lists.inkscape.org
2 comments
3 participants
participants (3)
-
Alexandre Prokoudine -
bulia byak -
jiho