G
glin
what can't you do in swing but in awt? thank you.
Alex Molochnikov said:The question was stated in the unqualified form: what can you do in AWT that
cannot be done in Swing. And the answer to THAT question remains: nothing.
Whether the operations might be simpler is of no consequence here, since AWT
has reduced functionality in comparison with Swing, and for this reason
alone is simpler in all respects. And AWT is, of course, lighter than
Swing - which again has nothing to do with the OP question.
Hal Rosser said:You can operate in a java 1.1 environment with awt - but not with swing
Alex Molochnikov said:The question was stated in the unqualified form: what can you do in AWT that
cannot be done in Swing. And the answer to THAT question remains: nothing.
Whether the operations might be simpler is of no consequence here, since AWT
has reduced functionality in comparison with Swing, and for this reason
alone is simpler in all respects. And AWT is, of course, lighter than
Swing - which again has nothing to do with the OP question.
components,Wiseguy said:Is AWT really (lighter) than Swing? I guess it depends on your definition
of lighter.
From page 3 of Sun's Mastering the JFC:
Swing is a set of mostly lightweight components built on top the AWT.
Swing provides lightweight replacements for the AWT's heavyweight
Alex said:Perhaps you forgot to put a smiley at the end of your statement. Otherwise
it is hard to take seriously claims of Swing deficiency in the timeframe
before Swing came into existence.
Rogan Dawes said:I think it was actually a fair comment, and did not require smiley's.
The reality is that there are still Java 1.1 environments around
(Windows 95, Win98?), and if you are writing an applet, you need to
consider this.
Alex said:The lifespan of this thread has already far exceeded its importance, and the
OP does not seem to care of the result of this debate either way,
Alex Molochnikov said:I cannot imagine anyone writing for Java 1.1 env. these days - where would
one even get it from? Applets are all but extinct now, and the few that
still survive make use of Java plugin available from Sun - and it ain't 1.1.
Again, the original question was - what can be done in AWT that cannot be
done in Swing? And my answer still is: nothing.
The lifespan of this thread has already far exceeded its importance, and the
OP does not seem to care of the result of this debate either way, so I will
let you have the final word in it.
Swing is a superset of AWT. So, by definition, anything that you can do in
AWT, you can do in Swing.
Gerry said:On a related note, is there any plans to extend the abilities of AWT?
Or is Swing supposed to be the way to go?
I would prefer to use native interface elements rather than using
something that might resemble a native control.
Gerry said:On a related note, is there any plans to extend the abilities of AWT?
Or is Swing supposed to be the way to go?
I would prefer to use native interface elements rather than using
something that might resemble a native control.
This is especially noticable on a Mac where the menu bar is not at the
top of the window. It's at the top of the screen.
Larry Barowski said:System.setProperty("com.apple.macos.useScreenMenuBar", "true");
or on Java 1.4 or higher
System.setProperty("apple.laf.useScreenMenuBar", "true");
will enable that for Swing with Mac L&F.
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.