This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: Making shared objects with GCJ
Bryce McKinlay wrote:
> Classpath's Swing implementation should not neccessarily be limited to
> using the same L&F across platforms. Since Swing was designed for
> pluggable look & feels, there is no reason why native toolkits can't be
> used to implement Swing, just like SwingWT and Apple's Swing
> implementation on OS X.
Swing was initially explicitly designed as a pure Java GUI toolkit. It
was only later that native functionality, such as system colours and
filesystem roots, was introduced into the mix.
If the intention had simply been to support a richer native GUI, I
believe AWT would have been extended instead of an entirely new API
introduced.
Note, I'm not saying I disagree with the idea of SwingWT etc. Swing was
largely introduced because of user concerns with the existing AWT: on
the target machines at the time, it was slow, and there were doubts as
to its memory consumption and scalability as well. Nowadays the typical
machine is that much faster, and these perceived problems with
natively-implemented GUI (including AWT) have disappeared.
--
Chris Burdess