On 8/6/2013 9:16 AM, Edward K. Ream wrote:
B. A "switch" in each headline: something like @rich (if the default
is plain) or @text (if the default is rich). Consistent in *form*
with Leo's existing conventions. Alas, it would conflict with @file,
@test etc. etc.
My vote is for @rich.
I don't see how it would necessarily conflict with @file, @test, etc.,
as you could structure it like so:
SomeOutline.leo::
@rich this is just a note node, not in a file
@file test.html
@rich Some block of rich text, serialized as html
With @rich, that doesn't add any mode bits, and when saved to disk it
will simply be an html string. Saving to RTF files, etc, is a different
concern altogether. Perhaps after @rich nodes are introduced, someone
could branch that off and create @rtf nodes, which serialize to
Microsoft RTF? Then it's a (not so) simple matter of doing something like:
@file blah.rtf
@rtf blahblah
Perhaps even a different switch altogether for RTF files, like @rtffile?
@rtffile blah.rtf
A headline for a node that is rich, given the @rtffile heading?
That seems ugly, however.
Perhaps, more generally (and this should be a separate topic), Leo needs
a @filetype directive, with a plugin system to define various
filetypes? For example, having a "@filetype binary" would have *all*
data saved as raw data on the disk, rather than as a string? Something
like that, where new @filetypes could be added with settings
(myLeoSettings.leo) or handled akin to the colorizer files?
Just some thoughts.
-->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.
