I guess the other thing we are forgetting is the potential for one of
wave's greatest feature - playback.
The possibility is there to also have playback for robot actions on a
user's waves & folders, etc. Since they could all be performed
through the API, they could be rolled back easily by the u
There are many interesting ideas raised by considering robots as tools
to act on a users behalf or in concert with them.
With respect to folder management, I do not see any problem with a
robot requesting movement via the API of waves into or between a
user's folders (deleting can be handled by mo
Robots, on Wave at least, seem to be intended to be participants in
the wave. Thus, Robots that operate on behalf of the user would be
confusing. However, there is already a system in place that acts on
behalf of the user, and that is Extensions, which are intrinsic to a
user, rather than a wave. T
This is also useful from a semantic web point of view which is why I
made the request. Using a unique ontology or webservice like
OpenCalais, documents that are co-created could be tagged easily as
well as categorized, the tags are easy to get as well as a general
area or topic, using this informa
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
Have you tried it recently? Because every time I use it it creates a
new wave. And I try it again...and it still creates a new wave. The
Python version might create a new wavelet inside of the wave like it's
supposed to, but the Java API most certainly creates a new wave.
To clarify, I was speakin
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
I agree with almost everything you said. Just one quick point on the
Robot's creating waves:
wavelet.createWavelet(participants, dataDocumentCallback); in Java
or
robot_abstract.NewWave(context, participants) in Python
It is possible, as Robots are indeed full participants in the system
as if t
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
The problem is that Robots can create a mass of waves, but can't
organize it very well for the user, so the user wouldn't want a robot
to do anything outside of the wave, but rather operate entirely
within. Allowing robots to organize themselves would be expand them
outside of a wave-by-wave basis
Lol, I just submitted a feature request for that yesterday xD
http://code.google.com/p/google-wave-resources/issues/detail?id=462
On Nov 17, 1:03 am, jhb wrote:
> Thanks for the discussion. I created a feature request and added some
> of the ideas discussed.
>
> http://code.google.com/p/google-
Thanks for the discussion. I created a feature request and added some
of the ideas discussed.
http://code.google.com/p/google-wave-resources/issues/detail?id=469
On Nov 15, 2:19 am, Bálint Kriván wrote:
> Well, it's a good idea. Maybe one could "star/highlight" particular tags
> with a style
14 matches
Mail list logo
