Re: [Pharo-dev] PetitMarkdown

2015-05-03 Thread H. Hirzel
Hi Jan, Thank you for your answer, in particular the PPMiniCommonMark example. For me this is an interesting work, I can see a lot lot of application areas in and out of the Pharo context. I'll have a closer look at your implementation, in particular the test cases. Have a good day Hannes On 5

Re: [Pharo-dev] PetitMarkdown

2015-05-03 Thread Jan Kurš
Hi Hannes, I actually did not do any changes to the grammar, I wrote the grammar from scratch. The reason I did so was to have a proof of concept of my PetitParser extension for parsing indentation-sensitive grammars such as Markdown or Python. The most simplest example you can do is to evaluate

Re: [Pharo-dev] PetitMarkdown

2015-05-02 Thread H. Hirzel
Thank you Jan, for your work in enhancing PetitParser for Markdown. I think I got what you did by loading PetitParser in Pharo 4.0. I found the examples PPMarkdownGrammarTest, category testing-documents. I also read http://scg.unibe.ch/research/indentParsing. Could you please elaborate a bit mor

Re: [Pharo-dev] PetitMarkdown

2015-04-20 Thread Damien Cassou
Dmitri Zagidulin writes: > Is this an issue of the version of Pillar that the book's build tools are > using? I thought I implemented that but you are right, it is not implemented. If you are lucky, Cyril will see this thread and fix it (hint, it's in PRLaTeXWriter>>writeEmbeddedPicture:). --

Re: [Pharo-dev] PetitMarkdown

2015-04-18 Thread Stephan Eggermont
On 18/04/15 18:49, Dmitri Zagidulin wrote: Didn't seem to work, the figure with no label was still placed arbitrarily by LaTeX (and not in the exact location). (And, actually, LaTeX placed the figure in the middle of a script block, which is really odd). Not a LaTeX problem. Scripts should be g

Re: [Pharo-dev] PetitMarkdown

2015-04-18 Thread Dmitri Zagidulin
On Thu, Apr 16, 2015 at 4:40 AM, Damien Cassou wrote: > Please note that if in Pillar you don't specify any label you could > reference from your text, then the figure will be placed by LaTeX at the > exact location where you put it in Pillar. This is because, in this > case, there is no way to w

Re: [Pharo-dev] PetitMarkdown

2015-04-16 Thread Damien Cassou
p...@highoctane.be writes: > Customer opinion on the output: why are figures not where I expect them to > be? they are where the *reader* expects them to be :-). The author of TeX thought that a machine can best decide where to put a figure because when you write the TeX source you don't know w

Re: [Pharo-dev] PetitMarkdown

2015-04-16 Thread Stephan Eggermont
On 16/04/15 12:07, p...@highoctane.be wrote: Customer opinion on the output: why are figures not where I expect them to be? Most of the figures are HD screenshots. Moving them around sucks. I'll try the no label thing. But labels are useful. HTML export is not doing that. LaTeX is an interim too

Re: [Pharo-dev] PetitMarkdown

2015-04-16 Thread p...@highoctane.be
Le 16 avr. 2015 10:41, "Damien Cassou" a écrit : > > > Christophe Demarey writes: > > > Le 14 avr. 2015 à 22:51, p...@highoctane.be a écrit : > > > >> I hate the figures not going where I want due to the LaTeX generation in Pillar. > > > > There should be options to place it where you want. Maybe

Re: [Pharo-dev] PetitMarkdown

2015-04-16 Thread Damien Cassou
Christophe Demarey writes: > Le 14 avr. 2015 à 22:51, p...@highoctane.be a écrit : > >> I hate the figures not going where I want due to the LaTeX generation in >> Pillar. > > There should be options to place it where you want. Maybe a pillar expert > could answer? this is not possible and, i

Re: [Pharo-dev] PetitMarkdown

2015-04-15 Thread Christophe Demarey
Le 14 avr. 2015 à 22:51, p...@highoctane.be a écrit : > I hate the figures not going where I want due to the LaTeX generation in > Pillar. There should be options to place it where you want. Maybe a pillar expert could answer? > As for class comments, markdown would make more sense to use whe

Re: [Pharo-dev] PetitMarkdown

