As I have planned it at the moment there will be no need for the robot to remove participants. All waves in my application will be public. Including the possibility for public users to add all kinds of robots and gadgets to the waves. That will be very powerful but I hope it will not cause too much problems and mess.
On Jun 10, 8:19 am, RAVINDER MAAN <[email protected]> wrote: > An other point which may relate to this is that at present robot can not > remove participant.Any thought to deal with this issue? > > > > On Thu, Jun 10, 2010 at 6:10 AM, Anders <[email protected]> wrote: > > I was thinking of having one robot creating all the waves in my > > application, and each time a wave is created the robot adds the public > > participant to the wave plus one or a few robots to provide default > > functionality (such as support for emoticons). > > > So when a user creates a wave in my application, it's the one robot > > that always is the creator of the wave. And each time a participant > > tries to remove the public participant or any of the default robots in > > a wave, then the robot who created the wave gets informed about that > > through WaveletParticipantsChanged() and immediately re-adds the robot > > that was removed from the wave. > > > Anyone can remove all the other participants in any of the waves in my > > application, but since the public participant is always re-added > > immediately, nobody is blocked from any of the waves and I thought it > > would be nice to allow anyone to add or remove their own robots to the > > waves which would potentially provide for powerful capabilities in the > > waves. > > > I haven't checked if all these things are possible in practice but > > that's my plan at the moment. And I don't know all the details yet. > > For example is it possible to catch an event and then consume it > > before any action has taken place? Or when a robot receives an event, > > then the action has already happened. > > > On Jun 9, 8:05 pm, Nathanael Abbotts <[email protected]> > > wrote: > > > Yes - but the robot adding public would be able to be removed also, > > unless > > > it created the wave. > > > > On 8 June 2010 23:53, Anders <[email protected]> wrote: > > > > > Oh, now I discovered this: > > > > > class WaveletParticipantsChanged(Event): > > > > """Event triggered when the participants on a wave change. > > > > > I assume that it can be used for catching all cases when participants > > > > are removed from waves. That would be good enough. At least until more > > > > fine-grained control has been implemented which I saw is planned for > > > > the wave roadmap. > > > > > On Jun 8, 10:44 pm, Nathanael Abbotts <[email protected]> > > > > wrote: > > > > > If it helps - I'm working on a robot that you can use to create waves > > for > > > > > you, and it will re-add anyone that was removed, unless they remove > > > > > themselves. (This robot would have created the wave, so it cannot be > > > > > removed). > > > > > > On 8 June 2010 21:00, Anders <[email protected]> wrote: > > > > > > > I have started developing a wave application with public waves. One > > > > > > problem is that the Public participant [email protected] can be > > > > > > removed by anyone, and then the wave is no longer public! Not good. > > > > > > > Another problem is that anyone can remove robots from a public > > wave, > > > > > > which also is a problem. > > > > > > > I would like to have the waves public when it comes to writing to > > the > > > > > > wave, but not public when it comes to removing participants, such > > as > > > > > > the Public participant and robots. > > > > > > > -- > > > > > > 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]<google-wave-api%[email protected]> > > <google-wave-api%[email protected]<google-wave-api%[email protected]> > > > > > <google-wave-api%[email protected]<google-wave-api%[email protected]> > > <google-wave-api%[email protected]<google-wave-api%[email protected]> > > > > > > > . > > > > > > For more options, visit this group at > > > > > >http://groups.google.com/group/google-wave-api?hl=en. > > > > > -- > > > > 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]<google-wave-api%[email protected]> > > <google-wave-api%[email protected]<google-wave-api%[email protected]> > > > > > . > > > > For more options, visit this group at > > > >http://groups.google.com/group/google-wave-api?hl=en. > > > -- > > 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]<google-wave-api%[email protected]> > > . > > For more options, visit this group at > >http://groups.google.com/group/google-wave-api?hl=en. > > -- > Regards, > Ravinder Singh Maan -- 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.
