+1. I can't think of any detractions.
On Mon, May 4, 2015 at 8:59 PM, Guillermo Polito <guillermopol...@gmail.com>
wrote:
> If I understand correctly... then, why the pillar.conf is not just a
> pillar file? (And the conf is the header if the file?) :)
>
> El lun., 4 de may. de 2015 a la(s) 2:50 p. m., Damien Cassou <
> damien.cas...@inria.fr> escribió:
>
>>
>> Cyril Ferlicot <cyril.ferli...@gmail.com> writes:
>>
>> > Hi,
>> > I'm currently working on the way we manage the input files and the
>> output files.
>> > The way we manage the files now makes hard some improvement of Pillar.
>> > That's why with Damien we though about makes some changes. The changes
>> > are big so I wanted to talk about that with you.
>> > We propose to have always 1 file with all the work inside. That can
>> > use the inputFile tag. For example:
>> >
>> > "${inputFile:Chapter1.pillar}$
>> >
>> > ${inputFile:Chapter2.pillar}$
>> >
>> > ${inputFile:Chapter3.pillar}$
>> >
>> > ${inputFile:Chapter4.pillar}$"
>> >
>> > And the option "separateOutputFiles" will now create 1 file each time
>> > we have a new Chapter. (!Level 1 header).
>> > That will make simpler the way to number everything and to create
>> > anchor because those 2 doesn't work well with the "separateOutputFile"
>> > option.
>> >
>> > What do you thing? That would be good with you?
>>
>> this change proposes to remove the option inputFiles from Pillar. Pillar
>> will now take only 1 Pillar input file that must include the rest. This
>> will simplify pillar.conf, this will simplify compile.sh, this will make
>> it easier for the author to understand the process, and this will
>> simplify Pillar's implementation. With this in place, we think we can
>> fix the problems with anchors and inter-chapter links.
>>
>> --
>> Damien Cassou
>> http://damiencassou.seasidehosting.st
>>
>> "Success is the ability to go from one failure to another without
>> losing enthusiasm." --Winston Churchill
>>
>>
