AA text used to be very slow once upon a time but I think I sped it up
mostly in 1.5 not 6
There could be other reasons why its 'faster' now. ie better detection
that rendering
involves readback from the surface (not specifically for text) which
can be slow
on AGP buses ..
As for the best default to use, there is a public mechanism built into
JDK6 to
let you get the hints that correspond to the system default. Swing
already uses this
See
http://java.sun.com/javase/6/docs/api/java/awt/Toolkit.html#getDesktopProperty(java.lang.String)
which directs you to the following detailed explanation
http://java.sun.com/javase/6/docs/api/java/awt/doc-files/DesktopProperties.html
-Phil
[EMAIL PROTECTED] wrote:
Hi
I'm looking at how we support AA for text in the Flying Saucer library. Before
Java 6 (we support back to 1.4 for the library), we found AA to be pretty slow,
hence we had it turned off by default. I just turned it back on and found
performance, at least with JDK 6, to be great--now my question is which of the
many possible values for RenderingHints.KEY_TEXT_ANTIALIASING we should use by
default when our users ask for AA text to be enabled. We set the value before
performing text operations (drawString()). I'll probably give them the option
via our configuration file, but am wondering what we should use as a default
recommended value--in our case, we don't know what systems the library will be
used on. Any reasonable approaches you can recommend?
Thanks
Patrick
[Message sent by forum member 'pdoubleya' (pdoubleya)]
http://forums.java.net/jive/thread.jspa?messageID=212445
===
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".
===
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".
