This is the code I use for my state diffing http://antimatter15.com/wp/2009/08/wave2-a-higher-level-wave-gadget-state-api/, rather than telling if something has been changed or added for everything that is changed or added (I made this for very data- intensive gadget and since the diffing needs a copy of the old data as well, I tried to keep the size of the backups to a minimum). To use it, just call wave2.statechange() from within your on state change event handlers and use wave2.listen("substring for what to listen for", callback function) and the callback will be called every time something that begins with the certain substring changes.
On Nov 1, 9:16 am, David Nesting <[email protected]> wrote: > On Sun, Nov 1, 2009 at 3:00 AM, pamela (Google Employee) < > > [email protected]> wrote: > > in view mode, but we expect that we may enforce that gadgets can only > > change state when the entire blip is in edit mode. > > If the motivation behind this is to ensure privacy, keep in mind that the > gadget can always record this information to their own local storage, or you > can use traditional web bugs within the gadget. The user just needs to edit > one blip with one of these gadgets to get all of their view history linked > to their identity. > > David --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Wave API" 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-wave-api?hl=en -~----------~----~----~----~------~----~------~--~---
