I haven't played much with gadgets, but if they could do a XMLHttpRequest(), they could tell a server when a user is on the wave...
It's just an idea for a back door, it should be easy to stop Andrew On Sun, Nov 1, 2009 at 9:00 PM, pamela (Google Employee) < pamela...@gmail.com> wrote: > I should make clear that there is a distinction between knowing when a > participant is inside the Wave client generally (as indicated by the green > dot) and actually viewing a particular Wave. The Wave client does not > provide any indicator when a participant is simply viewing a wave, for > privacy reasons. > > It is possible for gadgets to figure out who is viewing a wave currently, > as gadgets can change the state of a Wave in view mode, but we expect that > we may enforce that gadgets can only change state when the entire blip is in > edit mode. > > The general idea is that the Wave client should not reveal whether a user > has viewed a Wave, but the Wave client does reveal the fact that they are > currently logged in, and we may find a way to expose that in the API. > > Hope that makes sense. > > - pamela > > On Sat, Oct 31, 2009 at 11:07 PM, Andrew Red <andrewr...@gmail.com> wrote: > >> Could the first one be achieved by inserting a gadget, that has some >> javascript which changes data on the wave say every second or so, and if it >> stops changing the data, that person has stopped viewing the wave, that way, >> each gadget knows which users have the gadget open... >> >> Do I make any sense? >> >> Andrew >> >> >> On Sun, Nov 1, 2009 at 2:41 PM, pamela (Google Employee) < >> pamela...@gmail.com> wrote: >> >>> Regarding online presence - other developers have expressed their desire >>> for that here: >>> http://code.google.com/p/google-wave-resources/issues/detail?id=257 >>> >>> Regarding diffs - I can see the desire for that, and we have discussed it >>> on the team. Feel free to file a feature request. >>> >>> You may want to ask antimatter15 to share his diffing library or general >>> technique, as well. >>> >>> - pamela >>> >>> On Sun, Nov 1, 2009 at 8:53 AM, lstak <luc.stakenb...@gmail.com> wrote: >>> >>>> >>>> Hi, >>>> >>>> Based on some first gadgets I build, it would be useful if the Wave >>>> gadget API would support: >>>> >>>> - Online presence of participants in the wave. Currently you can only >>>> see who is a participant, but not if they are in the wave >>>> - the stateCallback provides the delta which caused the state change. >>>> This is useful when the Shared state is a large object and you only >>>> want to update a gadget based on the delta. >>>> >>>> e.g. >>>> >>>> function stateChanged(state, delta) { >>>> // state is the full state >>>> // delta is the changed part of the state >>>> } >>>> >>>> setStateCallback(stateChanged); >>>> >>>> >>>> Are there more developers who would find this useful? >>>> >>>> >>>> >>> >>> >>> >> >> >> > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Wave API" group. To post to this group, send email to google-wave-api@googlegroups.com To unsubscribe from this group, send email to google-wave-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-wave-api?hl=en -~----------~----~----~----~------~----~------~--~---
