I added manually
<g id="l1" title="Layer1" label="Layer1" inkscape:groupmode="layer"> ... </g>
around the content of a file. Two problems:
- on open, it shows (root). I think we agreed that if there's a single layer it must be entered on load if there's no current layer remembered in namedview?
- it shows #l1 so title and label are ignored. What is the way to set the visible title apart from id?
On Thu, 4 Nov 2004, bulia byak wrote:
I added manually
<g id="l1" title="Layer1" label="Layer1" inkscape:groupmode="layer"> ... </g>
around the content of a file.
That reminds me ... we could really use a "make sublayer from selection" action or something similar.
(I think if the selection is a single group, that would just make the group a layer; otherwise it'd group the objects first and then make a layer of that.)
Two problems:
- on open, it shows (root). I think we agreed that if there's a single
layer it must be entered on load if there's no current layer remembered in namedview?
Hmm. I recall implementing that; perhaps it has been broken at some point since?
- it shows #l1 so title and label are ignored. What is the way to set
the visible title apart from id?
<title> is an SVG element, not an attribute (I originally made that mistake myself), and label is not part of the SVG standard at all; it's an attribute in our own namespace. Try inkscape:label="Layer1"
FWIW, there's an important difference of purpose between <title> and inkscape:label...
<title> is an accessibility feature for end-users (e.g. to provide brief descriptions for folks using assistive technology) -- <desc> is its "longer" equivalent.
Conversely, inkscape:label is intended for names and annotations that need only be meaningful to the content author. You've probably seen the weird notations that some graphic designers like to use for their layer names in Gimp, Illustrator, or Photoshop. inkscape:label provides a place for that so they don't go trying to cram it into id or <title> instead.
-mental
That reminds me ... we could really use a "make sublayer from selection" action or something similar.
Why, the New Layer command could just take the selection and put it into the new layer. I think it would be logical.
(I think if the selection is a single group, that would just make the group a layer; otherwise it'd group the objects first and then make a layer of that.)
Yes.
Two problems:
- on open, it shows (root). I think we agreed that if there's a single
layer it must be entered on load if there's no current layer remembered in namedview?
Hmm. I recall implementing that; perhaps it has been broken at some point since?
Please test and fix, it's an important thing for newbie layerers.
<title> is an SVG element, not an attribute (I originally made that mistake myself), and label is not part of the SVG standard at all; it's an attribute in our own namespace. Try inkscape:label="Layer1"
Ah, thanks, that works.
Conversely, inkscape:label is intended for names and annotations that need only be meaningful to the content author. You've probably seen the weird notations that some graphic designers like to use for their layer names in Gimp, Illustrator, or Photoshop. inkscape:label provides a place for that so they don't go trying to cram it into id or <title> instead.
That makes sense.
So, what remains to do apart from enabling the buttons? (I can't wait :)
On Thu, 2004-11-04 at 19:42, bulia byak wrote:
That reminds me ... we could really use a "make sublayer from selection" action or something similar.
Why, the New Layer command could just take the selection and put it into the new layer. I think it would be logical.
That might be confusing... for example, if a user draws a bunch of shapes on one layer, and then immediately creates a new one, the last shape drawn will get moved to the newly created layer.
So, what remains to do apart from enabling the buttons? (I can't wait :)
From Roadmap:
* Finish show/hide lock/unlock buttons [mental] * Add UI for setting inkscape:label attribute [mental] * Add "selection to sublayer" command and its inverse [mental, bb] * Make "move to next/prev layer" move selected objects to next/prev layer [mental, bb] * Make "intelligent" raise/lower aware of visibility status (using per-desktop SPDesktop::itemIsHidden?) [bb] * Make selection tool and tests for item-at-point aware of per-desktop visibility [bb] * search checks inkscape:label, and ignores layers [bb]
With respect to "intelligent" raise/lower, we should skip over invisible objects as well as those whose bboxes are outside the viewport.
Also, it shouldn't be possible to select an invisible object with the selection tool.
-mental
On Thu, 4 Nov 2004, MenTaLguY wrote:
Date: Thu, 4 Nov 2004 19:21:36 -0500 (EST) From: MenTaLguY <mental@...3...> To: bulia byak <buliabyak@...400...> Cc: Inkscape inkscape-devel@lists.sourceforge.net Subject: [Inkscape-devel] Re: layers again
On Thu, 4 Nov 2004, bulia byak wrote:
I added manually
<g id="l1" title="Layer1" label="Layer1" inkscape:groupmode="layer"> ... </g>
around the content of a file.
That reminds me ... we could really use a "make sublayer from selection" action or something similar.
"New Layer from Copy Ctrl+J" and "New Layer from Cut Ctrl+Shift+J" work rather well (see Adobe Photoshop (7.0) or my scripts for the gimp:) http://matrix.netsoc.tcd.ie/~horkana/dev/gnome/gimp/script-fu/script-fu.html (python-fu version of "Layer from" also available)
Other raster application like Paint Shop Pro have something like Promote selection to layer but having used both I've got to say I prefer the way photoshop does it because I think gets you closer to where you were going anyway (I liked it so much I implemented it twice). I hope you'll try out my scripts to get a better feel for it before you make up your mind how to implement it.
<title> is an SVG element, not an attribute (I originally made that mistake myself), and label is not part of the SVG standard at all; it's
an
attribute in our own namespace. Try inkscape:label="Layer1"
FWIW, there's an important difference of purpose between <title> and inkscape:label...
I dont understand why you cannot use the group id directly as the layer name. Jasc Webdraw has a tree view widget, somewhat reminiscent of a layers dialog and the id's are the labels (although i think it automatically forces you to replace spaces with underscores).
Sincerely
Alan Horkan
http://advogato.org/person/AlanHorkan/ Inkscape, Draw Freely http://inkscape.org Free SVG Clip Art http://OpenClipArt.org
On Thu, 2004-11-04 at 19:44, Alan Horkan wrote:
I dont understand why you cannot use the group id directly as the layer name. Jasc Webdraw has a tree view widget, somewhat reminiscent of a layers dialog and the id's are the labels (although i think it automatically forces you to replace spaces with underscores).
Two reasons:
1. changing the id requires updating the document structure (which is a pain to require for every name change, and will be obnoxious to users who use external document references)
2. as you point out, the grammar for ids is very constrained; there are other restrictions besides simply whitespace being disallowed that would seem very annoying and arbitrary to users naming layers
-mental
On Thu, 4 Nov 2004, MenTaLguY wrote:
FWIW, there's an important difference of purpose between <title> and inkscape:label...
<title> is an accessibility feature for end-users (e.g. to provide brief descriptions for folks using assistive technology) -- <desc> is its "longer" equivalent.
Conversely, inkscape:label is intended for names and annotations that need only be meaningful to the content author. You've probably seen the weird notations that some graphic designers like to use for their layer names in Gimp, Illustrator, or Photoshop. inkscape:label provides a place for that so they don't go trying to cram it into id or <title> instead.
<title> and inkscape:label sound redundant to me.
Bryce
On Fri, 2004-11-05 at 01:24, Bryce Harrington wrote:
<title> and inkscape:label sound redundant to me.
Well... check out section 5.4 of the SVG 1.1 recommendation and see what you think. To sum up by example, though:
Is "Daisy's hat, decorated with spring flowers," a usable layer name? Would most authors mind having the layer dialog or layer selector be wide enough to show that?
Alternately, is "Hat [lineart] A" a useful textual/audio rendering for users employing assistive technology?
Many designers tend to name their layers more like the latter, while the SVG spec suggests <title>'s use as an accessibility feature for content consumers which may be rendered via tooltips, alternate stylesheets, speech synthesis, etc.
A secondary issue is that <title> (and <desc>) are supposed to support arbitrary markup (e.g. XHTML), which is probably a bit beyond what we want to have to deal with in layer names. I didn't realize that at first when I had you do the initial UI for them (at that time I thought they were attributes, too).
-mental
On Fri, 05 Nov 2004 21:27:23 -0500, MenTaLguY <mental@...3...> wrote:
On Fri, 2004-11-05 at 01:24, Bryce Harrington wrote:
<title> and inkscape:label sound redundant to me.
Well... check out section 5.4 of the SVG 1.1 recommendation and see what you think. To sum up by example, though:
Is "Daisy's hat, decorated with spring flowers," a usable layer name? Would most authors mind having the layer dialog or layer selector be wide enough to show that?
A nice solution would be cropping the name to widget boundaries and displaying the rest of it as a hint (like MS Word does it for header names in outline palette).
Alexandre
On Sat, 2004-11-06 at 04:31, Alexandre Prokoudine wrote:
Is "Daisy's hat, decorated with spring flowers," a usable layer name? Would most authors mind having the layer dialog or layer selector be wide enough to show that?
A nice solution would be cropping the name to widget boundaries and displaying the rest of it as a hint (like MS Word does it for header names in outline palette).
I believe that's already built into the modern Gtk treeview widget.
In any case I just don't want an audio SVG navigator to spit out "Hat bracket lineart unbracket EY," someday because that was a convenient layer name for the artist and we were using <title> for layer names.
-mental
participants (5)
-
Alan Horkan -
Alexandre Prokoudine -
Bryce Harrington -
bulia byak -
MenTaLguY