Hi Scott, I agree that using the reply box at the bottom of the wave does not work too well for discussing points in the top blip after many replies are made. I'd suggest two alternatives: * Use inline replies, by selecting a location in the top blip then creating a reply (hit enter, click the blip's reply button, or click on the reply button in the hovering menu). * Be proactive about deleting resolved content. It's all visible in playback if it needs to be referred to.
Those apply for Google Wave. For WIAB, you can make inline replies the same way (select text, click reply or hit enter). There is no playback in WIAB yet, so deleting obsolete content is a little more severe. -Dave On Thu, Apr 7, 2011 at 1:14 PM, Daniel Danilatos <[email protected]>wrote: > Hi Scott, > > I'm assuming you're referring to Google Wave and not WIAB. In Google > Wave, you can hit the space bar to go to the next unread blip. > > Dan > > Στις 7 Απριλίου 2011 12:06 μ.μ., ο χρήστης Scott Mitchell > <[email protected]> έγραψε: > > I'm not sure this made a lot of sense. All I'm saying is... when there's > > something important at the top of a wave then it's a pain to scroll very > far > > to see comments about it. I've noticed that family/friends don't know > when > > a comment is added and don't scroll down to check. > > >
