I have been very pleased with how the production Wave system worked the first day.
Compared to the sandbox I enjoy working in the production system. It is nice to start it an almost empty mailbox, where you can start from. When you have said what you want you can archive the waves, and they will not pop in to you inbox.
I have had three (I’m a big shot) conversations with different peers in the wave system. It was easy and fast to communicate with them. The wave popped into my inbox, when somebody had any comments.
It would be nice to know if your peers was online, so you knew if the where able to respond. Or that you got a popup from the Google Talk gadget when a new wave was created for you.
There are some incoming waves that I have no reason to be a part of. I don’t know why these messages come into my inbox. It seem a kind of random. Is this the spam we will see in Wave. I don’t think anybody has created spam bots yet, thought it would be fairly easy to make.
I had a problem with my WP-BOT, which created a blog with the wave. The blog wp-bot.masteringwave.com uses the Wavr plugin. This plugin had hardcoded the some sources from the wave sandbox, because it nobody knew how it would be. I have created a but report on it.
I’m currently waiting for invites to the live Wave system,. The sandbox works still fine, so I can still collaborate. So an obvious choose is to follow up on what is happening and research for news. Try to have a look at the API’s for the system, and then you can start your development. Try to get the AppEngine plugin up and running.
There are some interesting blogs, to read for the day. ReadWriteWeb has an article on what to expect from the Wave launch, this gives some interesting pointers to how the launch will take place. Among that you can nominate 8 friends with invitations. There will be no new features for the wave system.
Lars Rasmussen and Stephanie Hannon wrote about what he google blog. They write about the teams process and the fun they had when they was at a school and had the children write stories together. Lars and Stephanie believe that people will be more productive with wave when communicating and collaborating, which I believe is a large part of the day. I would have to agree with them.
Stephanie Hannon also wrote about what happened in the wave sandbox on the google blog. She mentions the SAP and Sales force as some of the vendors how have made some impressive demos of the potentials.
Stop checking the twitter channel for #googlewave, it is way to full today so you will just get a lot of messages. It is really difficult to follow the conversations. The just wait till people starts receiving the team had received of feedback and the use cases which was presented from the sandbox period.
So when you get online try to check out the maps gadget, Pamela Fox has made.
Then hope that you get an invitation. I just hope that I get an invitation for my domain, so I can start collaborating with the team.
Just found that a new JAVA API of the robots is available on the download site. The difference in the code can be seen on the changes page.
One interesting concept is the AbstractRobot which has been added. From my look at it this class gives is able to create the capabilities XML and the profile information. So you only need to implement one class and then you can have all the information you need one place. This will make it much easier to program robots. The Rave Ruby frameworks has something like this, you just implement the methods for each event you want to have. Then the framework can manage to create the capabilities XML file. The AbstractRobotServlet and ProfileServlet was not changed, this could lead to thoughts about deprecation of these classes.
Of other changes the Annotations and Range has better toString functions, which was missing when you needed to debug applications.
I hope there will be posted a change to the tutorial, so we can start using the AbstractRobot instead.
In this week there has been some interesting blogs about Google Wave and Enterprise.
The Fedone Book has been created by James Purser. It contains a description on how to install the example wave server and getting started with using it.
GoogleWaveBlogger has created a blog about Google Wave + Google Voice = The Holy Grail. He gives ideas on how a mashup of Wave and Voice could be. With this post in mind, it looks like Wave can be mashed up with many different technologies to make new killer apps.
A wave forum has also been created, where it is possible to talk about Wave applications and usages.
Dagfinn Parnas has created a SAP Blog about how to embed waves in SAP enterprise portals. This gives some really nice examples on the usage of wave in portals.
Talking about embedding Waves in pages, I wrote a blog about embedding Wave in wordpress. The story was picked up by Mashable and also on other sites.
The last I found was an example on a robot to integrate with Salesforce. The blog by Kyle Roche, is a tutorial which go in details with how to create the robot. I like the API to Salesforce; it looks really easy to get started with compared to using Webservices.
A wave hackathon was held in Copenhagen, I blogged about it and it was also written on Version2 a Danish media.
DJ Adams has also created an example on how Wave can call a SAP REST service to get data about transports.
Process-One made a demo of their Wave server. It should be implemented in Erlang and had realtime updates between users. So users can see each other’s key stroke as they type. The UI is not as impressive as Googles but Process One have probably been working on the protocol. They are using the ejabberd to the XMPP/Wave communication and it looks promising. Their server could be one of the first third-party wave servers created.
If you have any comments or know any post that I have missed, please comment on this post.
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.
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.