Is there a more user friendly way to describe the 'Vacuum defs' function ?
How about we rename something like 'Document Cleanup' ?
Maybe even a dialog with checkboxes and explanations of the various options:
Cleanup and remove the following unused definitions from this document
* Unused gradients * Unused color profiles * Unused patterns * Unused markers * Unused scripts * Unused clipping paths
* Unused filters etc
2012/6/11 John Smith <john.smith7545@...36...>:
Is there a more user friendly way to describe the 'Vacuum defs' function ?
How about we rename something like 'Document Cleanup' ?
The name should be a verb, so a better name is "Clean up document". I don't think a dialog is necessary.
Regards, Krzysztof
El 11/06/12 14:42, Krzysztof Kosiński escribió:
2012/6/11 John Smith<john.smith7545@...36...>:
Is there a more user friendly way to describe the 'Vacuum defs' function ?
How about we rename something like 'Document Cleanup' ?
The name should be a verb, so a better name is "Clean up document". I don't think a dialog is necessary.
I'm thinking about translations for "Document Cleanup" or "Clean up document" and at least in spanish a literal translation could be confused with cleaning all the elements in the document, not just unused definitions. I think that "Clean up unused definitions" or "Clean up SVG" could be more descriptive of the function, although not as "friendly" as the others. Anyway, don't forget that Vacuum defs is rather a technical command and in some cases you can't be too user frendly when it comes to things like that.
I think that "clean up SVG" is more user friendly, more or less descriptive and short enough to be a decent option.
Gez
On 11-Jun-2012 11:37, Guillermo Espertino (Gez) wrote:
El 11/06/12 14:42, Krzysztof Kosiński escribió: I think that "Clean up unused definitions" or "Clean up SVG" could be more descriptive of the function, although not as "friendly" as the others. Anyway, don't forget that Vacuum defs is rather a technical command and in some cases you can't be too user frendly when it comes to things like that.
The problem with "Vacuum Defs" is that a naive user will likely have no idea why it needs to be called in the first place. Place me in a related category - I have yet to find an instance where I would not have wanted vacuum defs to have run automatically whenever a definition was left dangling, but I have had to use vacuum defs many times to clean out these leftovers.
What about making vacuum defs the default on an optional action which occurs whenever a file is saved as an SVG? A high level user who intended to leave defs hanging could then do so by disabling this default action, while the 99.99% of end users, who would never do such a thing, would be spared from having to tidy up an SVG manually.
Regards,
David Mathog mathog@...1176... Manager, Sequence Analysis Facility, Biology Division, Caltech
2012/6/11 mathog <mathog@...1176...>:
The problem with "Vacuum Defs" is that a naive user will likely have no idea why it needs to be called in the first place. Place me in a related category - I have yet to find an instance where I would not have wanted vacuum defs to have run automatically whenever a definition was left dangling, but I have had to use vacuum defs many times to clean out these leftovers.
What about making vacuum defs the default on an optional action which occurs whenever a file is saved as an SVG?
Vacuum defs causes loss of data (e.g. it can remove complex patterns or gradients). In general it is very wrong to lose user data without an explicit action. There could be a checkbox that says 'Vacuum defs on save' that defaults to off. I don't think the ability to perform an arbitrary action is really that useful; adding specific things that can happen when saving (vacuum defs, exporting to specified formats) is better.
Vacuum defs on save would make it impossible to purposefully include unused defs in a file, for example when storing a few often used gradients in a blank document template, or at least prevent people from using Inkscape to create such documents.
Regards, Krzysztof
The name should be a verb, so a better name is "Clean up document".
This seems the most accepted term.
There could be a checkbox that says 'Vacuum defs on save' that defaults to off.
Will add a checkbox like this. Default off is safest - at least until the "loss of data" issue is fixed.
https://bugs.launchpad.net/inkscape/+bug/1015352
________________________________ From: Krzysztof Kosiński <tweenk.pl@...400...> To: mathog <mathog@...1176...> Cc: inkscape-devel@lists.sourceforge.net Sent: Tuesday, June 12, 2012 4:16 AM Subject: Re: [Inkscape-devel] Rename 'Vacuum defs'
2012/6/11 mathog <mathog@...1176...>:
The problem with "Vacuum Defs" is that a naive user will likely have no idea why it needs to be called in the first place. Place me in a related category - I have yet to find an instance where I would not have wanted vacuum defs to have run automatically whenever a definition was left dangling, but I have had to use vacuum defs many times to clean out these leftovers.
What about making vacuum defs the default on an optional action which occurs whenever a file is saved as an SVG?
Vacuum defs causes loss of data (e.g. it can remove complex patterns or gradients). In general it is very wrong to lose user data without an explicit action. There could be a checkbox that says 'Vacuum defs on save' that defaults to off. I don't think the ability to perform an arbitrary action is really that useful; adding specific things that can happen when saving (vacuum defs, exporting to specified formats) is better.
Vacuum defs on save would make it impossible to purposefully include unused defs in a file, for example when storing a few often used gradients in a blank document template, or at least prevent people from using Inkscape to create such documents.
Regards, Krzysztof
------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
2012/6/20 John Smith <john.smith7545@...36...>:
There could be a checkbox that says 'Vacuum defs on save' that defaults to off.
Will add a checkbox like this. Default off is safest - at least until the "loss of data" issue is fixed.
This is not an 'issue'. Loss of data is the very purpose of this command: it removes unused resources. It's just not a good idea to do this automatically by default, because under some circumstances you want to keep them.
Regards, Krzysztof
participants (4)
-
Guillermo Espertino (Gez) -
John Smith -
Krzysztof Kosiński -
mathog