Please correct me if i'm wrong but it looks like 1.5 and 1.6 wicket will
continue to use behaviors to work with ajax events driven by user events or
timers. In the real world a lot of my ajax needs occur when i need to push
back page state changes and don't want to write 100 lines of code with
custom javascript just to do something that could be provided by the API.
Hopefully I'm just ignorant of the existing elegant solution.
onClick(AjaxRequestTarget target){
//disable some controls
...
doWorkThatTakesSomeTime();
// update some label with current status
...
doSomeMoreWork();
// append results to an unordered list
....
// update labels with final results and enable controls
}
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Wicket-Ajax-direction-and-roadmap-regarding-push-like-updates-tp4351890p4351890.html
Sent from the Users forum mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
