Google Wave API combined with the Wookie engine and integrated in a Moodle platform

<p>
  To take a look, you need to head over to our <a href="http://getwookie.org/moodle">Moodle sandbox</a> and register yourself a profile (you&#8217;ll need to confirm your email address to activate the login). After that, go and <a href="http://getwookie.org/moodle/course/view.php?id=6">enrol yourself on this course</a>.
</p>

<p>
  Feel free to play <a class="zem_slink" title="Sudoku" rel="wikipedia" href="http://en.wikipedia.org/wiki/Sudoku">Sudoku</a>, mess with the poetry magnets, use the chat, and vote in the polls. All these tools are Widgets, written entirely in regular <a class="zem_slink" title="HTML" rel="wikipedia" href="http://en.wikipedia.org/wiki/HTML">HTML</a> and <a class="zem_slink" title="JavaScript" rel="wikipedia" href="http://en.wikipedia.org/wiki/JavaScript">JavaScript</a>, and don&#8217;t use any <a class="zem_slink" title="PHP" rel="homepage" href="http://php.net/">PHP</a> or any part of the Moodle platform they appear in other than using the context it supplies (the course ID in this case) and participant information (display name and avatar image); this means they can be embedded into any platform. Wave &#8211; the actual conversation engine &#8211; is the obvious one, but I think it makes sense to put live-updating collaborative applications into many different kinds of contexts &#8211; social networks, VLEs, blogs &#8211; anything with users and contexts.
</p>

<p>
  In addition to the W3C Widgets API and Google Wave Gadgets API, the <a title="Wookie Engine" href="http://getwookie.org/" target="_blank">Wookie engine</a> that renders the widgets also provides a moderator API, enabling admins to lock and unlock widgets. (However, test accounts are in the &#8220;student&#8221; role and so won&#8217;t see these controls)
</p>