Yikes! I'm seeing the same thing. I'll iron Chrome compatibility out this evening.
I'd recommend not using the old code. I've refactored a bit of javascript and the CSS styles may not match up entirely. A friend of mine pointed me to this great post on standard screen patterns: http://designingwebinterfaces.com/designing-web-interfaces-12-screen-patterns The Miller columns don't work well for inline replies, because inline replies have a specific location within the full blip. I still favor the idea of displaying inline-replies to the side of the blip, like marginalia, so that paragraphs don't get broken in half. How to reconcile this with normal reply blips... not sure. The view I'm currently working on is a two-column "comparison" view. This will have a couple uses: 1. Change histories: http://en.wikipedia.org/w/index.php?title=Google_Wave&action=historysubmit&diff=398958280&oldid=391868055 2. Previewing transformations, such as "what happens if I add this robot to the wave?". 3. Merging or comparing different blips. On Thu, Dec 2, 2010 at 7:04 AM, Torben Weis <[email protected]> wrote: > Hi, > > I have chosen Tensor as the first Web UI for lightwave ( > http://code.google.com/p/lightwave) since it has some nice ideas that > distinguish it from the Google Wave experience. > I always considered it difficult to read very long waves in GWave. The > Miller columns seem like a good way to solve this although I am still unsure > how to handle inline replies ... > > Anyway, I started off with the v1 version because the current Tensor > version behaves strangely on Chrome. The first column is at the middle of > the screen. Can you reproduce this? > > Greetings > Torben > > 2010/11/20 Kai Chang <[email protected]> > >> Introducing Tensor: a UI concept for Wave in a Box >> >> http://fleetinbeing.net/tensor-v1/ >> >> This iteration of Tensor focuses on problems related to: >> >> - Large organizations >> - Many waves in many contexts >> - Long waves and deeply nested blips >> >> My solution is an arbitrarily long chain of Miller columns. There's >> plenty more to decide on to make this view truly usable. Conspicuously >> absent is the Wave Editor, or any way to get to it. >> >> Tensor-v1 is all static HTML/CSS/JS. I just copied+pasted the Waves to >> create the Blips columns. If someone has suggestions for populating the >> prototype with dynamic content, that would help with usability testing. >> >> The top and bottom bars are fairly unresolved. A persistent metadata >> display would be useful for many users. For instance, my mom works in >> Information Services for US New and World Report. She needs a way to create >> and manage a controlled taxonomy to ensure content is findable. >> >> -- >> 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]<wave-protocol%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/wave-protocol?hl=en. > -- 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.
