On Tue, Jan 17, 2012 at 1:12 PM, Ville M. Vainio <[email protected]> wrote:
> This reminds me of my earlier valuespace work, and jinjarender plugin.
> That's all I have time for, in way of comments right now :)
Thanks for reminding us of these plugins. Here is what I consider to
be the most important part of the jinjarender docstring, as far as
this discussion goes::
Conceptually, [@jinja] acts like @nosent - tree is parsed,
template is expanded and content is written to the file.
As I was saying, having this work like @nosent simplifies matters
greatly. We only have to worry about one-way text generation: from
the @jinja node to the external text, not vice versa. In this case,
clones cause no additional complications (unless you clone an @edit
node containing the *output* file!!)
Edward
--
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.
