Bryan, History is implemented with history tokens, which is the portion after the '#' in the URL. This is not sent to the server and is used client side only. So while these are URLs, they're special and should work for the scenario you described.
Fred On Fri, Jul 10, 2009 at 4:05 AM, twittwit <[email protected]> wrote: > > anybody has any idea on this ? > > > On Jul 10, 1:29 am, imgnik <[email protected]> wrote: > > hi all, > > > > i want to implement history in my motion chart app. > > and basically i want to have a stack of history items that comprise of > > different motion chart. so basically as i have more motion chart > > ( different ones) my history stack increment and i can go forward and > > backward with the motion chart changing to the next and previous chart > > respectively. ( and hopefully in the same state where it was left in) > > but i really donno how to implement the history management for this? > > > > can someone advise me? i know the distribution contains example of > > history management. but those are mere hyperlinks. will it be the same > > for bigger widget like motion chart? or even maps? > > > > cheers > > bryan > > > -- Fred Sauer [email protected] --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
