On Fri, 19 Mar 2010 09:27:26 -0500 "Edward K. Ream" <[email protected]> wrote:
> On Thu, Mar 18, 2010 at 12:59 PM, Terry Brown <[email protected]> wrote: > > On Thu, 18 Mar 2010 12:52:37 -0500 > > Terry Brown <[email protected]> wrote: > > > >> viewrendered.py > > > > Forgot to mention this is a simple hack of Ville's sticky note plugin ;-) > > For a much lighter solution, look at the @@button nodes in test.leo: > > Prototypes-->Prototype of rendering commands > > These buttons/commands render directly in the body pane. Only for HTML, and somewhat destructively. I didn't really provide any context for this plugin, it was prompted by TL's (?) ansi color viewing comments, but not directly related. I was looking for something that updated automatically as you move through the tree. A better solution (but I think harder) would be rendered html / rst / whatever in the body itself as you move through the doc. (on nodes identified by whatever conditions you want). These rendered nodes would switch to plain text as soon as you tried to edit them, and in general p.b would be plain text, it's just the gui widget which is showing the rendered form. Also I think wysiwyg html editing for pyqt must be getting close, when we get to that the html nodes might not need to switch. viewrendered.py is just an interim thing, useful for even more immediate feedback when you're editing rst. html rendering is ok, although it doesn't seem to render styles... hmm, maybe I'm using the wrong widget. Anyway, this was an experiment on the road to "rich text" in leo. Not that I'm convinced it's a very important feature, with easy to read plain text markups like rst which can produce attractive rendered output later. Cheers -Terry -- 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.
