Sorting is OK. Provided you download all data in a table at once, instead of paging. If you page, you still need at least one roundtrip to the server.
The shopping cart could never work properly, IMO. It'd need to make a server call in order to find out if and what products are on stock, and how many. Then it would need to check the prices right before each total price calculation. Then it would need to look for discount info. Then ... Of course I'm exagerating, but my point is that you'd end up with many more roundtrips than if you'd execute the logic on the server. I'm new to wicket (very new, that is - I just started my learning app today), but we did develop web apps on a non-Java platform for the last almost seven years. Although we heavily use Javascript (not yet Ajax) to provide a nice and friendly UI, and something Ajax-alike but built before XmlHttpRequest was part of the W3C body of recommendations, we came to the conclusion that it is best to run the logic on the server in maybe 99% of the cases. Therefore it is my opinion that there's no point in working a lot on making canned or converted or generated Javascript available for the client, besides the standard Javascript required by components and whatever there is needed to support Ajax. Even if a generic mechanism for such a thing would be built, it would be used in a very small fraction of all projects done with wicket. Plus, given the variability of such projects, the mechanism would probably be as nice to use as JSP or PHP compared to Wicket. So IMO this would be a waste of time. (And no, the platform we were working on was not PHP, it was something proprietary. Thank God that we probably will soon drop it.) br, flj Korbinian Bachl wrote: > > possible ideas: > > - a shoppingcart that works 100% in the browser if possible, else degrades > gracefully to the well known server side > > - sorting logic of lists in backendapplications (e.g: sort by name > beginning > with "B*" ... so fancy excel stuff etc.) > > i like the idea, however i have no clue if it could be done... > > -- View this message in context: http://www.nabble.com/Wicket-%2B-java-%3Ejavascript-compiler--tf3517350.html#a10954077 Sent from the Wicket - Dev mailing list archive at Nabble.com.
