I think the idea was to implement heavyweight components only for the
AWT pieces that Swing relies on, and the rest of AWT would actually be
implemented on top of Swing. That way, you don't have to write as much
native code. I may have misunderstood, though, I'm only loosely
following the thread...
On Dec 19, 2007, at 8:54 PM, email@hidden wrote:
On Wed, 19 Dec 2007, robert engels wrote:
Yes, there are a few I forgot dealing with the menu bar, but that
is all. You don't need to implement the fields, or buttons, etc.
These are are lightweight components in a Swing application. Only
an AWT application needs them. Check the JDK source... (even under
OSX using decompilation - they are still Java rendered).
Last I heard, there were still a lot of applets out there that
used AWT components instead of Swing. Also, if you want to pass the
Java Compatibility Kit (which I'm sure the OpenJDK folks would see
as a requirement), you've got to implement all of them.
Peter
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/java-dev/email@hidden
