[
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))
|
Statefulness can be provided in other ways as well, but I'll buy that
that is an automatic strength of resource files. However I don't see it as a big
deal to add to apps that use static-generated code.
Of
course we could get into a self-modifying code discussion,
muihahahahahahahahaha!
--
Scott
Scott Stanchfield wrote:
RE
"Especially if the tool is one that generates code, I think you have
to count on the fact that there will be a need to tweak
it
Why a "need"? You're implying that if it
generates resource files that noone will ever need to tweak them,
countering your own first sentence...
What makes a resource file approach so darn
powerful? Noone has yet to answer
this...
A
resource file is a data file. Once the data file is read and placed into a
stateful condition, it can be modified according to the protocols provided at
runtime, eg, the user resizes the panel, drops some element into the
Presentation, sets up a new color scheme, the application adds some widget to
the Presentation. State is then re-persisted. This is incredibly powerful for
GUIs at runtime allowing for GUI statefulness and
evolution.
-Lane
