AWT is dead now

Cedric Berger cedric@wireless-networks.com
Tue Mar 21 09:17:00 GMT 2000


ks@micky.rgv.hp.com wrote:
> Take this clue. Swing does not run on KVM. Swing does not run on
> Chai. Swing does not run on IBM VM. Swing does not run on Kaffe.
> Swing does not run on jview. Swing does not run on TowerJ.

Swing do run very well on jview (I'm using Together/J in this
configuration).
I would be very very surprised if it didn't work on IBM VM or TowerJ
(even it doesn't make a lot of sense to use TowerJ with Swing, towerJ
being designed for server apps).
On the other hand, I will agree with you that Sun's Swing is probably too
big
for most of today's embedded application. But it is probably possible to
make a reduced version of Swing if for example you remove Pluggable L&F
> >
> > 4) if somebody really need it at that point, implementing
> > AWT widgets by calling Swing code: I believe that it is (or
> > was) Sun's plan too.
> >
>> What amazing hubris. Who is implementing AWT on top of Swing supposed
> to help?

Simplest way to achieve backward compatibility with old apps that uses
AWT.


More information about the Java mailing list

AltStyle によって変換されたページ (->オリジナル) /