Up until now, I have never regretted using separate outline and body panes. For coding especially, there are advantages: all body text is unindented, regardless of its position in the outline.
However, "embedding" outline text does have advantages, as both the Quiver overview <https://github.com/HappenApps/Quiver/wiki/Getting-Started#5---preview-and-presentation> and the Englebart video <https://vimeo.com/81238285> show. In particular, outline heads can be "rendered" in place, according to outline level, context and user preferences. Unifying the outline and body panes would require changes throughout Leo. It seems too big a project, but I am playing with the idea. The Englebart video is tantalizing. Kent has long requested unified *file *views. The VR2 plugin provides one way to get that for a given tree, but it could be improved. Jupyter provides such integrated views without outlines. Links and TOCs must be entered by hand, but the visual effect is good. All such options could be called preferences, so it's no good arguing about them. Leo needs to do better in this regard. #443: Adopt Quiver Look and Feel <https://github.com/leo-editor/leo-editor/issues/443> contains links to many other related issues, so #443 is probably a good enough placeholder. Your comments, please. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
