Hi, for me the most important UI question is: Should we stay with a "generic" UI like wave.google.com or should we accept that different use cases require different views on a wave?
IMHO wave never had the PERFECT interface for editing documents collaboratively. The inline comments are not very comfortable. They should be displayed to the right of the document more like comments in word (but with a more pretty look please). The document itself needs more screen width. Wave's 3 column mode was inappropriate for document editing and I grew tired of resizing it for every wave. When chatting with wave, I felt that instant messengers had a better interface for this task. Wave technology could do it all and better, but the idea of a generic UI setup for all tasks from chatting to mail to document editing never convinced me. >From a technical perspective I wonder how the UI should figure out what to do. How does it detect that a wave is more a chat rather than document editing? Either we put in some meta data OR the UI has to guess. If the first blip is very long, it is most likely collaborative document editing. If the wave has many small blips, it is more like a chat. The problem with guessing is that the system might surprise the user and surprising the user is never a good idea. Anyway, my believe is that we should drop the idea of a generic UI interface. Let the wave display waves differently depending on what kind of a wave it is. Developers love these generic things, but all the other normal beings out there typically don't. Torben 2010/11/27 Michael MacFadden <[email protected]> > All, > > As the web client's wave panel becomes more and more functional, I thought > I might turn my attention to the wave list and surrounding components, so I > can start to get a feel for the rest of the client. Obviously there is > plenty to be done in this area as well. > > The question is, do we have clarity on where we want to go with the overall > UI design. I have reviewed the UI mocks that were published on line. There > are some good ideas in there, but the package of mocks seems to show many > different options rather than a single design. For example some mocks use > pop up windows while others uses the more traditional side by side view of > GWave. > > I think we need some clear direction, however I envision long thread > postings debating some minutia of the dewing overshadowing the macroscopic > decisions we need at this point. > > Also, since this is a fairly visual thing, how do we collaborate? Seems > like groups will be hard since it's textual. > > What's the path forward? In the meantime anything simple that needs to be > done in the wave list? > > Michael > > -- > You received this message because you are subscribed to the Google Groups > "Wave Protocol" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<wave-protocol%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/wave-protocol?hl=en. > > -- --------------------------- Prof. Torben Weis Universitaet Duisburg-Essen [email protected] -- You received this message because you are subscribed to the Google Groups "Wave Protocol" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/wave-protocol?hl=en.
