Hi. The original link I sent:
http://codinginparadise.org/projects/dhtml_history/README.html Had callbacks as well. In other words, your application would log history "waypoints" where each waypoint represented a state change in the application. These waypoints would consist of a name for the waypoint as well as a set of data that could be used by the callback to re-construct the critical aspects of that state of the application. When a user clicked the back button, the callback would get triggered and passed the data appropriate to reconstruct the state of the application. I can envision many scenarios where re-constructing state would be hideously complex. For tabs or something similarly simple, it would be totally doable. Desktop applications for the most part don't have much application state (anyone else an Opera fan?) but they pretty regularly have control z for edit rollbacks. ------------>Nathan > -----Original Message----- > From: jquery-en@googlegroups.com > [mailto:[EMAIL PROTECTED] On Behalf Of Sean Catchpole > Sent: Thursday, April 26, 2007 9:33 PM > To: jquery-en@googlegroups.com > Subject: [jQuery] Re: Ajax application history > > > Nathan, > > A long time ago I made a simple proof of concept script on this: > http://www.sunsean.com/Jistory/ > > ~Sean >
