[LRUG] Googley Wavey Invitey

[Jocke Selin]

On 26 Nov 2009, at 11:52, Alex Young wrote:
> James Adam wrote:
>> On 26 Nov 2009, at 10:58, Chris Mear wrote:
>>> Trying to manage even, say, a to-do list would be like using a wiki
>>> page as your issue tracker -- you'd have to impose all the
>>> structure and operations by manual edits.
>> This is very true. To get the most out of Wave, you need to impose
>> some of your own ideas about how each document should evolve, what is
>> appropriate in terms of its evolution, and what it not. It might be
>> fine in some cases to have long chat-like conversations, but not OK
>> in others.
> 
> I think there's a case to be made that custom, single-use-type clients might work well. If you want to use it as a wiki, fire up a wiki client. If you want to use it as a to-do list, fire up a to-do client. Each could impose its own rules about formatting and the visibility of discussion without having to care about storage or communication media at all.

"custom, single-use-type client" _do_ work well. That's why they exist. Wave's strength [1] is the ability for a document to morph - not to be the best "to-do application". We all have been copying things criss-cross from application to application as the typed words and graphics have evolved. 

/JS

[1] Still to be proven.
PS, I'm the only Jocke Selin. ;)