On Tue, 17 Jan 2012 06:00:40 -0600
"Edward K. Ream" <[email protected]> wrote:
> > Perhaps Leo could offer some kind of generic solution by providing some
> > sort of templating system which could be applied to any text file
> > output. But it would still require a distinction between source files
> > and output, or built, files. Kind of cross-file section references.
>
> Interesting idea. It's likely no accident that templating systems are
> so popular on the web, because of the deficiencies of html and xml.
> Feel free to discuss ideas for templating in Leo. It might help a lot
> of people.
Basically something like
"""
Module for doing something
[<[URL for GPL boilerplate text]>]
"""
etc. So '[<[' and ']>]' would be some project level configurable
delimeters, and the "URL" would be some scheme we'd need to flesh out
to reference contents of nodes relative to the current (e.g. children),
relative to the top of this outline, or in other outlines. It should
also allow including non-Leo content, like text files.
It might be more bang for buck to integrate Genshi into Leo
http://genshi.edgewall.org/
*NOTE* Genshi works with plain text too, most of the docs document its
HTML/XML usage.
There's also http://cheetahtemplate.org/ another Python based template
language I'm not familiar with.
I think some combination of these things would address people using
clones to generate output. You can't get away from a source-file /
output-file dichotomy, but I don't think that's so bad for this
application. For people using clones to construct views of source
code, this approach would be irrelevant.
Cheers -Terry
--
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.
