I'm because Pillar is central to all my writings around Pharo (books,
slides,...).
We also want to use it for a lecture on open-source development.
Pillar got too complex and we should simplify its architecture.
I'm working on a new version of Cocoon but this tedious and I got
stuck in managing
initialisation of fields (from text to objects). now I will continue
to work but task switching is killing me.
Guillermo is helping me from time to time and damien helps me with the
makefile/latex.
I will first finish all the slides for my lectures at Prague first.
Now we made
- sure that we can run archetype without being forced to passed by the
command-line.
- and many changes and cleanup.
Now we should work on
- Make sure that we identify for real bugs showing up in the three
different archetypes (slides, books...).
- Avoid to convert to JSON files to apply mustache.
- Rethink the architecture.
- Like removing the dependency on magritte from the core.
- Avoid a lot of strange behavior related to metadata handling.
Stef
On Wed, Aug 2, 2017 at 6:15 PM, Alexandre Bergel
<alexandre.ber...@me.com> wrote:
> Pillar is becoming central in the way I produce documents.
> Is there anyone working on improving Pillar?
>
> Alexandre
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
>> On Aug 2, 2017, at 11:55 AM, Stephane Ducasse <stepharo.s...@gmail.com>
>> wrote:
>>
>> Hi martin
>>
>> I would like to wlak over epicea objects and save the changed methods
>> to be able to write booklets faster.
>> What advices can you give me?
>> Create a special visitor?
>>
>> Stef
>>
>
>
