i just dont see the point of wrapping a page made up of gwt components in wicket wrappers. the *entire* front end has to live on the frontend in order for the application to work offline...so whats the point? anyways my two cents.
cheers, -igor On Fri, Feb 19, 2010 at 9:43 PM, Eelco Hillenius <[email protected]> wrote: > On Fri, Feb 19, 2010 at 9:30 PM, Igor Vaynberg <[email protected]> > wrote: >> having data only on the client will not help you unless you also have >> behavior. these kinds of apps are really only feasible when you use a >> clientside framework like gwt. > > Any components you write wouldn't use the typical client/ server > interaction that regular Wicket components do, but I don't see why you > wouldn't be able to write a wrapper around this functionality so that > at least you'd be able to use such functionality within a Wicket > application. > > FWIW, I'm currently coding in GWT, something I really looked forward > to, because like most coders I like change, but man, I miss Wicket's > productivity. It's not a bad framework, but imho it's hard to beat > Wicket when it comes to churning out and integrating components. > > 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]
