On 20 October 2019 at 09.11.06, Pierce Ng (pie...@samadhiweb.com) wrote: On Sat, Oct 19, 2019 at 04:39:21AM -0700, Kasper Østerbye wrote: > I am currently working on a github markdown -> pillar tree (the internal > rep of pillar). I estimate I am a few days out from that one.
Are you doing this in pure Pharo? Yes. I want to be able to render it inside the image windows. I have wrapped libhoedown, a Markdown to HTML library. libhoedown uses callbacks to invoke its renderer and I started constructing a Markdown to Pillar (string, not object tree) renderer by having libhoedown call back into Pharo. Pierce I do understand you not wanting to write your own parser, it is a pest! However, I want a simple distribution model with no external dependencies. At the moment I have a working github-markdown parser (written in Pharo) which recognises: Blocks: headers, paragraphs, ordered and unorderd (nested) lists, block, code-blocs. Inline: bold, italics, overstrike, inline-code. I want links and images before releasing it as version 1. It is restrictive and is a bit peculiar regarding indentation and a few other things. — Kasper
