pkra / laml-wc

A continuation of an experiment

laml-wc

⚠️EXPERIMENTAL⚠️

A continuation (of sorts) of the laml experiment.

Boring web components for writing.

laml-wc's Issues

SSR

Let's add a demo/test to render server-side.

reconsider name-

We use it for sections, theorems and proofs.

It creates headings, so we probably want to limit them to sectioning. Maybe just call it heading- then?

look into penrose (for cichon's diagram)

Penrose https://penrose.cs.cmu.edu/ recently popped up on my radar again and still seems actively maintained.

It might be nicer for generating diagrams from plain text.

table of contents

or other navigation

of course there are tools that automatically generate such...

dual design

I think I'd like to do a dual design - web and print - to see how far we can take a "single source" approach.

think about proof-

Following #1's final change, I don't think the combination of proof- and blame- is good. Instead of overcomplicating statements, maybe it needs to be something entirely different?

move script to end of body

From #6 (comment)

While making them work, I ran what looks like an initialization issue. The connectedCallback was running before the children are in the DOM. Not sure why this hasn't happened earlier. I'm guessing we load the JS in the head and thus we can't assume everything has been parsed yet? Weird. Moving the script to the end of the body seems to resolve it. (And maybe we should really import as module and initialize when the DOM is ready.

work out a JS solution in lieu of CSS counters

From #3 (comment)

As it turns out, counters are hard (for me). First, I had to do the bad thing and grab some code from SO to get a counter to work at all -- and not understanding enough about custom elements and their constructors to really be sure it's how I'd like it to work -- plus, what I have right now wouldn't survive re-arranging the DOM.

Second, there's the problem of counter reset. The "best" I've come up is resetting in the constructor of the sectioning element. But of course that means I need custom elements for all sectioning. Probably not a huge deal since we only have section in HTML.

But still. It all feels horrid since CSS counters give me all of this for free.

This comment should be for a new issue, I suppose.

proofs should not be enumerated

Following #4, we can now disable numbering for proofs.

better SSR

Let's improve the SSR setup to make it easy to build.

naming

Maybe overhaul the names. Let's collect ideas

• statement => enunciation
• refactor enunciation generation
• blame => something title-ish?
• name => heading-ish?
• ...

revise proof

Following the discussion in #10, let's

• stop inlining proof-label into first paragraph
• add some generated qed after the proof

go through laml backlog

What's interesting from https://github.com/pkra/laml/issues ?

• pkra/laml#50 - check again later
• pkra/laml#7 - not sure what this was after
• pkra/laml#11 - in the sense that we haven't touched that subject yet

next steps for ref-

As expected, #3 is not good enough for all of m522.

As a first complication, there's a ref- pointing to the cantor set figure - not a theorem, thus no label to be found.

optional qed placement

From our last conversation, @sgcoskey would like a qed at end of proof (which we now have) BUT also the ability for an optional placement of qed.

add landing page and SSR output

For pushing something to GH pages, I'd like a landing page and SSR output.

sprinkle some aria

Some ideas

• h- could label their parents
• enunciation should be figures and their labels captions
• ...

add pagedjs demo

As already hinted at in mj.js, I had a working pagdejs demo but then something made pagedjs crash.

Let's try to bring it back.

make ref- do something interesting

It should populate its text with something worthwhile.