[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [platform-swt-dev] From Swing to SWT
|
Scott Stanchfield Friday, January 17, 2003 6:20 AM
> How long does it take to program a UI? The design/layout is really
> the hard part. Once you learn a UI toolkit, programming UIs is
> really pretty trivial.
I suspect we have very different definitions of "programming," "UIs,"
or both.
_The_ most difficult part of coding any non-trivial UI (i.e. one which
is large, or is part of a larger application) is dealing with
* (code-centric) all the [event, context] tuples which can arise
* (user-centric) all the strange and wonderful things users can try to
do with the UI, and when they can try to do them
This is why unit testing is so important, thus why test automation is
so important, which is why I find it so distressing that there are
several Java-based, JUnit-integrated GUI/test automation packages for
AWT users, but none for SWT.
IMHO *this* is SWT's great weakness at this time. By contrast, once
you learn a UI toolkit, _layout_ is really pretty trivial.
