Hi,
El 20/05/09 08:50, Edward K. Ream escribió:
On Tue, May 19, 2009 at 12:00 PM, Ville M. Vainio <[email protected]
<mailto:[email protected]>> wrote:
On Tue, May 19, 2009 at 7:01 PM, Terry Brown
<[email protected] <mailto:[email protected]>> wrote:
Backlinks are what I thought about immediately when confronted w/ this
problem, but then abandoned the idea. The problem w/ backlinks is that
they live in the object / opaque gnx / leo world, not the ever elusive
flat text world. And flat text world is what will always win :-)
Good point. I'd like to believe this statement is always true. I
have my doubts.
For example, I've always wanted Leo to be able to render html in
Leo's body pane. Maybe, following the color_markup plugin, we could
switch between rendered and plain versions of text with something like
@language html versus @language rendered-html.
I'd like to find a general way to handle other languages, like
networkx, for which text can be rendered to non-text. At present, this
is only a dream, but it would be a huge step forward for Leo.
[...]
Could we use "combined directives" for example "@render @language html".
I can Imagine situations where we would like to use both views, so
putting a hierarchy of @nodes could activate one of them or the other.
Just an idea,
Offray
--
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.
