Hi John,
John <[EMAIL PROTECTED]> wrote on 03/03/2006 10:46:51 AM:
> On the train into work this morning, I was working on a project idea.
The
> idea is a multi-layered map in SVG for a wargame. Now, the various
layers are
> primarily meant for segregation of data, by purpose, in memory. For
instance,
> a height map layer that contains data showing topographic heights;
another map
> that dictates foliage layer and density, etc. The purpose of layering
is to
> allow the map to toggle visibility of the layer (using <g> element
grouping)
> and limit the amount of data that the engine will have to search to
resolve a
> data check (so it only searches the Foliage layer, and not the height
map, for
> foliage density checks).
You might consider holding these as totally seperate SVG images
rather than viewing them as one multi-layer document. Otherwise you
will be turning on and off more stuff than you need too when you need to
'check' one of the non-visible layers (like foliage).
> 1920000 pixels in a 1600x1200 px map. Since the some layers are SVG
(text),
> they wont count pixel by pixel.
Right an SVG layer is essentially totally dependent on the complexity
of
the geometry not the output size... until you render it.
> Now, my question is this: For the SVG layers, does the color depth
impact the
> memory requirements for that 'layer' at all?
Not until you ask to render it.
> Does Batik default all SVGs as a specific color depth (32-bit), or does
it
> dynamically examine the data and use memory based on what it finds?
For vector data it holds the fill (usually as an RGBA color with
floats) and
the geometry to fill.
> Would a black and white (2-bit) SVG of text take less memory than an
identical
> 32-bit color SVG of the same node/shape/glyph data?
No.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
