Thanks Damien, No, unfortunately plugins are not an acceptable solutions. I feel nevertheless that there should be a way to communicate between frames. Preferably without JSNI?
On 5 Feb., 18:48, Damien Picard <[email protected]> wrote: > If you can accept browser's plugins in your project, take a look at Google > Gears. With this, you can take a better control of locally stored data and > much more ... > > http://gears.google.com/ > > 2009/2/5 asdf_asdf <[email protected]> > > > > > His, > > > Read some posts in the group and still wondering if implementing such > > a scenario would be possible with GWT: > > A web page is served which contains two frames - one for presenting > > the stuff and the other one to constantly make requests to the server > > (a timer) and maintain latest of data (lots of objects, so only the > > new data is added / removed and not everything at once). > > > Is there a way for one frame to get a reference to the other where the > > current data resides? The obvious benefit would be that when user > > clicks a link and goes to a different page the data is still in the > > other frame and there is no need to load everything over again. Has > > someone maybe already done that or experienced a similar challenge? > > > That's my view on the problem. But maybe there can be another way to > > retain pieces of working logic and current data without frames when a > > user jumps to physically distinct html page. > > > Many thanks, > > Denis --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
