|
No no no no...
If you generate source code, people *will* tweak
it. That's just a fact.
But it gets tiresome to see the same points
repeated over and over. This whole subject has been done to death in
eclipse.tools, where it belongs.
The only justification for having this thread in
platform-swt-dev is to either identify shortcomings in SWT vis a vis GUI
builders or to conclude there aren't any. I take it you are in the "aren't any"
camp. Are there any other points of view?
Bob
----- Original Message -----
Sent: Saturday, January 18, 2003 6:13
PM
Subject: RE: SWT History and Design
Decisions (WAS: [platform-swt-dev] AWT Toolkit using SWT (was: From Swing to
SWT))
No no no no...
If there isn't generated code, than the value of "tweaking" has
gone to nil. What are you going to tweak that you couldn't do easier
in the builder itself?
Because of that, and because you claim builders can
fairly go either way, I think that negates the argument for tweaking code as
well...
What
then, is the inherent value in munging the output (requiring round
tripping)?
--
Scott
There are GUI builders that generate
source code and those that don't (like yours). My feeling has always been
that round-tripping is a *requirement* and if you want to generate source
code then you open yourself up to having to round-trip from the source (or
object) code. However, if you don't generate source code you are free to
round-trip from whatever intermediate representation you have chosen. Either
way satisfies the requirement. One of them (the source code path) is much
harder than the other.
| 