With the new Robot API version 2 is it possible to interact with the gadgets using robots. This will allow for some interesting integrations and will mean that the gadgets can be used to show the graphical information that needs to be displayed by a user. By using the robot to fetch and populate the data, you are also able to make the requests update other information than is possible using the social API.
I have created a small demo that shows how this can work out. Look at this video.
Lifehacker describes the new Goolge Wave desktop notifier. Lifehacker is linking to the old version, the new version has some improvements. Google Wave Notifier is an application you install on your desktop and then you get notified when you get a new Wave in your inbox.
It works really easy and all you have to do is to enter your wave user id and password. When you get a new wave you can update the link, just by pressing the optup which comes.
For me it seems to work much better than the Firefox notifier. So I’ll try to see how it works out.
I normally prefere not to get any messages when I receive any mails or tweets. I prefer to check them, when I got time and need a break in my projects.
The ChartMarker Gadget is a gadget for creating graphs in Google Wave. It is really easy to use you add the robot with the address chart-maker@appspot.com.
To make a graph you use a command like the following {p 3,4,5}.
It is also possible to create other chart types like:
I created the SAP Enterprise service robot, which is described in the blog. I wanted to give you an explanation on how this robot was implemented.
I have therefore created a 5 minutes screen capture, showing what is going on and what the moveable parts are. Probably 5 minutes is a little too short, but if you have anything, which you want me to explain, I will do it. I hope you find it interesting.
I’m not proud of using crafted XML documents, instead of sending SOAP documents. But it was the only way that I could find to call SOAP web services from Appengine. If you have any suggestions to how I can avoid this, please let me know.
For this week there has been some interesting Wave blogs.
SAP Research in Brisbane had created a screen cast of their first Gadget. A gadget where people could collaborate on creating a process model. After the collaboration was done it was possible to export the process model and implement the model in SAP BPM. The screen cast show how complex gadgets can be and how they can assist with the collaboration. Also see Richards Hircsh response, which contains some insight full comments about the status.
LinkedProcess trying to make a more general protocol for Wave. The blog Social Computing or Let the bots talk! Gives a great overview of the technology, which allows the user to submit scripts to be executed on other hosts via XMPP.
Eye on FDA: Google Wave, Part 2 Examples on how Wave can be used in the pharmacy industry to help in some of the processes they have. It is always nice to get some concrete examples on how Wave can be used to help organizations.
App Engine SDK 1.2.5 released which is not Wave, but has some very interesting perspectives for Wave. It supports XMPP, which could mean that it is possible create wave clients/servers on Appengine.
I found the youtube video embedded below on, it is rather old now. It contains some interesting facts. 50 enginers in Google working on Wave. Make sure the protocol is open. Takes 2½ half year with the first wave application, but they hope that other groups will implement servers faster. Google compliments Twitter, and are working on ways to integrate twitter closer with wave.
Björn Wibben has created a blog about using jQuery in gadgets it looks quite interesting.
