It does work, and many robots do so, but there are some bugs filed about
cases where it does not work. For example:
http://code.google.com/p/google-wave-resources/issues/list?can=2q=setfieldcolspec=Stars+ID+Type+Status+Priority+Milestone+Owner+Summary+Internalcells=tiles
I think currently communicating from robot to gadget is not possible?
The gadget.setField does not change the state of the gadget in my
tests.
Regards, Jacco
On 12 nov, 16:48, just marvin marvin.greenb...@gmail.com wrote:
It occurs to me that since you'll need a bot and a gadget, you could
It occurs to me that since you'll need a bot and a gadget, you could
just have the bot add the gadget(s) to the wave. Then you just need
to add one thing to the wave and you'll know you have the correct
environment for the gadgets.
--
You received this message because you are subscribed to the
Thanks for comments, all. Now suppose I want the gadget to receive a
state change notification every time the state has changed. (I
don't want to have to continually poll an external site to see if
something has changed; I want a callback notification.)
Is it true that:
1) There is no good way
1) You are correct. The callback mechanism provided by gadget library is
only connected to the wave server.
2) Yes. When robot changed gadget states your gadget will receive the
callback.
Austin
On Wed, Nov 11, 2009 at 12:48 PM, rgibson rgib...@astro.washington.eduwrote:
Thanks for
Makes sense. Is there any way to get the state change callbacks
_without_ using the robot to manage the shared states?
(And without writing my own communication protocol that is, at the
bottom layers, just polling an offsite server?)
Thanks,
Rob
On Nov 11, 12:54 pm, Austin Chau (Google
Makes sense. Is there any way to get the state change callbacks
_without_ using the robot to manage the shared states?
I don't think so. To get a callback you either need
- someone (robot or ordinary user) to join or leave the Wave,
- or someone (robot or ordinary user) to change a gadget
If you end up using a Java robot and a static object variable -
remember to ensure you synchronize on it or use a synchronized
object. Otherwise, simultaneous Servlet requests can end up changing
the shared static object's value before each request is done with it.
On Nov 11, 10:05 pm, Niels H.
