>I have a component that takes several minutes and 10MB of spool file to >print. I would like to know if anyone has any optimization tips to share. > >I found that using a white background seems to improve the spool size >considerably. > >I plan to tweak the rendering hints. I figure out that using the lowest >quality rendering hints on a printer shouldn't deteriorate the end result >too much because printers have very high resolutions. I guess this will >mostly improve the time, but perhaps also the space?! Only 10Mb? - ours are usually about 100Mb and I've yet to find a printer which can print them. Some things you can try are to give it the lowest quality rendering hints. Definitely turn off antialiasing, don't draw images which have an alpha channel, and don't use any fancy alpha compositing in your rendering - any of these things will force Java2D to decide to render the whole page as an image instead of sending stuff directly to the printer (I'm assuming these are PostScript spool files). If you do all this, things may or may not improve. We have terrible trouble with Java printing drawing stuff at screen resolution and producing enormous spool files. We once had an A4 page which took two hours to print. We solved the problem for PostScript printers by producing PostScript directly and sending it to the printer and we're currently investigating using native methods to do direct GDI calls for Windows to bypass Java printing altogether. Jerry Jerry Huxtable http://www.jhlabs.com =========================================================================== 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".
