[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
RE: [platform-swt-dev] SWTToolkit as AWT Peers
|
That's kinda what it sounded like to me...
I'm really trying to do something more general. I'm hitting a few spots now
that look pretty tricky (like "where does the event loop go"). Looks like
I'll have to have some inter-thread communication to deal with that to avoid
the thread access and display issues...
Fun fun fun...
-- Scott
==============================================================
Scott Stanchfield FGM, Inc. scott@xxxxxxx
Home Page: http://javadude.com scott@xxxxxxxxxxxx
Lead author of "Effective VisualAge for Java, Version 3"
http://javadude.com/evaj
VisualAge for Java Tips and Tricks http://javadude.com/vaj
AWT & Swing FAQ Manager, jGuru.com
Visit for Java Enlightenment! http://www.jguru.com
==============================================================
> -----Original Message-----
> From: platform-swt-dev-admin@xxxxxxxxxxx
> [mailto:platform-swt-dev-admin@xxxxxxxxxxx]On Behalf Of Andrew
> Sandstrom/PHX/OTI
> Sent: Monday, November 26, 2001 11:01 AM
> To: platform-swt-dev@xxxxxxxxxxx
> Subject: RE: [platform-swt-dev] SWTToolkit as AWT Peers
>
>
> Another thing to add about 1.1 is that this implementation was targeted
> towards the embedded space, and as such was implemented to PersonalJava
> spec rather than J2SE. PersonalJava calls for 1.1 level API and features.
>
>
> --Andrew
>
>
>
>
>
> "David Whiteman/RAL/OTI" <David_Whiteman@xxxxxxx>
> Sent by: platform-swt-dev-admin@xxxxxxxxxxx
> 11/26/2001 08:49 AM
> Please respond to platform-swt-dev
>
>
> To: platform-swt-dev@xxxxxxxxxxx
> cc:
> Subject: RE: [platform-swt-dev] SWTToolkit as AWT Peers
>
>
> Yes, it's mostly just 1.1. It doesn't technically use the *Peer classes
> to implement the native implementation. SWT logically serves as a peer
> layer, but you don't get anything SWT-related if you call getPeer() on a
> Component in BBAWT; that's one of the noted deviations. If you really
> need SWT to implement the Peer interface, then you'd have to roll your
> own. However, I think that's an implementation detail that is not
> necessary for the Eclipse integration goals you're trying to
> achieve, if I
> understand you correctly. Probably the best test would be for you to run
> a lot of your favorite apps and snippets in our AWT to see if it
> runs your
> code as you expect - if it doesn't, we'd love to hear about it.
>
> Probably the biggest areas our AWT deviates from the 1.2 spec are in 2D
> graphics and printing, partly because a lot of that isn't currently (or
> wasn't previously) available in SWT for all platforms that we were
> interested in. Also, Swing kind of limps along on BBAWT (and only Swing
> 1.1.x works at all).
>
> Regards,
> David
> --
> David Whiteman
> OTI Raleigh
> david_whiteman@xxxxxxx
>
>
>
> "Scott Stanchfield" <scott@xxxxxxxxxxxx>
> Sent by: platform-swt-dev-admin@xxxxxxxxxxx
> 11/26/2001 10:28 AM
> Please respond to platform-swt-dev
>
> To: <platform-swt-dev@xxxxxxxxxxx>
> cc:
> Subject: RE: [platform-swt-dev] SWTToolkit as AWT Peers
>
>
> Isn't the personal config stuff only AWT v1.1, though? There were
> a ton of
> changes to how the peers are managed in 1.2 and beyond...
>
> Or did I misunderstand something?
> -- Scott
>
>
>
>
> _______________________________________________
> platform-swt-dev mailing list
> platform-swt-dev@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/platform-swt-dev
>