RE: [JAVA2D] java2d and X sessions
> The motif toolkit (which is the default in 1.4.2 everywhere and
> on Solaris in 5.0) is very bad at high latency connections.
> In 5.0 AWT added XAWT - X11-based toolkit, it's much, much better.
> But it wasn't made the default on Solaris, only on linux,
> so you'll need to force it.
OK. we'll have to get 5.0 and try it out.
> Try running on 5.0 with the XAWT instead
> the motif toolkit:
> AWT_TOOLKIT=XToolkit java YourApp
> (or you can set a -D property for the default toolkit).
I don't quite follow how I invoke my app, can i just do
java -Djava.some.property=XToolkit MyApp ...
or is AWT_TOOLKIT a shell variable, or what?
> In 6.0 remote performance improved even more (and the XAWT
> toolkit is the default on all unix platforms).
5.0 is a possibility -- maybe 50% shot -- but 6.0 is pretty much
we'll have to take whatever we can get. good to know that things are
better though. Maybe when we get to 6.0 in 5 years or so we'll see some
performance boosts! ;-)
(We JUST moved to 5.0 and are still unable to use the new language
due to our inability to guarantee that the systems we deploy to will
> Also, does your application do any kind of complex rendering,
> like antialiased rendering or alpha compositing (translucent images
> , etc)?
> If so, you might want to set this property:
> It might help.
no, the simple application we're testing is just a swing app
that has various components but nothing fancy. Not even any
custom components, just basic Swing layouts.
However, it's very handy to know this property. What does it
do, is there an API doc on it?
To unsubscribe, send email to firstname.lastname@example.org and include in the body
of the message "signoff JAVA2D-INTEREST". For general help, send email to
email@example.com and include in the body of the message "help".