On 8/14/2013 10:25 AM, Edward K. Ream wrote:
On Wed, Aug 14, 2013 at 9:21 AM, Terry Brown <[email protected]
<mailto:[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.
Agreed
2. If the plugin is going to have be @rich be heritable, it would be
good to support @norich. 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.
Also agreed, if the inheritable route is taken. I don't honestly care
if it's inheritable or not - I don't mind each node being marked @rich,
but some might.
Agreed on @language meaning the same as @norich. However, there has to
be an order of precedence with regards to @rich and @language - what if
the node is headlined "@rich blah" and the body contains "@language
blahblah"? Arguments could be made that either takes precedence - @rich
because headlines are higher-order (in my mind at least) or @language
because it specifies an intention. Perhaps @rich needs to test whether
the node body contains html?
-->Jake
--
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.
