On Wed, 14 Aug 2013 09:25:48 -0500
"Edward K. Ream" <[email protected]> wrote:

> On Wed, Aug 14, 2013 at 9:21 AM, Terry Brown <[email protected]>wrote:
> 
> >
> > Excellent idea.  So the rule would be:
> >
> > cke-text-open is called whenever a node is selected that includes
> > "@rich" in its headline, or is the descendant of a node which includes
> > "@rich" in its headline.
> >
> > And when rich text is opened by the above mechanism, it will be
> > automatically closed when a node not matching the above criteria is
> > selected.
> >
> 
> A few additions:
> 
> 1. Leo recognizes several directives when they appear either in headline or
> body text.  If possible, it would be good to support @rich in body text as
> well as headline text.

I suppose it can be 
  if '@rich' in p.h or '@rich' in p.b[:1000]:
but the ideal of having the directive '@rich' in a rich text seems a bit
at odds with the whole wysiwyg thing.

> 2. If the plugin is going to have be @rich be heritable, it would be good

I like heritable, I don't like seeing a whole list of nodes starting
with the same directive.

> to support @norich.  

Could do that, I assume searching for strings is cheap, timewise.

> Perhaps @language directives could be equivalent to
> @norich, the idea being that if one wants syntax coloring one would not
> likely also like rich text handling.

Might wait on that one, currently Leo inserts '@language html' into
@edit foo.html nodes, but I do want rich display in .html nodes...

Not sure if I'll really use rich text much myself - although the table
editor might be nice with an rst <-> html table format translator, for
those tables which are just a pain to edit in rst.

Cheers -Terry

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