You can just use the Annotation of a blip: http://wave-robot-python-client.googlecode.com/svn/trunk/pydocs/waveapi.document.Annotation-class.html
On 14 oct, 02:41, Joe Developer <joe.d.develo...@gmail.com> wrote: > On Tue, Oct 13, 2009 at 7:33 PM, ThomasWrobel <darkfl...@gmail.com> wrote: > > > Also, seeing as this would effectively just used as storage/ > > retrieving, would each user (/s client) effectively need to post a > > blank widget in a blip? > > There would be no reason for that as far as I can see.. > > > We could, I assume, use one widget for all the storage of the wave. > > But it would be nicer to keep the advantages of having one object tied > > to a blip. > > Well, presumably you would still need such a widget to view or modify your > objects, they would in this case also act as a container for data. I agree > that one could probably find more elegant solutions but at this point I am > not privvy to them. Perhaps you should seek out the author of say > SWFAnimator, a wave based collaborative swf animation tool. > > > > > On Oct 13, 2:25 pm, ThomasWrobel <darkfl...@gmail.com> wrote: > > > Ah, yes, that looks like it. > > > > Does the Wave store state changes for these key/value pairs in its > > > history automatically? > > Yes. > > Note that robots (or other clients) can alter and retrieve those key:value > pairs programmatically. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
