> Eelco .. I understand, and moreover in general versioning on ajax operation > is meaning less. > > But in some cases like tab operation would be nice, because from the user > point of view changing tab switch is like changing the page content. So > would be useful to let interact with browser back and fwd navigation.
We don't actually think it is meaningless. Just very hard for us to implement. We (or rather, Johan) did some work preparing the server side for this, and we have been talking about it a lot behind the scenes (yesterday even), but we probably will need a couple of weeks of intens work to really get this working. If we would be able to pull this off at all, which tbh isn't a certainty right now. > Looking on the Internet I found some interesting tricks [1] and [2]. > Basically that make use of a hidden iframe to store the history. Thanks. We were already aware of those techniques though. The main problems we are facing are: * Currently we don't assume pages are using ajax per se. We don't 'own' the browser, an we don't have a unified model of how ajax has to work. * We have to align the ajax versioning with our normal versioning, which is not easy. > Perhaps a solution to handle versioning for a generic ajax action could be > very complex. > > But a specific behaviour just to handle AjaxTabbedPanel versioning I think > it would not so difficult. > > I will make some experiment and let you know. If you up with something smart, please share! :) Cheers, Eelco ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
