Re: [platform-swt-dev] AWT on top of SWT

[David_Whiteman@xxxxxxx]

I'm equally curious.  Although our AWT was designed to be a PersonalJava implementation, you would hard pressed to find AWT 1.1 code we didn't run well.  The only stumbling block to actually using our AWT in desktop deployment would probably be the license agreement, since it's non-open source code (although source is provided).  FWIW, our AWT is the default web browser plugin on the QNX platform, so we run applets that were not designed for micro environments quite nicely.

I know what you're saying about peers from our previous conversation, since SWT doesn't implement the Peer interface, but how often do you write AWT application code that interacts with peers?  Does it really matter if the widgets being used are implementing that interface, as long as the AWT API works well?

David
--
David Whiteman
OTI Raleigh
david_whiteman@xxxxxxx

"Patrick Mueller" <pmuellr@xxxxxxx> Sent by: platform-swt-dev-admin@xxxxxxxxxxx 04/12/2002 01:41 AM Please respond to platform-swt-dev

To:        <platform-swt-dev@xxxxxxxxxxx>         cc:                 Subject:        Re: [platform-swt-dev] AWT on top of SWT

I'm curious.  Define "here", in the "really wouldn't work here" bit.  Are you trying to implement enough AWT to get a recent vintage Swing running or something?  Or just other > AWT 1.1, non-Swing features.
 
>I've been working on one, and got it partly working. Getting it to work as a
>plugin has been challenging wrt classloaders. I chatted with some of the
>Instantiations folks at JavaOne, and I think we came up with an idea to make
>the classloaders work. I'll see if I can try it out this coming weekend.
>
>BTW: The OTI implementation for VA Micro that keeps coming up really
>wouldn't work here. I've looked into it and it's not complete (I believe it
>assumes J2ME personal config, which is rather limited), and wasn't really a
>peer setup.
>
>-- Scott