Hi Thomas,
Thanks for the quick reply again.
On 8/9/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
I wouldn't think so, printing in most JDK's is done 'strip wise'
so high res shouldn't be an issue. Also normally the spool file
contains vector data not raster (although this depends a bit on
what is used in the file, fill, stroke and definitely group opacity
can cause problems).
A printer supporting SVG would be ultimate. I'll look if these
printers support it, but I doubt it.
Why won't this be a solution? Among other things the tiles
in the Tiff file can be JPEG compressed. Tiff is _very_ often used
as a container for very high resolution raster image data.
I thought it to be very slow. I'm currently offering the user a
"Print" button, which allows him/her to print this SVG file
(serverside printing). I have a fallback: the GIS server can give me a
PNG instead of SVG, but I am manipulating the SVG, so that's not
really what I want..
Also you might consider output to PDF, which can often
keep much of the data as vector as well...
I tried PNG, JPG, Direct to Printer, PDF. All have the same result:
- slow
- crash with "OutOfMemory" if I do not overrule the min heapsize
- if I overrule this min heapsize, it takes minutes for any result to appear.
I have started the tiled transcoder a few minutes ago, and it's still
hogging my cpu at 99% load. The java process is at 300MB of used
memory, and still growing. Even if it produces a picture, it's still
rather useless, as the user doesn't want to wait a few minutes for any
result.. :)
What I don't understand: what is Adobe doing differently in the SVG
Viewer? Why can they render a low res version within milliseconds? The
render I want to make is not of high quality (printer), so I expect it
to render as fast as Adobe. Where does my assumption go wrong? :)
Regards,
Pieter
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
