Le 3/4/16 10:55, Damien Cassou a écrit :
stepharo <steph...@free.fr> writes:
Le 31/3/16 17:56, Damien Cassou a écrit :
Norbert Hartl <norb...@hartl.name> writes:
Wow that sounds a lot of things are possible. Do you have a roadmap?
There are plenty of things we would like to do:
- clean the issue tracker by doing all the simple things (it's time for
users to write their ideas there)
- facilitate the creation of new Pillar projects. Currently, it's a hell
to start a new book or a new lecture.
- simplify Pillar to avoid the current transformation to a build system.
We want to remove the dependency to the Mustache template engine. We
also want to remove Pillar's ability to compile LaTeX files to PDF. I
want Pillar to do just 1 thing: convert a .pillar to a .tex/.html/.*.
The rest will move to external projects, reusing as much as possible
of what's already there (e.g., GNU/Make) and leveraging other tools
(e.g., other template engines, even not implemented in Pharo).
- Well I would prefer to improve mustache if necessary. Controlling
the stack of external great tools is important.
The idea is not to make Mustache perfect for every possible use case,
Damien can you read what I wrote?
Did I say make mustache perfect?
No so what is your point?
the idea is that users should be able to pick the template engine that
fits best.
and also have a solution that works without relying on a specific tools
runnning
on a single OS and that we cannot debug.
"Je dis juste si mustache a une limitation et qu’elle est facile a enlever
alors c’est mieux d’ameliorer mustache car
on ameliore mustache
on amerliore pillar
Et moins on doit maintenir de trucs exterieurs plus on a une solution
perenne.
Je suis sur que si on demande a norbert d’ameliorer mustache il le fera
en plus.
Am I clear?
Now if you do not want that I work and push Pillar tell it to me too and
I can do something
else.
In this moment I'm about to rethink what I want to spend my energy so
pillar could be also
one less.
Stef
