You’re forgetting another…
widget-adaptors to generic data types.
That’s quite practical, and is not an abstraction/wrapper the way
it’s usually meant by AWT folk. It’s specifically a channel between
data and SWT, and highly useful within a GUI builder. It sounds like Lana’s is somewhat like
that, but I’ll have to check it out.
Neither of the options that you mention are ones that I’d
consider. Specifically, I’d avoid
trying to tie AWT and Swing together. I
think an SWT-aware builder is what’s needed, regardless of whether such a
tool was also aware of AWT/Swing.
Regards,
Christian.
-----Original Message-----
From: platform-swt-dev-admin@xxxxxxxxxxx
[mailto:platform-swt-dev-admin@xxxxxxxxxxx] On
Behalf Of Bob Foster
Sent: Thursday, January 16, 2003 8:50 PM
To: platform-swt-dev@xxxxxxxxxxx
Subject: Re: [platform-swt-dev]
AWT Toolkit using SWT (was: From Swing to SWT)
These two or three threads inspired
by Lane's remarks seem excessively philosophical for this list. So far I have
seen two proposals that would make SWT more "GUI builder friendly".
- An abstraction layer over SWT and
AWT/Swing
- Support for AWT/Swing within SWT
Abstraction layers are not SWT-like.
I doubt you'll find much support for that.
AWT/Swing within SWT should be
supported for a lot of reasons, but this isn't one of them. This just makes SWT
friendly to Swing GUI builders, it doesn't provide a GUI builder for SWT.
Awhile ago I proposed adding (a
handful of) property getters and setters that would make widgets more beanlike.
(Forget the constructor thing; that's not an issue.) As long as objects can be
serialized to some sort of stream and reconstructed by reading that stream
USING THE EXTERNAL API, GUI builders have what they need.