2015-04-14 Thread Sven Van Caekenberghe
I am sorry, but I don't think you really have looked at this in detail. Read http://en.wikipedia.org/wiki/Markdown History & Extensions, just to known about some of the differences out there. Any language without any formal spec is close to impossible to parse well, it is just hacking. Note t

Re: [Pharo-dev] PetitMarkdown

2015-04-14 Thread Damien Pollet
On 14 April 2015 at 23:11, Dmitri Zagidulin wrote: > It is super hard to write a parser for MD. >> > > What do you mean? Why? > The syntax depends on indentation and block layout of text. It's very hard to express using the usual grammar tools. In PetitMarkdown, before Jan added indent-aware par

Re: [Pharo-dev] PetitMarkdown

2015-04-14 Thread kilon alios
Stef gets "fierce emotional" at times, he is very passionate about Pharo. I dont think he has a problem with having a good MD parser though it looks like that will be hard to do because of the nature of the MD syntax but his real problem is people porting doc to MD and abandoning or not even giving

Re: [Pharo-dev] PetitMarkdown

2015-04-14 Thread Dmitri Zagidulin
On Tue, Apr 14, 2015 at 9:21 AM, Jan Kurš wrote: > If there is an interest to use PetitParser/CommonMark in Pharo, I can > spend some time on it. I guess, I would be able to parse majority of the > examples (I am not sure about all the corner cases). > That would be fantastic! In general, even r

Re: [Pharo-dev] PetitMarkdown

2015-04-14 Thread Dmitri Zagidulin
On Tue, Apr 14, 2015 at 4:10 PM, Sven Van Caekenberghe wrote: > > Furthermore, there is NO MarkDown standard, nor will there ever be. There > are slight but annoying differences between the main implementors. Not true. There is at least http://spec.commonmark.org/ > It is super hard to write

Re: [Pharo-dev] PetitMarkdown

2015-04-14 Thread p...@highoctane.be
Some should cool down. I am using Pillar to write my (internal) docs. And I use markdown too. Both have their uses. Compared to things like RMarkdown, knitr, and RPubs in the R community, what we do have is passable in terms of output. We have a small community, we have to deal with that fact.

Re: [Pharo-dev] PetitMarkdown

2015-04-14 Thread Sven Van Caekenberghe
> On 14 Apr 2015, at 22:03, Dmitri Zagidulin wrote: > > Whoa. > I genuinely don't understand the fierce emotions here. Why do Pillar and > Markdown have to be opposed? Why is wanting support for better parsing of MD > (a commonly used format around the web, and useful in many projects) someho

Re: [Pharo-dev] PetitMarkdown

2015-04-14 Thread Dmitri Zagidulin
Whoa. I genuinely don't understand the fierce emotions here. Why do Pillar and Markdown have to be opposed? Why is wanting support for better parsing of MD (a commonly used format around the web, and useful in many projects) somehow an insult to the work done on Pillar? (Incidentally, I don't quit

Re: [Pharo-dev] PetitMarkdown

2015-04-14 Thread Tudor Girba
Hi, MD is a cool exercise for PetitParser exactly because it is a terrible language. Jan did a great job at pushing parsing limits, but that does not mean that we have to jump on it to use it inside Pharo :). Actually, at this point in time, I really do not quite understand why we are still enter

Re: [Pharo-dev] PetitMarkdown

2015-04-14 Thread stepharo
I'm really pissed off. Because nearly nobody tried to write anything with pillar and you just talk about what you do not know. But thanks this is great to see that we are spending our energy for people who will never even try to use what we are doing. Superb! No need to reply I will not read t

Re: [Pharo-dev] PetitMarkdown

2015-04-14 Thread stepharo
Le 14/4/15 11:43, Esteban Lorenzano a écrit : how complete it is? we would really like to think on: 1) include petitparser in Pharo 2) allow the writing of class docs in MD format :) seriously? With all the efforts and that damien and me are spending on pillar! Thanks a lot for your consider

Re: [Pharo-dev] PetitMarkdown

2015-04-14 Thread Esteban Lorenzano
> On 14 Apr 2015, at 15:51, Norbert Hartl wrote: > >> >> Am 14.04.2015 um 14:24 schrieb Peter Uhnák > >: >> >> On Tue, Apr 14, 2015 at 2:19 PM, Christophe Demarey >> mailto:christophe.dema...@inria.fr>> wrote: >> >> Le 14 avr. 2015 à 11:43, Esteban Lorenzano a écrit

