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
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
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
Dmitri Zagidulin dmi...@zagidulin.net 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
On Thu, Apr 16, 2015 at 4:40 AM, Damien Cassou damien.cas...@gmail.com
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,
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
Christophe Demarey christophe.dema...@inria.fr 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
p...@highoctane.be 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
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
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 when
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
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
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
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 format :)
I
+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
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
On 14 Apr 2015, at 15:51, Norbert Hartl norb...@hartl.name wrote:
Am 14.04.2015 um 14:24 schrieb Peter Uhnák i.uh...@gmail.com
mailto:i.uh...@gmail.com:
On Tue, Apr 14, 2015 at 2:19 PM, Christophe Demarey
christophe.dema...@inria.fr mailto:christophe.dema...@inria.fr wrote:
Le 14
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
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
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
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
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
On 14 Apr 2015, at 22:03, Dmitri Zagidulin dmi...@zagidulin.net 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
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.
On 14 April 2015 at 23:11, Dmitri Zagidulin dmi...@zagidulin.net 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
On Tue, Apr 14, 2015 at 9:21 AM, Jan Kurš k...@iam.unibe.ch 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
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
Are there any news on this?
--Hannes
On 12/28/14, Norbert Hartl norb...@hartl.name wrote:
I found markdown parsers in smalltalkhub and in the configuration browser.
http://smalltalkhub.com/#!/~PharoExtras/PetitMarkdown/
http://smalltalkhub.com/#!/~PharoExtras/PetitMarkdown/
and the one in
I found markdown parsers in smalltalkhub and in the configuration browser.
http://smalltalkhub.com/#!/~PharoExtras/PetitMarkdown/
http://smalltalkhub.com/#!/~PharoExtras/PetitMarkdown/
and the one in the configuration browser
PPMarkdown
If I understand it correctly both are rooted into work
The markdown parser of PetitMarkdown looks pretty decent. Is there any code
that converts markdown nodes to pillar ones?
thanks,
Norbert
On Sun, Dec 28, 2014 at 6:05 PM, Norbert Hartl norb...@hartl.name 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
31 matches
Mail list logo
