pkra / laml Goto Github PK

In vatter.html, rendered in-browser

As discussed F2F, let's be direct.

With #7 I'm not sure if we need something other than name as a automatic heading element.

Either that or a helper.

It's annoying to break rendering when refs have no targets (e.g., typos, work-in-progress).

Catching errors and logging them out is nicer.

I accidentally removed the logic. Let's bring it back a bit.

For input, full HTML headers can be cumbersome and are more a preamble.
For output, to feed into CMSs etc.

The combined example from the readme is what I mostly use, so lets add it as an npm script.

I forgot to do this.

Let's redo #12.

If no statements are found, we get an error. Let's avoid that.

When processing fragments, there will be no title tag.

This should really go on https://github.com/pkra/tools-for-math-on-the-web somehow

• http://visjs.org/network_examples.html
• jsxgraph
  • e.g., http://jsxgraph.uni-bayreuth.de/wiki/index.php/Category:Examples, http://jsxgraph.uni-bayreuth.de/wiki/index.php/Even_simpler_function_plotter
• https://github.com/mauriciopoppe/function-plot
  • e.g., with mathjs computation: http://mathjs.org/examples/browser/plot.html
• https://cindyjs.org/
• http://sigmajs.org/
• https://plot.ly/javascript/
• https://bramp.github.io/js-sequence-diagrams/
• http://js.cytoscape.org/
• https://github.com/wbkd/awesome-d3
• https://mermaidjs.github.io/
• https://github.com/OpenKieler/elkjs
• https://github.com/theia-ide/sprotty
• https://github.com/ivanceras/svgbobrus
• all libs supported by https://github.com/asciidoctor/asciidoctor-diagram
• https://casual-effects.com/markdeep/
• From https://github.com/sindresorhus/awesome (check for more)
  • https://github.com/zingchart/awesome-charting
  • https://github.com/wbkd/awesome-d3
  • https://github.com/willianjusten/awesome-svg/blob/master/topics/Libraries.md

This should really go on https://github.com/pkra/tools-for-math-on-the-web somehow

• http://visjs.org/network_examples.html
• jsxgraph
  • e.g., http://jsxgraph.uni-bayreuth.de/wiki/index.php/Category:Examples, http://jsxgraph.uni-bayreuth.de/wiki/index.php/Even_simpler_function_plotter
• https://github.com/mauriciopoppe/function-plot
  • e.g., with mathjs computation: http://mathjs.org/examples/browser/plot.html
• https://cindyjs.org/
• http://sigmajs.org/
• https://plot.ly/javascript/
• https://bramp.github.io/js-sequence-diagrams/
• http://js.cytoscape.org/
• https://github.com/wbkd/awesome-d3
• https://mermaidjs.github.io/
• https://github.com/OpenKieler/elkjs
• https://github.com/theia-ide/sprotty
• https://github.com/ivanceras/svgbobrus
• all libs supported by https://github.com/asciidoctor/asciidoctor-diagram
• https://casual-effects.com/markdeep/
• From https://github.com/sindresorhus/awesome (check for more)
  • https://github.com/zingchart/awesome-charting
  • https://github.com/wbkd/awesome-d3
  • https://github.com/willianjusten/awesome-svg/blob/master/topics/Libraries.md
• https://d3-discovery.net/
• observable (d3 / js notebooks)
  • https://simonwillison.net/tags/observable/
  • https://beta.observablehq.com/@mbostock/five-minute-introduction

https://github.com/scoskey/m522

When running server-side, we should handle MathJax as well.

Figure out YAML metadata as a more humane alternative to json.

It should be something related to making a title, header etc but all words are overloaded.

Accidentally pushed part of this in 4bbd79e.

Let's add the underlying file.

I.e. try to convert in either direction latex to/from laml.

E.g., add links to emmet documentation, add links to demo videos.

Simple enough.

Our front page should have a sample table (or whatever) with three columns: source code, output code, and rendered product. It makes it so people can grok in 3 seconds what we're up to. This is how markdown is explained in wikipedia.

@scoskey says: "statements are more like (fixed-position) figures, free of page hierarchy".

We could customize the tag name for the "heading".

What's up with that.

• create DLs
• customize citation marker content
  • allow customization per item?
• add example generated from JSON

Simple enough.

Ahead of #34, let's have a separate samples document and move the existing sample to it.

Let's add a simple PDF generator.

For example, m522 goes from 8.2 to 2.8MB unzipped; the amount of extra nodes makes for much faster rendering by browsers as well.

Now that we have webpack and reload, we can combine them.

We spent a good deal of time thinking before arriving at our approach.

If names only appear in other elements, should they be custom handled there?

We'd still have a helper for it but we'd only use it within another module.

E.g., pass a selector, customize name/blame handling.

aCf. also #7

Make nonempty contents of "ref" and "cite" tags replace the default anchor contents.

• in text-nodes (e.g., *...*)
• paragraphs (commonmark needs line-breaks after tags; maybe just add some to whitelisted elements?)

Natural step.

Feels wrong to have that in the source.

I didn't change the mode to the correct type (it's still on what mathjax-node-page uses).

E.g., for chapters.

A module shouldn't fail if it's not used (e.g., if no yaml data is found).

Just some aesthetic edits like parentheses and line breaks

• allow CLI
• move to bin

It might be useful to have a dedicated helper that applies renameTag to all matches for a given selector.

It might even return an array of results for further processing.

@scoskey what do you think?

Counters. We need them.

@scoskey what requirements do you see?

It currently won't run through node.

We should move the CSS into the modules and build it out.

Split out and build for production.

• helpers
• metadata
• preamble
• abstract
• statements
• figures
• names
• blames
• refs
• bibitems / citations
• (foot)notes
• bibliography