On Tue, 17 Jan 2012 10:02:57 -0600 "Edward K. Ream" <[email protected]> wrote:
> On second thought, I am skeptical of any such scheme. The problem > isn't in defining a template, the problem is updating the template > based on changes to external files. > > The short form of the thought: templates would be easy if we only used > @nosent. > > But in the world of two-way flow of information (@file, @auto), > templates are not going to work. Only if you're trying to protect people from the "complexity" of a split between source and output files. I'd argue that that can't be done without exposing yourself to all sorts of risks from the (mis)application of clones. If you accept that what you're editing in Leo are the source files and when you want the output you 'File->Generate outputs from templates' or whatever, changes to external files aren't a problem. The plus for supporting a templating system in Leo is that all these systems work by rendering some sort of 'context' information in the template, and in Leo the context could include access to the Leo outline structure, which would be great leveraging of Leo's data model. 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.
