Closed Jazzpirate closed 2 years ago
ad. sTeX-compatibility: MiKoMH does not use any more compatibility than smglom and (like SMLoM) does not intend to use any. This is why I propose to get rid of stex-compatibility.sty
completely and not release it at all. That also takes care of the Maybe comment after that.
ad. sTeX-compatibility: MiKoMH does not use any more compatibility than smglom and (like SMLoM) does not intend to use any. This is why I propose to get rid of
stex-compatibility.sty
completely and not release it at all. That also takes care of the Maybe comment after that.
Even better - but I don't see how it solves the latter point - that's mostly about "how do we organize the smglom better", splitting up big modules into small ones, having separate files for declarations+documentation, "formal" definitions (in particular where multiple definitions exist), examples, theorems etc, maybe merging some fragments from MiKoMH in there to have some less formal sparagraphs in there too... all the things that people should be able to reuse, or might be relevant for guided tours that are more "generic" than specific MiKo-courses etc
you are right, it solves the compatibility layer problem, not the "showcase" problem. About the showcase, I am all against having two copies of smglom (one showcase and one "real"). If you want to showcase things, use HelloWorld.
you are right, it solves the compatibility layer problem, not the "showcase" problem. About the showcase, I am all against having two copies of smglom (one showcase and one "real"). If you want to showcase things, use HelloWorld.
It's not (just) about showcasing things - the "showcase" library is what the smglom should (in due time) be, after a thorough refactoring ;) The main thing is that refactoring the whole smglom will be very time consuming, so I think it's a good idea to start early, plan a somewhat decent repository/directory/namespace structure that we want to use and start refactoring a small fragment (e.g. mv and all-the-things-in-sets-that-aren't-actually-about-sets). Then the result can serve as both a showcase and as something that e.g. we can have students fill up with the content in the (current) smglom
yeah, then I agree fully.
But the refactoring is dangerous, since it can break anything that references the SMGloM. So indeed, we should start this early, while all the content in danger is mine.
Yes - which is also why I would prefer a separate git group/repo rather than branches that would have to be switched etc.
Then the "old" smglom can just continue to exist, you can keep using them, other people can use them (being aware that it's "deprecated"), and the new one is what we encourage people to actually use and extend :)
On that note: At some point we're going to need a "deprecate and redirect" mechanism of some sort, for change management. But I would defer that to some later point
\definiendum, \definame, \symname brauchen root=,post=,pre= \synonym = \symref + root=,pre=,post=
\symdecl\symdef\notation switch argument order
\vardef*[varn,varm]{Let $\varnot[varn]{n},\varnot[varm]{m}$, be \symtype[varn,varm]\NaturalNumbers{natural numbers}} such that \premise{...}
Can we close this, after all, the release has happened.
I spun out the remaining three todos, closing
\vardef*[varn,varm]{Let $\varnot[varn]{n},\varnot[varm]{m}$, be \symtype[varn,varm]\NaturalNumbers{natural numbers}} such that \premise{...}
MiKoCourses/AI/source/SS20/orig.exam.en.tex
do not even run through that should be fixed).{sproblem}
, that behaves like{sexample}
in that its presentation can be specialized.stex-compatibility
<- this is not an sTeX-TODO, that's more like an smglom-TODO - nothing in compatibility "should" be used at all, but the smglom might in some instances, and MiKoMH probably does a lot.[args=ai]{foo}{[#1]_{#2}}{##1 + ##2}
instead, expand to{[\stex_assoc:nn{#1}{##1 + ##2}]_{#2}}
type=symdoc
for sparagraph (MMT)assoc=
key for symdef (how to "resolve" associative arguments):bin
(associative binary),binl
(left-associative)binr
(right-associative),pre
(as in nested quantifiers),conj
(conjunctive, as in a=b=c => a=c /\ b = c, or a,b=/=c => a=/=c /\ b=/=c),pwconj
(pair-wise conjunctive, as in a=/=b=/=c), ...\symname
and\comp
whenever the definition is in the same document. After all, that is the only direct benefit we provide for all that markup.