I was just trying to design a robot that I would like to show for a demo. I needed somehow way to describe how the robot would interact with the user.
As so many other times I found the Whiteboard very useful. With the whiteboard is it possible draw with different colors for each participant. By using this method it will be possible to see the resulting Wave. The resulting wave will give an impression if the content is sufficient.
I would expect that use cases also could be an option, but they would focus more on with what the participants interacted with, not on how the result looked. The use case design is probably still a good idea, to make sure that all interactions are covered,
Designing such an interacting robot, might be involve many participants. It would be idea if the users cold design the resulting wave, by using Google Wave as the collaborative tool. They should probably create a wavelet, they could collaborate on and one where they could sketch the resulting wave.
Do you know of any modeling tools or methods, which could be prove useful for designing robots?
In some instances you want to have the robots and gadgets to interact. A scenario where it could make sense is, when the user wants information about a site. The page which could be showed could be the sales report of the customer or some other information which is of interest to the participants.
The robots listens for two event. First the SELF_ADDED which creates the URL form with a text box and a submit button. When the button is pressed a gadget is inserted in to the Blip, with the url of the gadget + the target URL. Probably something should be performed to ensure that the submitted URL is valid and can be sent as a query parameter. Probably a URL encoding should be performed or save the data in the datastorage.
PrintWriter out= resp.getWriter();
out.println("<?xml version=\"1.0\" encoding=\"UTF-8\"?>" +"<Module>" +"<ModulePrefs title=\"inline_external_page\" height=\"400\" width=\"800\"/>" +"<Content type=\"html\">" +"<![CDATA[ " +" <div id=\"main\"><!--Main container for the iframe-->" +" <iframe name=\"check\" id=\"check\" height=\"100%\" src =\""+(String)req.getParameter("url")+"\" width=\"100%\" frameborder=\"0\">" +"<p>Your browser does not support iframes .</p>" +"</iframe> <!-- this is where contents of the links are displayed -->" +"</div>" +"]]></Content>" +"</Module>"); }
The code is the same in the original blog it has just been placed into a servlet, to make it possible to have parameters inside. It just inserts the query parameter into the gadget XML.
I’m designing an application for Google Wave, which interacts with the user. The following is the considerations that I have for how the architecture of the application works best.
The application that I’m planning on should consist of a Robot which interacts with the user. The other part of the application should be a web application where users can configure how the robot should interact and view status from the waves. There should also be some analytics capabilities. The backend application needs to be rather a little complex to fulfill the requirements.
It looks like the developer preview will stop on September 30th, and then we must hope we can get an account on the production system. So we will not float without wave access for a long time.
What is interesting is that Douwe Osinga from Google is sharing, what they believe they can achieve before the end of the developer preview.
The things I think is the most exciting news are the following:
The Robots can use other addresses that email@example.com. That could mean you could have more robots on the same application making the robots tailored to the user. Also we will see that robots will exist on our own servers and not app-engine.
A better integration between robots in to Wave, so they robot can perform tasks even the wave is not active by a user.
OpenSocial integration for both robots and gadgets. That is something that I’ll need to look more into.
Insert simple HTML into the waves. This is not possible now, so the robots can make some better looking content easy. Then we need to consider using CSS on the document.
Open source the robot API it does not matter much now, but for the adoption that will probably make things easier.
I’m impressed with the plan Google has created for the development of the Google Wave API. I hope they have made some of the improvements already otherwise they will have a hard time implementing them all.