did anyone ever answered this? Vaadin provided us with complete set of advanced components and with patterns to follow to build application UI. Wicket in that sense provides only basic elements. If I was to compare the two, it would be that Wicket is on the same level as GWT (framework) while Vaadin (while using GWT) is taking it yet another level up (solution).
HTH, Jan On Feb 23, 2011, at 10:57 AM, Anton Matheis wrote: > > Hi magnolians, > > i understood from your talk why you use vaadin instead of GWT. > Just to follow the rationale: what were the arguments against wicket? > > > Thanks, > Anton > > > ---------------------------------------------------------------- > For list details see > http://www.magnolia-cms.com/home/community/mailing-lists.html > To unsubscribe, E-mail to: <[email protected]> > ---------------------------------------------------------------- ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
