Woot, I also have a robot to contribute to this thread- [email protected].
(I guess we've all decided that gadgets development is simple enough
to be done in wave, or atleast the small debugging gadgets).

You can see gadgitty in action here:
https://wave.google.com/a/wavesandbox.com/#restored:search:with%253Agadgitty,restored:wave:wavesandbox.com!w%252Bja1pKz86C

You put the XML in the blip, and each time you submit the blip, it
outputs the gadget XML at a new (non-cached URL), and inserts a gadget
with that URL at the bottom of the blip (deleting the gadget that was
previously there).

The advantage of this technique is that you can collaboratively edit
the gadget.
That sample wave is actually from a demo where I created the gadget
from scratch while alternating between two different users and showing
their waves update simultaneously.

I will add Gadgitty to the samples gallery in a few weeks.

- pamela

On Fri, Jan 29, 2010 at 9:19 PM, eyalzh <[email protected]> wrote:
> Nice job!
>
> I made a similar effort to develop some kind of an in-wave gadget
> development playground for personal use, but not a full-blown IDE.
> My bot stores the code on the appengine server and creates a dynamic python
> script which fetches the code and outputs XML. That script is the dynamic
> preview gadget. It receives as a parameter the id of the wave, which is in
> turn the DB key. When the "preview" button is clicked, the robot adds a new
> blip with the dynamic gadget. That way, I don't need to refresh the wave.
>
> At first, I wanted to use a textarea for the code but eventually I just
> encapsulated the code in the blip itself. Turned out it was a great idea, as
> I get to use all kind of annotations and in-code elements (like images and
> links) and enjoy the all the OT goodness. Two of my latest gadgets were
> developed to stable state entirely on wave!
>
> Eyal.
>
> On Fri, Jan 29, 2010 at 8:28 AM, rockwalrus <[email protected]> wrote:
>>
>> I've created a simple IDE for in-wave development of gadgets.  It's
>> inspired by the Google Gadget Editor.  There is a public demo wave at
>>
>> https://wave.google.com/a/wavesandbox.com/#restored:wave:wavesandbox.com!w%252BrEPms820D
>> .  You can also try it out by adding [email protected] to a new
>> wave.
>>
>> There are several known issues due to Wave bugs or missing features:
>>  * Gadget preview URL isn't changed to reflect renaming of main gadget
>> xml file
>>   http://code.google.com/p/google-wave-resources/issues/detail?id=637
>>  * "Update" button doesn't actually update the gadget preview
>>   http://code.google.com/p/google-wave-resources/issues/detail?id=636
>>   http://code.google.com/p/google-wave-resources/issues/detail?id=637
>>   (Workaround: switch to another wave and back.)
>>  * Gadget doesn't display if it has expired from the Tidal robot's
>> cache
>>   http://code.google.com/p/google-wave-resources/issues/detail?id=633
>>   (Workaround: if the file is not cached, make a trivial edit to
>> refresh it.)
>>
>> It's pretty easy to run up against the 100k limit with this tool, but
>> it's still useful if your gadget is small.
>>
>> Rockwalrus
>>
>> --
>> 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.
>>
>
> --
> 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.
>

-- 
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.

Reply via email to