Comments on: What I would like to see in Google Wave http://surfinggooglewave.com/2009/11/what-i-would-like-to-see-in-google-wave/ For a Clearer Understanding of Google Wave and its Application Tue, 09 Feb 2010 17:15:30 +0100 http://wordpress.org/?v=2.9.1 hourly 1 By: Ferdinand Kolcak http://surfinggooglewave.com/2009/11/what-i-would-like-to-see-in-google-wave/comment-page-1/#comment-46 Ferdinand Kolcak Fri, 27 Nov 2009 16:39:08 +0000 http://surfinggooglewave.com/?p=66#comment-46 I would add the better playback funcionality while playing back a long wave every now and then you need to scroll down (or up) to see the text added. So playback function should put each blip that has been added or edited to the center of the screen and possibly mark the relevant blip or edited text by a color (or to make it visible some other way for reader). Excellent post Nenad. Ferdinand I would add the better playback funcionality while playing back a long wave every now and then you need to scroll down (or up) to see the text added. So playback function should put each blip that has been added or edited to the center of the screen and possibly mark the relevant blip or edited text by a color (or to make it visible some other way for reader).

Excellent post Nenad.
Ferdinand

]]> By: Anand Srinivasan http://surfinggooglewave.com/2009/11/what-i-would-like-to-see-in-google-wave/comment-page-1/#comment-33 Anand Srinivasan Mon, 23 Nov 2009 11:49:52 +0000 http://surfinggooglewave.com/?p=66#comment-33 Very nice post Nenad. I've added a few more such suggestions on my Google Wave blog. Do take a look : http://techmein.com/google-wave-wish-list/300128 Very nice post Nenad. I’ve added a few more such suggestions on my Google Wave blog. Do take a look : http://techmein.com/google-wave-wish-list/300128

]]> By: Nenad http://surfinggooglewave.com/2009/11/what-i-would-like-to-see-in-google-wave/comment-page-1/#comment-32 Nenad Fri, 20 Nov 2009 09:19:07 +0000 http://surfinggooglewave.com/?p=66#comment-32 Thanks for a well thought out and extensive comment. I am glad to have somebody else's point of view on this, now I no longer feel like I am talking to myself. Thanks for a well thought out and extensive comment. I am glad to have somebody else’s point of view on this, now I no longer feel like I am talking to myself.

]]> By: ThatsAllFolks http://surfinggooglewave.com/2009/11/what-i-would-like-to-see-in-google-wave/comment-page-1/#comment-30 ThatsAllFolks Thu, 19 Nov 2009 17:09:12 +0000 http://surfinggooglewave.com/?p=66#comment-30 Permissions: I can see someone wanting more permissions. But really, the Wave is for multi-party editors, and each wave can be effortlessly copied/exported so readers can have it. That said even if someone did go in and majorly screw stuff up, you can always go back to the prior edit. Permissions for me would be a somewhat nice feature that I genuinely fear would be heavily misused and abused. Wave is liquid, flowing, and permissions are therefore less important. I suggest if you're working with people you don't trust that you take refuge in the fact that nothing you do will really be lost in the wave, and you can always set ground rules for everybody editing the wave. Locking as finished: Not all that significant. If it's done, it's done. Good thing about it - if someone catches an unfinished piece they can go in and fix it. You can even use copies of the wave for really anal-retentive version control. Although version control can be done just as easily in a single wave by typing the version number at the top with each new version. In fact, I don't even bother. Google has a number corresponding to each revision of the wave. Linking/Tagging blips - that's actually a neat little idea that would be interesting to see. Not sure I'd use it, but I can see its advantage. I'd say so far one of the coolest part about blips is that wherever you click "reply" in the wavelet, that's where the reply appears. Removing People: I"m a bit surprised this isn't a feature. To me this has got to be rather high priority. It may mean permissions would have to be done first. I can see it becoming sticky though. Number one if you're working on something (some of it maybe being your own creative work) you wouldn't want someone stealing it and leaving you without a way to access the information. So a static copy would have to be provided for such a kicked member - the last version they were on as editor. Maybe up front, at the beginning, each member of the wave could agree to the permission-set of the wave. That is, you can set it so that people can be muted/kicked freely...or no special permissions as it is now. Splitting/Branching waves: You can copy a wave, which is similar. Draft - sorry, I see this as being email-only. Email Integration: Every user is given an @googlewave.com email address. I haven't played with that yet. Reposition Windows: I think it works great the way it is. Tagging/Grouping Contacts: Sounds good to me. Saving Setup: I think this should be an opt-in feature (at first you probably just want to get used to how the wave suggests you work, and decide later whether you want to keep it that way or not). Permissions: I can see someone wanting more permissions. But really, the Wave is for multi-party editors, and each wave can be effortlessly copied/exported so readers can have it. That said even if someone did go in and majorly screw stuff up, you can always go back to the prior edit. Permissions for me would be a somewhat nice feature that I genuinely fear would be heavily misused and abused. Wave is liquid, flowing, and permissions are therefore less important. I suggest if you’re working with people you don’t trust that you take refuge in the fact that nothing you do will really be lost in the wave, and you can always set ground rules for everybody editing the wave.

Locking as finished: Not all that significant. If it’s done, it’s done. Good thing about it – if someone catches an unfinished piece they can go in and fix it. You can even use copies of the wave for really anal-retentive version control. Although version control can be done just as easily in a single wave by typing the version number at the top with each new version. In fact, I don’t even bother. Google has a number corresponding to each revision of the wave.

Linking/Tagging blips – that’s actually a neat little idea that would be interesting to see. Not sure I’d use it, but I can see its advantage. I’d say so far one of the coolest part about blips is that wherever you click “reply” in the wavelet, that’s where the reply appears.

Removing People: I”m a bit surprised this isn’t a feature. To me this has got to be rather high priority. It may mean permissions would have to be done first. I can see it becoming sticky though. Number one if you’re working on something (some of it maybe being your own creative work) you wouldn’t want someone stealing it and leaving you without a way to access the information. So a static copy would have to be provided for such a kicked member – the last version they were on as editor. Maybe up front, at the beginning, each member of the wave could agree to the permission-set of the wave. That is, you can set it so that people can be muted/kicked freely…or no special permissions as it is now.

Splitting/Branching waves: You can copy a wave, which is similar.

Draft – sorry, I see this as being email-only.

Email Integration: Every user is given an @googlewave.com email address. I haven’t played with that yet.

Reposition Windows: I think it works great the way it is.

Tagging/Grouping Contacts: Sounds good to me.

Saving Setup: I think this should be an opt-in feature (at first you probably just want to get used to how the wave suggests you work, and decide later whether you want to keep it that way or not).

]]>