Hi all,
I was reading through the following blog
(http://weblogs.java.net/blog/joshy/archive/2005/05/the_reponse_to.html)
where I read the following:
"Fonts are another one of Metal's areas where insistence on backward
compatibility is hurting Swing. Metal still has those big bold chunky
fonts by default that scream "amateur", and I've seen Sun's response in
the past being "some clients depend on these font sizes and types". Sun
does all the hard work technically - Swing can pick up system fonts and
font sizes, it can anti-alias fonts, and so on, *IF* you use the
correct command-line option, because by default it's
backward-compatible. Boom - most people never see the change.
It was a similar story with J2SE 1.4 and assertions - they were
provided but were off by default. In my team makefiles are maintained
by one guy. If assertions were disruptive (they were not), he would
have changed javac options to be backward compatible and none else
would have noticed. As it is, J2SE 1.4 was backward compatible, we
smoothly transitioned to it without a change, and even today developers
are not getting indoctrinated into using assertions because it is off
by default."

So what he's saying here is that through a simple command-line option
we have anti-aliasing? That would be really cool, however, I searched
through the command-line options that are posted by Sun and could not
find anything about this subject. I tried responding to the author on
the java.net site, but for some reason even after logging in it would
not allow me to post comments.

Therefore my question is, does anyone know which command-line option
the author of the blog was referring to?

Thanks, Jonck