Skip to main content

How To Understand Wavelets

I got acquainted with developing against the Google Wave Preview last week, and I'll be doing more of it this week. There are still many gaps in the documentation and in the public understanding of what exactly is going on in a lot of cases. This post is halfway between an introduction to Wave development and a story of my personal hurdles in my first experiments working with it.

One of the first things you'll find in the Wave documentation is a diagram I have reproduced here. This diagram is wrong.


You're going to notice something when you look at this diagram and play around with Wave itself, the web client. You're going to realize you have no idea what the difference between a Wave and a Wavelet is. You don't seem to be able to even see the term "Wavelet" appear anywhere in the application! What's more, everything the API docs describe a Wavelet as is what the UI seems to call a Wave. This was really confusing to me and I know I'm not the only one confused.

It took me a little bit of time to get the perspective to understand what I missed. Correcting my diagram with that information produces this:


See what was missing there? The missing piece was the all-too-subtle connection, not between Wave and Wavelet, but between individual waves. The official documentation diagram places the waves in parallel and mislead me to look in the wrong mindset for the distinction between Wave and Wavelet in the presentation context.

So how does this pan out in the user interface of Wave? Private replies. A private reply to any blip/reply will create a new Wavelet with two participants: the creator of the blip you reply to and yourself. (Actually, you can create a single-participant child wavelet if you reply to yourself privately.)

I'd like to try some experiments and see if and how the interface would present setups like a child wavelet with completely different participants from the parent wavelet. I'm investigating the use of these as sort of hidden data channels in a Wave. For example, the Robot I am developing might store some auxiliary data about the waves it gets used in via private replies to itself. 

Now, since I'm probably going to be spending a good bit more time with Google Wave in the weeks to come, I expect to document more of the things I'll learn along the way. If you're interested, let me know what you're doing or thinking about doing with Wave.
Labels:

Comments

Unknown said…
Your diagrams are not public documents, so they don't come through as images.
2:36 AM
Calvin Spealman said…
Thanks, Cory. Fixed.

That's what I get for thinking the publish feature from Google Docs to Google Blogger would actually work right for once.
8:08 AM
Post a Comment

Popular posts from this blog

CARDIAC: The Cardboard Computer

I am just so excited about this. CARDIAC. The Cardboard Computer. How cool is that? This piece of history is amazing and better than that: it is extremely accessible. This fantastic design was built in 1969 by David Hagelbarger at Bell Labs to explain what computers were to those who would otherwise have no exposure to them. Miraculously, the CARDIAC (CARDboard Interactive Aid to Computation) was able to actually function as a slow and rudimentary computer.  One of the most fascinating aspects of this gem is that at the time of its publication the scope it was able to demonstrate was actually useful in explaining what a computer was. Could you imagine trying to explain computers today with anything close to the CARDIAC? It had 100 memory locations and only ten instructions. The memory held signed 3-digit numbers (-999 through 999) and instructions could be encoded such that the first digit was the instruction and the second two digits were the address of memory to operat...
1 comment
Read more

Statement Functions

At a small suggestion in #python, I wrote up a simple module that allows the use of many python statements in places requiring statements. This post serves as the announcement and documentation. You can find the release here . The pattern is the statement's keyword appended with a single underscore, so the first, of course, is print_. The example writes 'some+text' to an IOString for a URL query string. This mostly follows what it seems the print function will be in py3k. print_("some", "text", outfile=query_iostring, sep="+", end="") An obvious second choice was to wrap if statements. They take a condition value, and expect a truth value or callback an an optional else value or callback. Values and callbacks are named if_true, cb_true, if_false, and cb_false. if_(raw_input("Continue?")=="Y", cb_true=play_game, cb_false=quit) Of course, often your else might be an error case, so raising an exception could be useful...
1 comment
Read more

Announcing Feet, a Python Runner

I've been working on a problem that's bugged me for about as long as I've used Python and I want to announce my stab at a solution, finally! I've been working on the problem of "How do i get this little thing I made to my friend so they can try it out?" Python is great. Python is especially a great language to get started in, when you don't know a lot about software development, and probably don't even know a lot about computers in general. Yes, Python has a lot of options for tackling some of these distribution problems for games and apps. Py2EXE was an early option, PyInstaller is very popular now, and PyOxide is an interesting recent entry. These can be great options, but they didn't fit the kind of use case and experience that made sense to me. I'd never really been about to put my finger on it, until earlier this year: Python needs LÖVE . LÖVE, also known as "Love 2D", is a game engine that makes it super easy to build ...
Post a Comment
Read more