> Can you expand on your vision for this? The use case is creating waves to collaborate with students and other researchers and then add content into those waves using a bookmarklet.
In fact, such functionality already exists in drop.io, and it's very useful there. I keep such bookmarklets in a bookmark folder on my bookmark toolbar, so I can add things drops with a single click. But I'd prefer using Wave for this rather than drop.io because of the better permission and sharing features, and because of some other robots that I'm using. (Actually, some of the other features in drop.io, such as RSS feeds and a per-wave E-mail address would also be very useful.) > Seems like it may be something > worth exploring for a future version of the service (or something that could > be built via the Robots API and App Engine). Well, yes, in principle one could build a robot for this. The robot would add a bookmarklet to the wave that people could then drop to their browser, and it would handle adding new stuff to the wave. However, I think this is really core functionality that should be in every wave. Tom -- 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.
