That's why I don't like a statement like "UI programming on client-side
with Java". You are just giving the impression of programming your GUI
in Java, but in the end is a lot of JavaScript, and this doesn't help
code maintenance as pointed out by Eelco .
I know that GWT is good at "mimicking" desktop style but you can do it
also with Wicket with the right components.
Ugh, I mean 'just do that in JavaScript'
On Thu, Oct 27, 2011 at 7:07 PM, Eelco Hillenius
<[email protected]> wrote:
To be honest, I don't think the comparison matrix is that bad. I would
consider a framework like Vaadin over Wicket if all I wanted a typical
desktop style only (menu bar, content frames + layout manager, fancy
widgets) only type of application, what they call "application
oriented", especially if it would benefit a lot from client-side UI
management.
Or just do that in Java. I can tell you from experience that
developing (and e.g. debugging!) with GWT is painful on many different
levels. I like how Vaadin markets itself, what it's goals are etc, but
I can't imagine not stumbling into the same kind of hassle that comes
with developing with GWT. Might even make it worse, as it's yet
another abstraction over it.
My2c,
Eelco
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
