On 13/10/2012 11:38, Alexandre Prokoudine wrote:
On Sat, Oct 13, 2012 at 1:31 PM, ~suv wrote:
> Same here: the first steps I did after compiling the initial commit was
> exploring which options to use to have the previews rendered at the same
> scale for all symbols (to see how they relate to each other).
Hmmm, what would be the practical use for this?
TBH I don't know the scope of real use cases for custom symbol files in
Inkscape (the list of related feature requests in the bug tracker is
long IIRC, and I haven't revisited them yet), nor for <symbol>
definitions found in SVG files in general - for me personally, exploring
the preview options as described was a logical first step to get
acquainted with the (to me unknown) symbols contained in the sample
symbol file (without having to insert each one into the current document
first).
For technical drawings (or other use cases which might keep the symbols
mostly unscaled (1:1) in the document), one could think of
- different sizes of the same symbol
- a set of similar symbols varying mostly in one dimension
- unscaled default stroke widths (same stroke width for all previews)
- different default stroke widths defined per symbol, depending
on original 1:1 size
- …
> Having quick access to the view options seems part of the basic
usage to
> me: AFAICT a preferred current view mode will also depend on the kind of
> symbols available in the currently selected symbol file (or the current
> document).
I can only think of small bitmaps as symbols, as opposed to vector objects.
?
The 'Symbols' dialog manages and renders previews of any kind of SVG
<symbol> defined in the current document (not limited to those inserted
from a shared or custom Inkscape symbols file). AFAICT SVG 1.1 does not
imply limitations to the size, content or use cases of a <symbol> element:
<
http://www.w3.org/TR/SVG11/struct.html#SymbolElement>