netsql wrote:
I would say that key for any "new" framework is that it has to default
to client side rendering of ui. DHTML/Ajax ... or others ;-)
And then as option be able to do server side generated UI.
What does that really MEAN though? For instance, take the common form
controls we all know and love... what does it really mean for them to be
rendered client-side and where does DHTML/Ajax fit in?
I think in discussing things like this we need to be careful not to
simply succumb to buzzword-itis. Many people view JSF as the future,
and to the best of my knowledge the default widget set (or whatever the
correct term is) looks very much like today's UI widgets and does't
require DHTML/Ajax. I recall hearing of JSF components that take things
further and DO use those things, but it isn't a requirement of JSF as I
recall.
That being said, I definitely DO think there is a place for those
things, and I think once people come to the conclusion that scripting is
good and offloading some of the work to the client is good, we'll enter
a new age of much more robust webapps. Some of us are doing those
things today and are quite happy about it (as are our clients who love
the things we produce). But if these things are *required* by a
general-purpose framework, I think it will turn a lot of people off, at
least for a time.
Frank
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
