That's the main difference between GWT and Wicket - so if you really NEED it all client-side, then use GWT.
As far as your tab problem - sure, you can do this with Wicket. The default (I believe - it's been a while since I used the tabbed panel) is to load the other tab via ajax. But if you want some tabbed panels to preload everything, just use jQuery or dojo, etc to make that tabbed panel - IOW, output all of the markup with Wicket and add the tabs as a JS effect. It eliminates the server callbacks. Make this a reusable component and you can use it wherever you want it. Remember not to prematurely optimize. Code maintenance costs more than operational costs. -- Jeremy Thomerson http://www.wickettraining.com On Wed, Apr 29, 2009 at 10:06 AM, kan <kan....@gmail.com> wrote: > Is there any easy way to make wicket applications like GWT? I mean to > make a "heavy client side", so it will allow easy manage data > pre-loading and requests (AJAX too) caching. The aim is to minimize > amount of web-server requests. > Say, I have several tabs on a page. Some tabs should have all data > pre-loaded and switched immediately (no requests to server). Some tabs > are "big", so they do an AJAX request for data, but only if a tab is > opened first time. > > -- > WBR, kan. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
