posts

On Google Waves

So, Google Waves and its associated protocol were announced at the Google IO conference (video on waves homepage homepage). They mentioned that it was a collaboration platform. I thought ‘hmmmm, what about….’:

• Would it be possible to create a tool that let you upload a directory of text files…
  • For example a set of source code for a java package net.fbstj.example would be in ./net/fbstj/example/*.java
• …so that they still appeared as files (maybe as inline-reply-like things) and were editable in the standard sense, and maybe the traceback would be taggable.
• And then, would it be possible to download that set of files, as they are in that wave, just like you do for the pictures thing.
• What about subdirectories, I hear you ask. Well they could either be separate waves;
  • so wave named net/fbstj/example links to wave titled net/fbstj/example/Class.java
• or each directory is a ‘level’ of inline-reply-likeness;
  • so wave net/fbstj/example has an ‘inline reply’ at line with the words Class.java wihch holds the contents of the class file.
• or they could all be at the same ‘sub’ level but be ‘named’ by their appropriate level;
  • so wave named net/fbstj has ‘inline reply’ at line example/Class.java and another at line utils/AnotherClass.java
• I guess it depends on how much code you have, and how many sub packages you have too.

Another question I have is, is it possible to make a wave read-only?

A third I ask: is it possible to see the ‘source’ of a wave? as I like editing it directly. Also what about semantics, like RDFa and things like that.

What about transclusion? there is no point in having a hard copy of a document. And something using mozilla bespin would be tasty/sweet :D