On Wed, 29 Sep 2004, MenTaLguY wrote:
I think we will need to revisit orphan collection policy once we have swatches implemented; we may be able to do something that feels a little more natural.
...
With the current UI (i.e. no swatches) the current policy seems to be the most aggressive one that doesn't surprise most users when it deletes things).
"Clean up defs" has to be a temporary solution! Let's not discuss on where to put it, it's not important, really.
so long as it is clear that this solution is not permanant, that is enough to keep me happy for now.
there are still more issues I didn't mention but I want to mention and this should be my last post on this thread for a while.
I changed the subject of the thread because I really think that something we could do now would be to change the label wording to something simpler like "Clean up defs" or "Remove Unused defs" and ideally we we will need a better term than an abbreviation like <defs> as it is an implementation detail we shouldn't be exposing to the users.
I forgot to mention how bizarre it is to have a menu item that to the casual user appears to do nothing, when working exactly as intended. Having a clear status bar message is a start but doesn't help the fact that if an ordinary user is wondering what "Vacuum defs" does and then tries it out they will be none the wiser to what has actually happened as there is no significant visual feeback.
Shouldn't this feature be a checkbox item? (or moved to preferences?) if you want to have unused defs automatically cleaned up would you really want to invoke it manually each time? (I know I wouldn't)
Sincerely
Alan Horkan
http://advogato.org/person/AlanHorkan/ Inkscape, Draw Freely http://inkscape.org Free SVG Clip Art http://OpenClipArt.org