2 additional options: - Have robot insert a gadget, specify config in gadget, then delete gadget. See embeddy article: http://code.google.com/apis/wave/articles/embeddy.html
- Use info after the "+" in the robot address ([email protected]<bla%[email protected]>). Emaily sample does that: http://wave-samples-gallery.appspot.com/about_app?app_id=46003 - pamela On Sat, Jan 16, 2010 at 10:06 AM, qMax <[email protected]> wrote: > You may put configuration for robot in root blip before adding it. > The same way as you issue various commands to robots. > A good scheme/practice is to enclose parameters/commands/configs in > square brackets with keyword, like: > [Foo: parameters fopr foobot] > > When robot added it has access to root blip and may copy its config > into data document or somewhere else, > and remove it from blip content. > > On 13 янв, 21:25, Ojii <[email protected]> wrote: > > Is it possible to make a robot configurable? For example if the robot > > is added to a wave you have to configure that robot? If so, how do I > > do that? > > -- > 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. > > > >--
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.
