Hi, Assuming that there is a good JS library for managing the history events, what should Wicket do ? I guess the best reliable solution is to store the pages as we do now for non-Ajax requests.
The problem is that this way the disk store will be filled up much faster. The page will be stored only if it is dirty, i.e. if there are changes in its tree. On Fri, Jul 26, 2013 at 1:00 PM, Martin Grigorov <[email protected]>wrote: > Hi, > > > On Fri, Jul 26, 2013 at 12:48 PM, Hendy Irawan <[email protected]> wrote: > >> I wonder if Wicket 6/7 has or planned for good history API support, i.e. >> navigable ajax updates a la Twitter/Facebook? >> > > It will be very useful if we extract use cases for this functionality. > > >> >> If not then I'd like to propose... It'd make Wicket not only very relevant >> but a breakthrough in a *post*-HTML5 world. >> >> [~mgrigorov] responded: >> >> > Do you know of a good JS History library ? >> > All I have tried have issues for different browsers. >> >> What I ever used is Backbone. Which is a great all around library. >> >> Snippet from http://backbonejs.org/#Router : >> >> <blockquote> >> Web applications often provide linkable, bookmarkable, shareable URLs for >> important locations in the app. Until recently, hash fragments (#page) >> were >> used to provide these permalinks, but with the arrival of the History API, >> it's now possible to use standard URLs (/page). Backbone.Router provides >> methods for routing client-side pages, and connecting them to actions and >> events. For browsers which don't yet support the History API, the Router >> handles graceful fallback and transparent translation to the fragment >> version of the URL. >> </blockquote> >> >> Breadcrumb components would benefit greatly from History API support (and >> is >> probably its main use case). >> >> Although any parameterizable page will benefit from this. For example >> we're >> developing an analytics app so the parameters include date range, >> precision, >> and selected sections. Those can be encoded in URI. Although while >> selecting >> these things we immediately perform AJAX updates, with bookmarkable URI >> it'd >> great. So the page stays "stateless" instead of stateful. Just like how >> Google Analytics does it. >> >> History API libraries include: >> >> 1. http://backbonejs.org/#Router >> 2. https://github.com/browserstate/history.js/ > > > The second one is one of those which I have tried and didn't like. It > behaved differently than native History API. > > http://tkyk.github.io/jquery-history-plugin/ - this is the one we use in > our app at the moment but its maintainer stopped supporting it. > > >> >> >> I also created a ticket at >> https://issues.apache.org/jira/browse/WICKET-5290 > > > I think there is a ticket about this already. > > >> >> >> Hendy >> >> >> >> -- >> View this message in context: >> http://apache-wicket.1842946.n4.nabble.com/Wicket7-History-API-support-for-navigable-AJAX-pages-components-tp4660502.html >> Sent from the Forum for Wicket Core developers mailing list archive at >> Nabble.com. >> > >
