> 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.
I, for one, would welcome this. > 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. Occasionally both at once is useful, specifically when writing things for others, which will be consumed in html or some other rich text fashion. Of late I've been hanging around the Stack Exchange network (www.stackexchange.com), and their edit mode is the best implementation of plain text edit + rich text preview I've had the pleasure of using so far. It's near simultaneous, and most everything can be keyboard driven (e.g. [ctrl-b] for bold, [ctrl-k] for code, etc.). --matt -- 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.
