[Pharo-dev] Spec new release :)

Benjamin Benjamin.VanRyseghem.Pharo at gmail.com
Wed Nov 13 19:06:09 EST 2013


Have a look at http://jgm.github.io/lunamark/ :)
It may be a dirty hack, that I do not know :)

Ben

On 13 Nov 2013, at 20:27, Sven Van Caekenberghe <sven at stfx.eu> wrote:

> 
> On 13 Nov 2013, at 20:22, Benjamin <Benjamin.VanRyseghem.Pharo at gmail.com> wrote:
> 
>> On 13 Nov 2013, at 20:05, Sven Van Caekenberghe <sven at stfx.eu> wrote:
>> 
>>> 
>>> On 13 Nov 2013, at 19:59, Benjamin <Benjamin.VanRyseghem.Pharo at gmail.com> wrote:
>>> 
>>>> It was a real question, and it feels like you overreacted the answer …
>>>> 
>>>> To me, markdown or pier is a new syntax to learn so I am asking …
>>>> To me, doing Pier because you do or because you said to is no really an argument.
>>>> 
>>>> Then I am open to a real answer but I also see that markdown is integrated to a lot of tools (github and jekylls by examples)
>>>> and that a lot of people knows about markdown.
>>>> 
>>>> This was a real question, not a troll …
>>> 
>>> I like .md as well and yes, the github integration makes it compelling.
>>> 
>>> But one objective argument against Markdown and in favour of Pier is that the former has no good parser and/or document model and and the latter does have both, in Pharo. That means that we can write all sorts of tools ourselves and get things finished, as was proven with the books.
>>> 
>>> There simply isn’t any definitive, unambiguous Markdown syntax (the github variant is only one version).
>> 
>> Ok :)
>> But as an end user, do you feel the difference ?
> 
> I know, but the documentation is meant to be integrated in the Pharo ecosystem.
> 
> It would be completely silly to have class comments in MD (no matter how cool this would be) _and_ *not* be able to have Nautilus parse/render them, with active links, etc…
> 
>> There are some PEG grammar for markdown, maybe it could be reused so PP can parse it :)
>> then one could generate Pier format out of markdown :)
> 
> So indeed, that is what we need. [And what we already have for Pier].
> But be sure to ask Camillo how his 2 attempts went before you get ambitious.
> I look at the PP MD code and thought, I can do better, but after writing some actual code, I stopped ;-)
> 
> BTW, please point me to grammar, I never found one ! Each MD parser is one big hack.
> 
>> Ben
>> 
>>> 
>>>> Ben
>>>> 
>>>> On 13 Nov 2013, at 19:22, Stéphane Ducasse <stephane.ducasse at inria.fr> wrote:
>>>> 
>>>>> do you really think that I insist of using pier syntax because
>>>>> 	A- I want to lose my time
>>>>> 	B- this is for my ego?
>>>>> 	C- because I'm funny
>>>>> 	D- ...
>>>>> 
>>>>> No seriously?
>>>>> 
>>>>> If you want to get an answer read the thread that yuri raised a while ago.
>>>>> Because we already discussed discussed and discussed it.
>>>>> 
>>>>> I will not write any book in markdown. Now you can try and we see.
>>>>> 
>>>>> Stef
>>>>> 
>>>>>> Stef, what is the advantages of writing it in Pier compared to markdown ?
>>>>>> 
>>>>>> Ben

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/attachments/20131114/7b3b5ed0/attachment-0002.html>


More information about the Pharo-dev mailing list