Hello blind people You confuse form and contents. May be you should try to understand. But you continue to get blind after all everybody should carry its own cross and this is perfectly ok not to try to understand.
Pillar is not about syntax but about the text model and all the visitors. We are working on a release of Pillar 70 but we are slow because busy with other things. Part of the effort is to redesign and remodularised the core model since it grew too much with optional features. But for that we needed to design the production pipeline and clean a lot of problems (like relying on external bash files and external servers, and saving mustache files while we can just use stream and many more). Now where can I find a real robust parser of markdown written in Pharo (with tests of course)? I mean one that fully handles badly designed markdown? and one that I can extend to support references and missing things. Because Pillar could use multiple input formats. Now I will not spend MY time to write a parser. Why because I can write all the books I want with Pillar and this is a "Soup of Stone" in Pillar dev. Repeat after me: the domain is more important than the syntax. The proof is that pillar can generate slides, book, ascii, epub, markdown (but apparently the one of git, yes because they are multiple ones). HTML, static web sites .... I personally do not want to be tight to any external frameworks like pandoc. Stef PS: for the record, pillar syntax was invented in 2000. So please stop to bash us about not invented here because this syntax was invented before markdown was well-known. So check your sources before insulting people. On Sat, Dec 30, 2017 at 4:19 PM, Kjell Godo <[email protected]> wrote: >> As community we need to not blind ourselves to alternatives and overcome >> the Not Invented Here >> Syndrome, to see value in what is done outside Pharo for documentation in >> the same way we have >> done for software management (specifically Git). > > +1
