Thomas DeWeese wrote:
Does 3K of memory usage for each <use>'d <line> seem right?
That seems kind of high to me.
It's perhaps a bit higher than I would have expected but only
by a factor of 2 or so which probably means it's right ;). Just to
summarize the objects involved with each element in the DOM:
Thanks for the summary, that puts things in perspective.
I will mention that you will be much better served putting all
the line elements into one 'big' path/polyline element (although
115 lines is not that big for a path/polyline). I suspect that
you need the individual lines for some reason? Hit testing?
Already did that (<polyline> replacement) and it did in fact
help a lot, to the point where it's not an issue anymore.
A zillion individual lines is what you get when you export certain
DXF files from Adobe Illustrator into SVG. Another fun side effect
is a <g> node with no attributes containing a zillion <line> nodes
each of which repeats the same stroke, fill, stroke-linejoin, etc.
attributes, instead of setting them once in the enclosing <g> node.
These are some reasons I've thought in the past about writing an
SVG optimizer, which would transform an SVG document into an equivalent,
but smaller one. I'm sure there are lots of tricks one could use to
compact this kind of semi-automated output.
Thanks,
-Archie
__________________________________________________________________________
Archie Cobbs * CTO, Awarix * http://www.awarix.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
