We used Google Wave in a conference call…

… and were mildly impressed.

We set up an agenda before the call started, and used that as our base document. It was then filled out as we discussed the various points, and comments were posted to capture remarks, questions and clarifications.

A couple of observations:

  • If your participants don’t have a Google account, you can’t add them with their regular Email address (even though that is somehow linked to their googlewave.com account), but you have to use their googlewave.com address.
  • The Ribbit plugin didn’t work.
  • There is a reluctance to edit other people’s blips. It seems to be more “polite” to comment on the blip and say that something isn’t correct than to go in and just edit the blip to correct it. Cultural thing – I’m sure it will change once more people have used Google Wave or even a Wiki.
  • It’s hard to make a comment in the conference call, and record it in the wave at the same time. However, a conference call is far superior in hammering out a discussion quickly. Maybe a designated typer would be an idea in a conference call?

We didn’t run into any software problems. There were 5 people on the call and the wave, and we never saw a slow-down or a crash. The only disappointment was the Reddit plugin, but that was easily overcome.

I think Wave is still looking for a good application. Minutes and collaborative documents seem the most obvious application, but I have the feeling there are more exciting applications for the Wave technique in the future.

Progress User Conference 2009 – Day 1

The first day of the Progress User Conference 2009 is behind me, and there were some interesting, some not so interesting sessions I attended.

The Opening Session went largely past me: I had to switch around windows a bit which caused me to restart the session a few times, and then a production issue took me away from my desk for a while. I intend to go back and look at it some time next week.

The first break-out session looked interesting: “Transparent Data Encryption”. This session described an add-on product to encrypt the whole or parts of the database. I can see some problems with the implementation, mainly that data is stored in memory unencrypted, which was a recent security issue I heard (can’t remember what the product was – I think it was Acrobat?). For the rest it looks interesting, albeit not very flashy.

After that came “Introducing OpenEdge Explorer”. It allows the same functionalities as Progress Explorer, but can be run from a web browser – thereby allowing multiple platforms. Similar to Progress Explorer, OpenEdge Explorer allows you to manage multiple machines and multiple products from one interface. OpenEdge explorer adds a few extras, like a log file viewer in the browser. The interface is similar to OpenEdge Management.

The last session before the break I followed was “Optimizing OpenEdge Performance in VMware ESX”. John Harlow from BravePoint described what VMWare is, and in what situations OpenEdge could be virtualized. He went into some detail on what memory settings are best, what are the adventages and disadvantages of more memory and CPUs, and what disk system should be used. Very informative.

After the break I switched channels and went to the UI flexibility track. “Serializing ProDataSets to JSON” describes the new features in OpenEdge 10.2B to convert to and from JSON objects with one or two statements. This makes Progress a more flexible server for WebServices.

“RIA in Perspective” describes the various Rich Internet Application interfaces, and which interface is most appropriate in what situations. Distinctions made are in user knowledge level, user interface and footprint. The options are combined in a RIA User Interface Decision Tree, available in the Progress Community website.

The last session for the day was “Implementing RIA and OpenEdge”. Dustin Grau from BravePoint describes what tools he uses to create RIAs, and showed several components. Unfortunately at that point I had the presentation slide maximized (the interface for the online conference contains a video screen which most of the time shows the presenter’s face, and a second area that displays the slide show), and missed most of the live demo. Another one on the list of presentations to view later.

All in all an interesting day, with some research subjects. I want to go back to two sessions to see them in their entirety, and two sessions I wasn’t able to attend (“Introducing OpenEdge GUI for .NET” and “Tales from The Trenches: Using the OpenEdge GUI for .NET”). I’m looking forward to Day 2, where I’ll be attending some sessions on productive development and distributed development.

Progress User Conference 2009 – online!

I’m currently attending my first Progress User Conference without being on location. Progress decided to go with an on-line conference this year in honor(?) of the economic recession.

The on-line format has some advantages and some disadvantages. Advantages are that I don’t need to get on a plane, check into a hotel, run all over the place to find the right room. I can actually keep an eye on my email, and look up things online, while listening to the presentations (although I could do that with a laptop). Disadvantages are the audience responses, human interaction, and the fact that I’m still at my desk and my co-workers look at me sideways wondering why I have these headphones on…

I’ll post a short update at the end of each day (which now ends around 1:15PM, as opposed to around 4PM for regular conferences) to let you know what I’ve taken away from that day.