[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
RE: SWT History and Design Decisions (WAS: [platform-swt-dev] AWT Toolkit using SWT (was: From Swing to SWT))
|
Must check out Conga...
Cg.
-----Original Message-----
From: platform-swt-dev-admin@xxxxxxxxxxx
[mailto:platform-swt-dev-admin@xxxxxxxxxxx] On Behalf Of Lane Sharman
Sent: Thursday, January 16, 2003 8:06 PM
To: platform-swt-dev@xxxxxxxxxxx
Subject: Re: SWT History and Design Decisions (WAS: [platform-swt-dev]
AWT Toolkit using SWT (was: From Swing to SWT))
It is so interesting how over time we come to a common knowledge space
about engineering principles. Many moons ago, I was looking at
controllers and widgets and said, ah hah! We need an adapter which
easily propagates the lifecyle, action and property set of a widget.
Thus was borne the adapter property in the base class of the Conga
widget set.
http://opendoors.com/conga/2.2/docs/javadoc/marimba/gui/WidgetAdapter.ht
ml
indicates the basic structure of the Conga adapter interface.
An adapter implementation will provide bi-directional association and
flow of messages between the widget adapted and the from the
presentation controller.
regards,
Lane
Christian Gruber wrote:
>... which is half the reason it feels so right to me... based on a
>SmallTalk GUI approach... hmmm.... yummy.
>
>Seriously, though. My previous e-mail about using adaptors should fit
>quite nicely, as it was developed for a similar system.
>
>Cg.
>
>-----Original Message-----
>From: platform-swt-dev-admin@xxxxxxxxxxx
>[mailto:platform-swt-dev-admin@xxxxxxxxxxx] On Behalf Of David Whiteman
>
>
>SWT originally was developed by OTI as an internal toolkit for use in
>building its VisualAge Micro Edition IDE. The SWT API evolved out of
>the widget classes found in VisualAge Smalltalk. At the time of its
>development, Swing was limping along at version 1.0, and OTI was able
>to build SWT quickly due to the fact that it was essentially a port
>from its Smalltalk work. I.e. I don't think the original intent was
>to develop a reusable externally available toolkit. But since it
>turned out so well, it seemed like something others would want: a good
>performing widget toolkit that used a mix of native and custom
>widgets.
>
>
>_______________________________________________
>platform-swt-dev mailing list
>platform-swt-dev@xxxxxxxxxxx
>http://dev.eclipse.org/mailman/listinfo/platform-swt-dev
>
>
>
--
Lane Sharman
http://opendoors.com Conga, GoodTimes and Application Hosting Services
http://opendoors.com/lane.pdf BIO
_______________________________________________
platform-swt-dev mailing list
platform-swt-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-swt-dev