| RE: SWT History and Design Decisions (WAS: [platform-swt-dev] AWT Toolkit using SWT (was: From Swing to SWT)) |
|
You know, it’s funny, because when
you’re talking about XMLTalk generated code,
you make me realize that my definition of “code” is somewhat
limited, and in the terms of this discussion, there might be an approach that
would satisfy us both. I need to
think about it, and I’d like to see your tool when it’s ready, but
if you count an XML spec for laying out a GUI, and a spec for associating GUI
elements to data as code, even though it’s not compiled, then
code-generation meets resource file quite nicely. I think that’s what you were trying
to say before, but terminology was a bit of a barrier. Anyway, I look forward to seeing your
work. Good luck with the patterns
course. Regards, Christian. -----Original Message----- Sounds like I'm missing
my mark. Bummer. Well, annoy or debate, I gotta do one of them ;) [Thanks for the kind
words, btw] Can't see the tool yet --
not ready to show. Getting there, though. I've been low on free time lately,
prepping to teach a patterns class at Wrt the generated code, I
plan to have at least two generators that I'll write -- one that generates VAJ
like code, and one that generates XMLTalk or something like BML or the
long-term persistence stuff that Sun does. Not that I recommend the
resource file approach, but I wanted to show it was equally as easy to do.
(Note that I had been planning to do this before this thread, though this
thread has confirmed that folks are interested in something like that.) My hope is that as people
see the generated code, they'll give me feedback, or perhaps create alternative
code generators. A kind of community optimization, if you will... -- Scott |