On 11/12/12, Esteban Lorenzano <[email protected]> wrote:
> +1

+1

> On Nov 12, 2012, at 9:57 PM, Tudor Girba <[email protected]> wrote:
>
>> Hi,
>>
>> I completely agree that the PIer syntax is rather niche these days, but we
>> should not confuse the PIer syntax with the Pier model. I think that it
>> would be beneficial to capitalize on this model (and all the
>> infrastructure built on top of it) and simply create a Markdown support.
>>
>> Cheers,
>> Doru
>>
>>
>> On 12 Nov 2012, at 15:56, Stéphane Ducasse <[email protected]>
>> wrote:
>>
>>> You won I put a filter markdown to thrash on my mail sadly.
>>>
>>>
>>> On Nov 12, 2012, at 3:11 PM, Camillo Bruni wrote:
>>>
>>>>>> It depends at which level.
>>>>>> Can you tag on word in markdown to have bold, italic, index?
>>>>
>>>> stef, I already explained you that at least 4 times! Plus I gave you the
>>>> solutions,
>>>> the only thing I don't have is the time to complete the Markdown
>>>> parser!
>>>>
>>>>>> If I would not have written 350 pages of seaside book with pier it
>>>>>> would be a different story but
>>>>>> so far pier syntax is good for doing everything: html, latex, even
>>>>>> markdown.
>>>>>
>>>>> In Markdown, it is *italic* or _italic_ and **bold** and __bold__.
>>>>>
>>>>> Now for index entries, I don't know exactly - making an automatic index
>>>>> is a special post process function anyway.
>>>>> I think you could do something like [ReadStream][index-entry]s are
>>>>> objects that you can read bytes or characters from.
>>>>>
>>>>> Making a book from several independent source files is quite a job that
>>>>> requires custom programming. It would be very cool if we could do all
>>>>> that in Smalltalk, using a good Markdown parser and a cool object
>>>>> representation.
>>>>>
>>>>> I have nothing against Pier, but it is something that only exists in
>>>>> our niche world, not in the larger world out there.
>>>>
>>>> my words!
>>>>
>>>> So we already had a Markdown / HelpSystem crossover for NativeBoost /
>>>> ASMJit where we injected
>>>> custom URLs to add method and class links, that worked pretty well. So I
>>>> assume it will be
>>>> not that much work on top to get section links ready.
>>>>
>>>> Something like book://section/subsection is very easy to do, a bit
>>>> verbose maybe but very
>>>> consistent.
>>>>
>>>>
>>>> so, please support:
>>>> https://github.com/dh83/PPMarkdown
>>>> http://ss3.gemstone.com/ss/petitmarkdown.html/
>>>
>>>
>>
>> --
>> www.tudorgirba.com
>>
>> "Every thing should have the right to be different."
>>
>>
>>
>>
>
>
>

Reply via email to