HI, On Sun, Jul 24, 2011 at 7:14 PM, stephanos2k <stephan.beh...@googlemail.com>wrote:
> Thanks a lot for your post! :-) > > I looked at what you suggested, are there any hints/tips on how to > integrate > such functionality with Tapestry? > > Well it's obviously not trivial. > I suppose a JS script (like history.js) should receive and handle + request > and 'call' Tapestry to actually do the rendering. But I can't seem to come > up with a good way on how to 'squeeze' the library in-between. > > Basically the short example here <https://github.com/balupton/History.js> > relies on rendering JSON in different states (all the logic is based on states). Using tapestry you can make a GET request and return a JSON response. So that's maybe the simplest scenario. More complex scenario would be that you integrate zone's in the whole picture. This one's tricky and I wouldn't suggest much at the moment. Maybe one idea would be: when you make an ajax request using an EventLink you somehow put the name of the action (or some other ID) in the URL and also the context and the parameters in the URL (basically all info that the EventLink carries), so if you bookmark and make a GET you make an Ajax call using those parameters and update the corresponding zone reconstructing the link that triggers the update. I'm not sure if this is a good idea, but as I said generalizing the functionality using zones is not trivial. Cheers Dragan Sahpaski > Cheers > > -- > View this message in context: > http://tapestry.1045711.n5.nabble.com/Ajax-Navigation-tp4627764p4628324.html > Sent from the Tapestry - User mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >
