Jim Graham wrote:
The ImageIcon class you are using in 2 places uses the original image APIs that have been around since the 1.0 versions and which were targetted at Applets. These APIs were designed to manage modest images that might be appropriate for web page design elements and to do so asynchronously so that your applet is not necessarily stuck waiting for image data to arrive over the network while it is trying to get initialized. The image data for these APIs is stored very opaquely and is very difficult to manipulate and needs to be converted when moving to or from a BufferedImage.
Wow....TREMENDOUS improvement. I haven't gotten the refactoring completely finished, but so far I've created the custom component, loaded the image and magnified it 10x and am hovering at around 28m ram usage....it was around 72m at 10x under the previous design.
Thanks very, very much guys. I'm a newbie when it comes to Java imaging (and imaging at all, for that matter) and feeling my way through the dark.
Are there any good sources of information, targeted at non-enlightened java developers like myself, that you would recommend? I have purchased the book "Building Imaging Applications with Java Technology", and while it's been somewhat helpful, the examples are iterative and I haven't had the time to read cover-to-cover. I'm looking for more of a reference with best practice information....how to do this and that while not aiming gun at foot. For instance, some of the examples in Sun's tutorial demonstrate loading images via an ImageIcon, iirc. I would've never known it was causing such a negative effect had you not mentioned it.
Thanks again for your time.
John
=========================================================================== 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".
