A few comments.....
1) The reason everyone keeps bringing up performance is that it is
a problem not only for graphics but also for GUI. If we could have
a point in time where a Java application's GUI would perform as fast
as a native apps GUI in all hardware configs then we're happy.
ie this brings up the problems with images depths, remote X servers
etc etc all of which boil down to the Java 2D implementation sooner or
later.
2) Is cross-platform pixel accuracy a goal worth obtaining at all costs ?
Anti-aliasing lines might be the same in the current Java2d implementation
but the rendering is ugly compared with OpenGLs. Fonts definitely dont
render the same way anyhow. Just rotate a font on Solaris :-)
3) We realize that unifying all the best bits of the graphics API
is a herculean task, if not impossible, but the long and short of it is that
as programmers we dont have a choice here. As Java2D is such an integral
part of the Java2SE platform we can't just go and implement something
better. We're relying on the Java2D team to give us a platform that allows
us to say "Yes choosing Java 2 to develop a client application was the best
idea."
4) Where is the bar being set for the post-Kestrel release ?
What are the objectives for performance, cross-platform compatibility, etc ?
How do these improvements relate to the GUI.
And when-ish is it due ?
Ok, so enough already. If you were pitching Java 2D against C++ for
development of a large client application (lots of GUI, lots of graphics)
due end of next year, what would be your pitch on
performance issues ?
regards,
Graeme Wallace
Technical Director
INT Inc.
===========================================================================
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".
