On Mon, Nov 04, 2024 at 10:18:41PM +0100, Grégory Vanuxem wrote:
> That’s interesting, I will look at how SAGE folks manage this, thanks.
>
> In fact, as of now, my primary concern is formatting examples in a "not"
> ugly way. Furthermore, I am not at a stage where \example{}s are clickable
> and executed in an Xterm like HyperDoc do, just api.spad does not seem to
> handle them. I also do not know how HyperTex processes their commands,
That is all documented in chapter about writing HyperDoc pages.
There is small number of base constructs understood by HyperDoc:
- \lisplink
- \windowlink
- \spadcommand
- \unixommand
with some variants + bunch of formatting constructs. HyperDoc has
macros and the rest expands to those above. In particular '\example'
expands to '\spadcommand' with some added formatting.
During normal operation HyperDoc is connected to FriCAS and may
request computations, '\lisplink' and '\spadcommand' send expression
which is evaluated as Lisp or FriCAS input expression respectively.
Some HyperDoc features are realized by dedicated functions written in
Boot, in particular browser is done in this way. More precisely,
HyperTex macro expand to a command which sends Lisp code to FRICASsys.
FRICASsys evaluates Lisp code which generates page content which is
then rendered by HyperDoc. Currently this depends on Lisp and Boot.
But with small changes this code could be written in Spad. In
particular in my private version, part of this is done by Spad code.
Commands are still sent as Lisp commands (to avoid large changes in
other parts) and actual content is still generated by Boot code (it
needs much more work before all this is handled by Spad), but page
data is gathered in Spad data structures and actual sending of data
from FRICASsys to HyperDoc is done by Spad code.
--
Waldek Hebisch
--
You received this message because you are subscribed to the Google Groups
"FriCAS - computer algebra system" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/fricas-devel/ZzA3tBE4qwvzgqi6%40fricas.org.
