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 you've got 10 users on a wave, and a robot gets added, and some of the users have a folder, and others don't, what happens? Robots aren't extensions, they're just participants, AI's or Agents that act the same way that any other participant in the wave could, but automatically, and without human intervention. Just like I can't drag one of your waves into one of your folders, a robot can't move a wave into one of your folders, because they aren't the Robot's folders, they're Your Folders. Giving a random robot access to my folders just because I happened to have opened a wave that they were partipating in would be a huge security hole, and I wouldn't want to allow that. Tags are a different matter, since they are assigned to the wave, not bound to a user. Neither the Java API nor the Python API appears to currently support adding tags to items, though it seems reasonable that they could. I'd be worried about robot authors misusing them, but it seems like something that should make it into those APIs at some point in the future. Gadgets are closer to the standard definition of "extensions" but they're still bound to the wave, not a particular user. Again, granting gadgets permission to muck about with my folder structure just because I happened to open a wave they were attached to would be a bad idea. This would be like allowing attachments to auto-execute themselves when you open an email, and any security expert can tell you why that's a bad idea. Again, I think a third type of "API" would be necessary to support the kind of extensions you're talking about here. Either of the existing extension APIs would cause serious security flaws if they were to be allowed to move things around in your folders, or create new waves. On Mon, Nov 16, 2009 at 11:08 PM, Olreich <olre...@gmail.com> wrote: > 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 and allow them to be more full- > featured applications. Then again, since robots are essentially > extensions, maybe add the functionality only in robots that are part > of extensions. > > On Nov 17, 1:58 am, Adam Ness <adam.n...@gmail.com> wrote: >> I don't think Robots could ever be expected to be capable of moving >> items into folders, since they're just another Participant on the >> wave, and the folders belong to other participants. >> >> Possibly a Gadget API would be a better place for this, or maybe a new >> client plugin API, to allow users to write their own plugins that >> don't use the protocol at all, but just the client. >> >> On Sun, Nov 15, 2009 at 2:07 AM, pamela (Google Employee) >> >> >> >> <pamela...@gmail.com> wrote: >> > Hi jhb - >> > A wave can only be in one folder, and robots do not currently have the >> > ability to move wave into a folder (or assign tags, a related action). >> > Please file a feature request for folder manipulation here: >> >http://code.google.com/p/google-wave-resources/issues/entry?template=... >> > - pamela >> >> > On Fri, Nov 13, 2009 at 11:30 PM, jhb <barr.j...@gmail.com> wrote: >> >> >> Is there a way to manipulate the location of a wave from a user's >> >> inbox to robot created or previously created folders. Also, can a >> >> wave be in multiple folders? >> >> >> -- >> >> >> You received this message because you are subscribed to the Google Groups >> >> "Google Wave API" group. >> >> To post to this group, send email to google-wave-...@googlegroups.com. >> >> To unsubscribe from this group, send email to >> >> google-wave-api+unsubscr...@googlegroups.com. >> >> For more options, visit this group at >> >>http://groups.google.com/group/google-wave-api?hl=. >> >> > -- >> >> > You received this message because you are subscribed to the Google Groups >> > "Google Wave API" group. >> > To post to this group, send email to google-wave-...@googlegroups.com. >> > To unsubscribe from this group, send email to >> > google-wave-api+unsubscr...@googlegroups.com. >> > For more options, visit this group at >> >http://groups.google.com/group/google-wave-api?hl=. > > -- > > You received this message because you are subscribed to the Google Groups > "Google Wave API" group. > To post to this group, send email to google-wave-...@googlegroups.com. > To unsubscribe from this group, send email to > google-wave-api+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-wave-api?hl=. > > > -- You received this message because you are subscribed to the Google Groups "Google Wave API" group. To post to this group, send email to google-wave-...@googlegroups.com. To unsubscribe from this group, send email to google-wave-api+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-wave-api?hl=.