Re: [Pharo-dev] PetitMarkdown

2015-04-14 Thread Norbert Hartl
> Am 14.04.2015 um 14:24 schrieb Peter Uhnák : > > On Tue, Apr 14, 2015 at 2:19 PM, Christophe Demarey > mailto:christophe.dema...@inria.fr>> wrote: > > Le 14 avr. 2015 à 11:43, Esteban Lorenzano a écrit : > > > how complete it is? > > we would really like to think on: > > > > 1) include petit

Re: [Pharo-dev] PetitMarkdown

2015-04-14 Thread Jan Kurš
Regarding completeness, it is not great. It was implement with an emphasiz on the indentation/prefix-related part (the hard one, I hope) so quoted blocks and and lists are almost complete (with arbitrary nesting). I did not need the other stuff, so there is a basic support for headers, paragraphs a

Re: [Pharo-dev] PetitMarkdown

2015-04-14 Thread Peter Uhnák
On Tue, Apr 14, 2015 at 2:19 PM, Christophe Demarey < christophe.dema...@inria.fr> wrote: > > Le 14 avr. 2015 à 11:43, Esteban Lorenzano a écrit : > > > how complete it is? > > we would really like to think on: > > > > 1) include petitparser in Pharo > > 2) allow the writing of class docs in MD fo

Re: [Pharo-dev] PetitMarkdown

2015-04-14 Thread Christophe Demarey
Le 14 avr. 2015 à 11:43, Esteban Lorenzano a écrit : > how complete it is? > we would really like to think on: > > 1) include petitparser in Pharo > 2) allow the writing of class docs in MD format :) I would prefer pillar for class / packages comments smime.p7s Description: S/MIME cryptogr

Re: [Pharo-dev] PetitMarkdown

2015-04-14 Thread Damien Pollet
+1 PetitMarkdown (at least in the state I left it) had an incomplete and contorted grammar, translated from another implementation (the one used by pandoc, I think). I started something to handle indentation, but meh. Jan's extension of PetitParser is the way to go, and it should make the grammar

Re: [Pharo-dev] PetitMarkdown

2015-04-14 Thread Esteban Lorenzano
how complete it is? we would really like to think on: 1) include petitparser in Pharo 2) allow the writing of class docs in MD format :) of course, we are talking about the not-so-near future, but is an idea we are thinking about… :P and in any case, I would like to use a good MD parser for m

Re: [Pharo-dev] PetitMarkdown

2015-04-14 Thread Jan Kurš
Hey, I also created an indentation sensitive extension of PetitParser, I also included some examples including Markdown. If you load PetitParser, you get the Markdown example as well. There is a short introduction to the indentation: http://scg.unibe.ch/research/indentParsing Cheers Jan On Apr

Re: [Pharo-dev] PetitMarkdown

2015-04-13 Thread H. Hirzel
Are there any news on this? --Hannes On 12/28/14, Norbert Hartl wrote: > I found markdown parsers in smalltalkhub and in the configuration browser. > > http://smalltalkhub.com/#!/~PharoExtras/PetitMarkdown/ > > > and the one in the configu

Re: [Pharo-dev] PetitMarkdown and pillar

2014-12-28 Thread Damien Cassou
On Sun, Dec 28, 2014 at 6:05 PM, Norbert Hartl wrote: > The markdown parser of PetitMarkdown looks pretty decent. Is there any code > that converts markdown nodes to pillar ones? I've never heard of anything like that. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ab

[Pharo-dev] PetitMarkdown and pillar

2014-12-28 Thread Norbert Hartl
The markdown parser of PetitMarkdown looks pretty decent. Is there any code that converts markdown nodes to pillar ones? thanks, Norbert

[Pharo-dev] PetitMarkdown

2014-12-28 Thread Norbert Hartl
I found markdown parsers in smalltalkhub and in the configuration browser. http://smalltalkhub.com/#!/~PharoExtras/PetitMarkdown/ and the one in the configuration browser PPMarkdown If I understand it correctly both are rooted into work