Thanks for the response.
When and why would a user use the Vacuum Defs function; what advantage does it have?
-Kevin
On Tue, 08 Mar 2005 14:15:18 -0500, Kevin Wixson <kevin@...518...> wrote:
Thanks for the response.
When and why would a user use the Vacuum Defs function; what advantage does it have?
For example, if you have gradients you don't use in your picture, they will be gone and your SVG will have a smaller size.
Alexandre
On Tue, 08 Mar 2005 14:15:18 -0500, Kevin Wixson <kevin@...518...> wrote:
When and why would a user use the Vacuum Defs function;
When he's finished with the artwork and is sure he won't ever need any of the stuff which is not currently used by existing objects.
what advantage does it have?
Reducing SVG file size, some speeding up.
On Tue, 2005-03-08 at 14:15 -0500, Kevin Wixson wrote:
Thanks for the response.
When and why would a user use the Vacuum Defs function; what advantage does it have?
What are the drawbacks of going the other approach - doing vacuum defs automatically and only store gradients that are actually used.
I think it's more rare to want the unused gradients stored than not. The way to store gradients if auto-cleanup was to be used is to have a hidden object/layer.
cheers
Jakub Steiner wrote:
What are the drawbacks of going the other approach - doing vacuum defs automatically and only store gradients that are actually used.
It actually comes up fairly often with people working with themes or sets or styles. They might start out with things unused, or add unused defs before the shapes. And copy-n-paste from other documents is another place it comes up.
Probably just needs some intelligent heuristic to get things to a fair balance.
Quoting Jakub Steiner <jimmac@...446...>:
What are the drawbacks of going the other approach - doing vacuum defs automatically and only store gradients that are actually used.
Since SVG allows external references, we don't have enough information to know whether it really is safe to delete arbitrary gradients etc. we may find in the document.
You run the risk of chewing up files that are e.g. intended to be used as "libraries" containing resources (gradients, whatever) that are included from other SVG files. Even though Inkscape doesn't directly support this yet, I do this a fair amount for use with other SVG renderers.
I should note that we do perform automatic cleanup on many types of objects that Inkscape creates without user intervention (since we can guarantee they're only used locally). Perhaps we can tune the automatic vacuuming policy a little more, but I think it's already nearly as agressive as it can safely be.
-mental
participants (6)
-
unknown＠example.com -
Alexandre Prokoudine -
bulia byak -
Jakub Steiner -
Jon A. Cruz -
Kevin Wixson