On Mon, 5 Aug 2013 16:07:14 +0200
dufriz <[email protected]> wrote:

> Thanks for the clarification.
> >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).
> Of course, this is your choice as developers, but allow me to point out
> that this limits considerably the chances of Leo to compete with other
> applications such as Notecase and the like.
> 
> 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. Only then would I be willing to adopt Leo as my main
> production tool.
> Having the export tools (to HTML and to RTF) are not good enough, because
> what I need is to be able to *see* the projected outcome visually on the
> screen, while I am working on it.

Just a note that the `view rendered` plugin is a real time presentation
of the final output of rst, md, etc.  But authoring is still in rst etc.

I think what you're looking for could be added to Leo quite simple *if*
there's a PyQt compatible Qt rich text editor out there somewhere, we
just haven't found one yet.

Cheers -Terry

> 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?
> 
> >From what I understand, Leo has the potential of serving a wide range of
> purposes, and it is a pity to see its power restrained.
> Just adding some (native) support for rich text, in whichever form, will be
> a great improvement.
> 
> I only hope that the developer does not fail to see how crucial is the
> point I am making, as it may determine the future success or failure of Leo.
> 
> 
> ---------------------------------------------
> 
> 
> 
> 
> 
> 
> 
> 
> On Mon, Aug 5, 2013 at 3:38 PM, Edward K. Ream <[email protected]> wrote:
> 
> > On Mon, Aug 5, 2013 at 8:30 AM, Edward K. Ream <[email protected]>wrote:
> >
> > >
> > I'll update the opening words of the docstring to emphasize that the
> > plugin can render both markdown and rST
> > .
> >
> > Done at rev 5852.
> >
> > EKR
> >
> >  --
> > You received this message because you are subscribed to a topic in the
> > Google Groups "leo-editor" group.
> > To unsubscribe from this topic, visit
> > https://groups.google.com/d/topic/leo-editor/uTjcqREs8qQ/unsubscribe.
> > To unsubscribe from this group and all its topics, 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.
> >
> >
> >
> 

-- 
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.


Reply via email to