The free_layout and viewrendered plugins are a huge step forward. But the lighter/heavier distinction suggests a new way to use them.
Suppose Leo supports @render-rest or @render-html. This means that all nodes in the tree will have the body pane become a rendering pane for rST or html. Imagine LeoDocs completely rendered at all times. Of course, for specific purposes, say in Leo's scripting chapter, we might want to override these rendering directives (which should be allowed in headlines too) with @no-render. The point is that having *both* the original text *and* the rendered text be visible is often too heavy: the user usually does not want to know about the sources: the rendering is good enough. I suppose for sophisticated users, something like show/hide-body pane would be good commands to have, but that doesn't matter: those commands to not increase the burden on the user while she is reading the (rendered) docs. Your comments please, Amigos. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" 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/leo-editor?hl=en.
