GitHub just released a "Tree Slider" that is similar in function to Tensor's columns:
https://github.com/blog/760-the-tree-slider Rather than using Miller columns, it accumulates breadcrumbs. Good for saving screen space while digging 7-9 levels deep, and definitely less disorienting than traveling to a whole new page. Thanks for the response on Notes. I'm going to start the HTML/CSS structure for indented replies so we can get a better picture of what a full Wave will look like in Tensor. On Mon, Dec 6, 2010 at 4:36 AM, Torben Weis <[email protected]> wrote: > This rocks. I liked it the very momment I saw it. Looking forward to > realizing this in lightwave. > > Torben > > 2010/12/6 Kai Chang <[email protected]> > > Here's an inline-reply concept to chew on: >> >> http://fleetinbeing.net/tensor-notes-v1/ >> >> There may be an annoying bump if the browser needs to create a scrollbar. >> >> >> On Sat, Dec 4, 2010 at 11:19 PM, Chris Harvey <[email protected]> wrote: >> >>> Superscripts are an interesting idea. I think that inline replies are a >>> (potentially) useful feature, especially for making multiple comments on a >>> large document. In that case, I think there's an issue around having to >>> scroll to the bottom to see the comments. It works on an academic paper >>> (where reading the annotation is not essential to understanding the content >>> of the document) but might be a problem where reading the comments inline >>> are essential. >>> >>> Maybe a one-click "hide all inline replies", or "show all inline replies >>> as bottom-annotation" would 'solve' the problem. I guess it depends largely >>> on the use-case. >>> >>> My main reason for (up to now) leaving out inline replies is simply that >>> the average-user has way too many different ways to 'reply'. In this >>> instance, Wave is 'over-designed'. >>> >>> Based on feedback we have received so far, it looks like we'll stick with >>> this column approach. >>> >>> -- >>> Chris >>> iotawave.org >>> Singapore >>> >>> -- >>> 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]<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.
