That's actually accurate, as Martin already explained, Wicket has no provisions for client side Java based programming.
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. On Wednesday, October 26, 2011 10:18 PM, "Andrea Del Bene" <[email protected]> wrote: > That's right but why they didn't include Java among languages you can > use to program on client side with Wicket. It's a mystery! > > On Wed, Oct 26, 2011 at 10:02 PM, Andrea Del Bene<[email protected]> > > wrote: > >> You missed the funniest row: "UI programming on client-side". What does it > >> mean "Java, Javascript" for GWT and Vaadin and just "Javascript" for > >> Wicket? > >> Does it mean that GWT and Vaadin run bytecode inside browser? Did they > >> (re)invented applets :)? > > They (actually GWT, Vaadin is reusing it) compile Java to JavaScript. > > I.e the developer writes only Java and the framework does the rest. > > > > > > > > > --------------------------------------------------------------------- > 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]
