On 18/07/2025 16:52, Waldek Hebisch wrote:
You are confused. FRICASsys is main FriCAS process, it runs when you
run FriCAS. API pages are generated when you do 'make doc' or
'make localdoc', that is they are generated as part of build process,
and then used as fit, either put on a web site or accessed
locally. Anyway, API pages are generated by FRICASsys, but intent
is to do this once. HyperDoc generates pages on the fly allowing
more complex interaction. At least now my intent is to support
only local use: current HyperDoc protocol allows triggering
arbitrary computations from a request. Before allowing access
from the net it would have to be reworked quite a lot to limit
it only to allowed actions.
Thank you, that makes it clearer, I find it hard to understand the top
level information flow without a diagram so this is my attempt:
Existing Code
-------------
build process such as make doc
library ---> database ----> .rst ---> Sphinx ---> HTML
source tables files (static web pages)
code |
v
HyperDoc -----boot
started by code
C code ^
|
.ht
file
Planned Code
-------------
build process such as make doc
library ---> database
source tables
code | |
SPAD +----------<-----------+ can javascript
code | call SPAD code?
v |
browser -----HTML ---- > Javascript --> SPAD
started by files code
user |
server for
more complex
requests
--
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/4ea0d977-b0a4-4f0a-811e-f893e4b0e87f%40martinb.com.
