I imagine that we could implement robots or robot-like agents that
participate on the Wave on your behalf, instead of as an additional
participant. The API would be very similar to robots, but there would likely
be additional UI for users to confirm that these robot-like agents could act
on their b
Odd, the behavior must have changed, when I was working with it a week
ago, It wasn't creating new wavelets, but I was actually using
RootMessageBundle.createWavelet(participants), so maybe they're not
the same. It definitely points to an issue with the documentation, it
should be clearly spelled
Also, wavelet.createWavelet(participants, dataDocumentCallback); in
java doesn't create a new wave, it only creates a new wavelet inside
an existing wave.
Adam Ness
On Tue, Nov 17, 2009 at 12:52 AM, Olreich wrote:
> I agree with almost everything you said. Just one quick point on the
> Robot's c
But what if I read a wave which you added that gadget or robot to, and
I don't want that gadget or robot to automatically manage my folders?
On Tue, Nov 17, 2009 at 12:52 AM, Olreich wrote:
> I agree with almost everything you said. Just one quick point on the
> Robot's creating waves:
>
> wavele
Actually, there's no way in the current Robot API to create a wave.
Robots can only respond to new blips on an existing wave.
Also, because the robots operate within waves, allowing Robots to
assign waves to folders is problematic, because it's not clear which
user's folders receive the wave. If
