You could look into the Html5' s local storage mechanism for saving your application's state before a reload happens. You can also decide what part of the state you want to save, thus reloading gracefully the most important parts of your application and letting the user do the needed actions to reach at her previous state (i.e in a tree you could just load the tree at its initial state and have the user manually open the nodes to her previous selection ... )
As you mentioned your approach is a lazy one, and in ajax refresh is less and less used, but the application should not try to teach users new ways to interact with the browser and if possible handle the history events in a non catastrophic way ... Cheers! -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
