I think it can be an interesting basis for the way to interact with a
versioning system -
* You get automatic updates about changes anyone (or interesting
parties) make to any code (or just specific packages).
* The way the versioning system gets its information is that it is
simply another player in this game - getting updates from everyone
that's working - except that instead of displaying something, it would
simply save the state of each session it is connected to.

So each session is recorded as a diff against a known version on the
server. There is still a question of what the basis should be - the
pristine version of Squeak at that update level + those packages?

BTW, of course we'd need some client flexibility to allow one to control
what and when is published. Not all code should be recorded publically.

Daniel

Avi Bryant <avi at beta4.com> wrote:
> Yes, I think the proposed JabberingBrowser and Hydra are in a similar
> space - I don't necessarily need to see everyone's text selection like in
> Hydra, but I'd like to be able to open a browser that tracks which
> class/method someone else is looking at, and updates my code every time
> they accept.
> 
> Somehow it seems like this could be the basis for a versioning system, but
> I'm fuzzy on exactly how it would work...
> 
> Avi