[Pharo-dev] Spec new release :)

Benjamin Benjamin.VanRyseghem.Pharo at gmail.com
Wed Nov 13 19:05:07 EST 2013

On 13 Nov 2013, at 21:19, Stéphane Ducasse <stephane.ducasse at inria.fr> wrote:

>> 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…
> With Athens inside the image we will use the pier parser to generate a document tree and render it inside the image. 
> Now one step at a time. 
>>> 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 :)
> What most of you do not get is that. But I do not care about Pier format. I care about a REAL solution that can produce a REAL document tree AND that ***I*** can edit and maintain and enhance so that I can create books.

So why not extending markdown then ?


> So I'm pragmatic we wrote the seaside book with pier so I took pier because I do not want to write a MD parser and building model
> and reinventing the wheel. And I do not want to have to learn a new language just to make sure that I can write books.
> Stef

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

More information about the Pharo-dev mailing list