[Google Wave APIs] Re: Suggestions for Wave Gadget API

2009-11-01 Thread Andrew Red
I was thinking about this last night, and I thought just to restrict the information to the gadget to be anomous when the gadget loads, and only when the user interacts with the gadget (press a link or button) to make all the data available. The only problem with this is that the gadget could use j

[Google Wave APIs] Re: Suggestions for Wave Gadget API

2009-11-01 Thread antimatter15
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

[Google Wave APIs] Re: Suggestions for Wave Gadget API

2009-11-01 Thread David Nesting
On Sun, Nov 1, 2009 at 3:00 AM, pamela (Google Employee) < pamela...@gmail.com> 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 ca

[Google Wave APIs] Re: Suggestions for Wave Gadget API

2009-11-01 Thread cmdskp
Another solution is to alert the user before entering a wave that has gadgets that 'requireViewerId' to the privacy issue and allow them to view the wave with those gadgets disabled until they choose to activate them or edit the wave. Or disabling all gadgets until activated or wave edit. This w

[Google Wave APIs] Re: Suggestions for Wave Gadget API

2009-11-01 Thread Andrew Red
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 shou

[Google Wave APIs] Re: Suggestions for Wave Gadget API

2009-11-01 Thread pamela (Google Employee)
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 reas

[Google Wave APIs] Re: Suggestions for Wave Gadget API

2009-10-31 Thread Andrew Red
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?

[Google Wave APIs] Re: Suggestions for Wave Gadget API

2009-10-31 Thread pamela (Google Employee)
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 a

[Google Wave APIs] Re: Suggestions for Wave Gadget API

2009-10-31 Thread antimatter15
The online state is something that they restrict for security reasons just like how you can only see the online status of people in your contacts. I have state diffing implemented as a applicaiton library over the Wave Gadget API in my applications. On Oct 31, 5:53 pm, lstak wrote: > Hi, > > Bas