semanticb...@appspot.com is a robot that takes all subsequent blips in
a wave and highlights the Keywords as found by the OpenCalais API.
I'm waiting for access to tags to add automated tagging capability.
Also, I am looking to add access to the AlchemyAPI per a request.
I set up public wave to tr
This is not a bug, you are using the wrong constructor. If you have a
label, you need a defaultValue
public FormElement(ElementType type,
java.lang.String name,
java.lang.String defaultValue)
instead of
public FormElement(ElementType type,
>> 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.
>
> > >>
in the
> >> Inbox/All/Trash views.
> >> What do you think?
>
> >> On Sun, Nov 15, 2009 at 11:07 AM, pamela (Google Employee) <
> >> pamela...@gmail.com> wrote:
>
> >>> Hi jhb -
>
> >>> A wave can only be in one folder, and robots do
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 emai
Is there a way for a root to determine the participant who added it to
a wave?
--~--~-~--~~~---~--~~
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-api@googlegroups
hat (so you can authenticate the user
> explicitly).
>
> David
>
> [1]http://code.google.com/p/google-wave-resources/issues/detail?id=344
>
> On Thu, Nov 5, 2009 at 1:36 PM, jhb wrote:
>
> > I am making a robot that uses a 3rd party service that requires a
> > licen
I am making a robot that uses a 3rd party service that requires a
license key to get data back to the robot. What is the best way to
store a user's password or key so they are not required to
continuously reenter it. The service requires a license key for every
REST request, there is no login, s