2D printing always makes at least 2 passes.
The 1st is to figure out whether it is possible to render the page using
graphics primitives (path graphics) or to create it as a raster.
If the raster path is taken then many passes may be needed, each generating
a band or slice of the page. That is expected behaviour for rasters.
Bongo must have something on the page which makes printing use a raster.
These rasters can be quite large, and efforts are underway to reduce
the number of cases in which the whole page is a raster.
The forthcoming beta release of 1.3 will no longer use a raster if there
are opaque images on the page. That work isn't complete yet, so may not work
quite right for all cases.
There will be a private implementation-dependent property to force the
raster path to be used if the beta causes such problems in your apps.
Similarly, there are improvements happening in the path graphics printing pipe.
Text will be printed using "GDI" primitives. However the unimplemented
part is that so far it works only for "physical" fonts such as "Arial",
or "Times New Roman", obtained through either the "getAllFonts()" or
"getAvailableFontFamilyNames()" APIs. "Logical" fonts such as "dialog"
which are the most commonly used missed beta and will have to be addressed
in the FCS.
So far in beta these improvements will only show up in win32 printing.
We hope to address the same set of issues in Solaris/PostScript printing.
The 1.3 beta (aka kestrel or Java 2 Standard Edition V 1.3) should ship
before the end of this month.
-Phil.
> I have great performance and memory problems with the
> printing classes of 1.2.
>
> Each page of my printout seems to require many passes to
> render it.The print method is called x times with the same
> page index. (It seems that the print method is called for
> every component im my GUI).
>
> Meanwhile the print job is spooling about several minutes.
> At last my graphics to print is about 4 MB. With the
> printing classes of 1.1 the same graphics has 3 KB.
>
> The GUI is implemented with Free Bongo, but I dont't think
> that the Bongo Components cause these problems (Bongo is
> based on AWT). I heard of people with the same problems
> using AWT Components or Swing Components.
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JAVA2D-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
