Re: freemarker-generator: Improving the input documents concept

2020-02-23 Thread Daniel Dekany
What you are describing is more like the angle that FMPP took initially, where templates drive things, they generate the output for themselves (even multiple output files if they wish). By default output files name (and relative path) is deduced from template name. There was also a global data-mode

Re: freemarker-generator: Improving the input documents concept

2020-02-23 Thread Siegfried Goeschl
Hi Daniel, Good timing - I was looking at a similar problem from different angle yesterday (see below) Don't have enough time to answer your email in detail now - will do that tomorrow evening Thanks in advance, Siegfried Goeschl ===. START # FreeMarker CLI Improvement ## Support Of Multip

Re: freemarker-generator: Improving the input documents concept

2020-02-23 Thread Daniel Dekany
Correction... this is not what I meant: freemarker-cli [...] --named-document users somewhere/foo-users.csv --named-document groups somewhere/foo-groups.csv It should have been this: freemarker-cli [...] --document-name=users somewhere/foo-users.cs

freemarker-generator: Improving the input documents concept

2020-02-23 Thread Daniel Dekany
Input documents is a fundamental concept in freemarker-generator, so we should think about that more, and probably refine/rework how it's done. Currently it works like this, with CLI at least. freemarker-cli -t access-report.ftl somewhere/foo-access-log.csv Then in access-rep