pillar-markup
Microdown Stef Roadmap
Pharo10
- Release MD
- Release BC
For books:
-
make sure that we can write “simple” books in microdown and produce latex - case one with conversion to Pillar objects [this is working] - case two without conversion
-
Path to go there
- should manage inputfile (transofmration)
- resurrect basic converter from PR to MIC files
- Try on Pharo with Style
- check LaTeX export
For Slides
- support meta data
- introduce columns
- introduce slides
- Latex output (nearly done in fact)
- HTML output
Wrt columns, take a look at the MicTextPresenter class>>exampleCheetSheet. It is there already.
Ok I will have a look I wanted to know also how we manage finally the new line in text. Because there are strange code in some rendering (like splitting text on newline to iterate and to put it back). S
On 7 Jan 2022, at 09:53, Kasper Østerbye @.***> wrote:
Wrt columns, take a look at the MicTextPresenter class>>exampleCheetSheet. It is there already.
— Reply to this email directly, view it on GitHub https://github.com/pillar-markup/Microdown/issues/324#issuecomment-1007238453, or unsubscribe https://github.com/notifications/unsubscribe-auth/AADJTJIQAKRVURLSLPGBO5DUU2SZRANCNFSM5LOJMJXQ. Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub. You are receiving this because you authored the thread.
Yes, that is the meta issues "Several issues is related to handling of children of nodes”. Listed in #323.
It is not a hard issue to address implementation wise, but it has some overall design considerations which it would be useful to discuss.
Best,
Kasper
On 7 Jan 2022, at 10.14, StéphaneDucasse @.***> wrote:
Ok I will have a look I wanted to know also how we manage finally the new line in text. Because there are strange code in some rendering (like splitting text on newline to iterate and to put it back). S
On 7 Jan 2022, at 09:53, Kasper Østerbye @.***> wrote:
Wrt columns, take a look at the MicTextPresenter class>>exampleCheetSheet. It is there already.
— Reply to this email directly, view it on GitHub https://github.com/pillar-markup/Microdown/issues/324#issuecomment-1007238453, or unsubscribe https://github.com/notifications/unsubscribe-auth/AADJTJIQAKRVURLSLPGBO5DUU2SZRANCNFSM5LOJMJXQ. Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub. You are receiving this because you authored the thread.
— Reply to this email directly, view it on GitHub https://github.com/pillar-markup/Microdown/issues/324#issuecomment-1007250935, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEHHCYK2OLBA7VLE3FEMUFDUU2VF7ANCNFSM5LOJMJXQ. You are receiving this because you commented.
Ok what I started to do is to follow the design of the dom or XML
- Domain nodes are always in children and can be optional accessible via specific setters and getter. It means that we can access all the nodes using children.
- Entities that are not in the tree are annotation (for example url of a link).
Is what I'm saying clear?
The question is do we want the body of a code block (basically a large text or a list of line expressed as a Text elements) to be in the tree or we cut the flow at the block level.
I can live with the XML notion of children/elements, and the the attributes as annotations (typically using MicArgumentSplitter). But XML is not in agreement on this - this short discussion shows it pretty well: https://www.w3schools.com/xml/xml_dtd_el_vs_attr.asp
But yes - I like
- Domain nodes are always in children and can be optional accessible via specific setters and getter. It means that we can access all the nodes using children.
- Entities that are not in the tree are annotation (for example url of a link).
If that means the variable children should be used, or the method children should return the thing you ask for - I am perhaps more to the latter version.