On Mon, Aug 5, 2013 at 9:07 AM, dufriz <[email protected]> wrote: > > From what you wrote, I take it that no form of rich text support (whether > Microsoft's RTF or otherwise) is going to be added *natively* to Leo (i.e. > excluding plugins). >
The distinction between plugin code and "native" code makes no difference in practice. In fact viewrendered.py is a standard plugin that is already enabled in the @enabled-plugins node in leoSettings.leo. What I would love to see is a *native* implementation of some form of rich > text (at the very least: font colors, sizes, italic, etc - that is, the > basics) within Leo. I think I understand what you mean. The typical way is to have lots of formatting icons in the body text, as in most wysiwyg editors. But that's not a high priority for Leo. > I think the question ultimately boils down to: do we want to keep Leo as a > strictly (or 'mostly') programmer's tool, or should we be also looking at > at wider range of uses, such as information storage (PIM and the like) and > text production tool? > Leo works really well as both a PIM and as a text production tool. In fact, it is much more flexible than "what you see is *all* you get" editors. True, you may have to adjust your notions of how to produce text, but you will have to do that for any high-performance text-production tool. 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 http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/groups/opt_out.
