+1 as well, a compliment of [1]. There are a number of standardized client architectures (like backbone) with significant followings, being able to "Wicketize" a live mockup written in a single would be powerful. Creating a standardized server environment to work with many of these platforms would be huge. But of course, backwards compatibility being what it is...
[1] http://markmail.org/message/bdv6nk7vdbv33tmj On Sep 19, 2011, at 8:22 PM, robert.mcguinness wrote: > +1 for what Juliano said...something in the lines of what backbone.js but for > Wicket...History API support (pushState, replaceState, onPopState) would be > "wicket-ed". > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/Ajax-in-Wicket-next-tp3824240p3825552.html > Sent from the Forum for Wicket Core developers mailing list archive at > Nabble.com. >
