You are viewing a plain text version of this content. The canonical link for it is here.
Posted to batik-users@xmlgraphics.apache.org by th...@kodak.com on 2006/05/02 12:04:28 UTC
Re: printing svg is still too slow. How Microsoft solve that?
Hi Mario,
JavaTeam <ma...@inet.hr> wrote on 04/30/2006 05:19:16 AM:
> I have an outOfMemory problems in a huge charts printing so I tried to
solve
> the thing with the batik and SVG. I cut my chart in a dozen svg files
> (about 1MB) and then print it. I don't have OutOfMemory problem any more
but
> still I was wondering how Microsoft can solve the printing a huge
charts,
> so quick, in a MS Project ? If you tried that product?
In general printing a chart is not a lot of real 'geometry', so if you
can get the output from just simple drawing commands the result should be
small. However, I know that there are lots of Java2D operations that will
force rasteriziation (the use of opacity is the main one - any semi-opaque
fill, or image). Once you start rasterizing parts of the page your memory
requirements for a large chart will go off the chart...
---------------------------------------------------------------------
To unsubscribe, e-mail: batik-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: batik-users-help@xmlgraphics.apache.org
Re: printing svg is still too slow. How Microsoft solve that?
Posted by JavaTeam <ma...@inet.hr>.
Hi Mario,
JavaTeam <ma...@inet.hr> wrote on 05/02/2006 02:31:03 PM:
> You said:
>> Once you start rasterizing parts of the page your memory
>> requirements for a large chart will go off the chart...
>
> If I understand I must send the parts of the chart. I tried that before
I
> use batik, in a print method of a printable class:
I was refering to the fact that some operations on Graphics2D can't
be mapped 'cleanly' to some 'back ends'. When that happens it rasterizes
the content at device resolution.
That is way I got some un-undertandable parts of svg file. They are node of
JTree I generate to svg.
I was thinking that I forgot some small images in a code. :)
--
View this message in context: http://www.nabble.com/printing-svg-is-still-too-slow.-How-Microsoft-solve-that--t1532216.html#a4207321
Sent from the Batik - Users forum at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: batik-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: batik-users-help@xmlgraphics.apache.org
Re: printing svg is still too slow. How Microsoft solve that?
Posted by th...@kodak.com.
Hi Mario,
JavaTeam <ma...@inet.hr> wrote on 05/02/2006 02:31:03 PM:
> You said:
>> Once you start rasterizing parts of the page your memory
>> requirements for a large chart will go off the chart...
>
> If I understand I must send the parts of the chart. I tried that before
I
> use batik, in a print method of a printable class:
I was refering to the fact that some operations on Graphics2D can't
be mapped 'cleanly' to some 'back ends'. When that happens it rasterizes
the content at device resolution.
> public int print(Graphics _g, PageFormat pageFormat, int pageIndex){
> _g.setClip(x0,y0,xpage,ypage);
> }
>
> But it is also memory too heavy.
> --
> View this message in context:
http://www.nabble.com/printing-svg-is-still-too-
> slow.-How-Microsoft-solve-that--t1532216.html#a4196865
> Sent from the Batik - Users forum at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: batik-users-unsubscribe@xmlgraphics.apache.org
> For additional commands, e-mail: batik-users-help@xmlgraphics.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: batik-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: batik-users-help@xmlgraphics.apache.org
Re: printing svg is still too slow. How Microsoft solve that?
Posted by JavaTeam <ma...@inet.hr>.
thomas.deweese wrote:
>
> Hi Mario,
>
> JavaTeam <ma...@inet.hr> wrote on 04/30/2006 05:19:16 AM:
>
>> I have an outOfMemory problems in a huge charts printing so I tried to
> solve
>> the thing with the batik and SVG. I cut my chart in a dozen svg files
>> (about 1MB) and then print it. I don't have OutOfMemory problem any more
> but
>> still I was wondering how Microsoft can solve the printing a huge
> charts,
>> so quick, in a MS Project ? If you tried that product?
>
> In general printing a chart is not a lot of real 'geometry', so if you
> can get the output from just simple drawing commands the result should be
> small. However, I know that there are lots of Java2D operations that will
> force rasteriziation (the use of opacity is the main one - any semi-opaque
> fill, or image). Once you start rasterizing parts of the page your memory
> requirements for a large chart will go off the chart...
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: batik-users-unsubscribe@xmlgraphics.apache.org
> For additional commands, e-mail: batik-users-help@xmlgraphics.apache.org
>
>
>
You said:
Once you start rasterizing parts of the page your memory
requirements for a large chart will go off the chart...
If I understand I must send the parts of the chart. I tried that before I
use batik, in a
print method of a printable class:
public int print(Graphics _g, PageFormat pageFormat, int pageIndex){
_g.setClip(x0,y0,xpage,ypage);
}
But it is also memory too heavy.
--
View this message in context: http://www.nabble.com/printing-svg-is-still-too-slow.-How-Microsoft-solve-that--t1532216.html#a4196865
Sent from the Batik - Users forum at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: batik-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: batik-users-help@xmlgraphics.apache.org