The REPL is really just there to provide a simple interface to the running web server for debugging your apps. That said, it _is_ a full-on Node.js REPL so you can pretty much run any JavaScript you want in it.
(I’m not going to even pretend I understand what you’re using it for but it’s fun to see folks playing with it in ways I never imagined.) :)
the main thing for me (still quite a while til I need to use it) is that the kitten eepitch is a very convenient interface into the #kitten's kittendb (from inside #emacs).
So the kitten eepitch can be used to read and set values that determine what pages are generated, in real time.
@eduardoochs we must convince Aral to adopt your category diagrams for Kitten's database typing ;p
(The typing diagrams are elsewhere, and not as polished. Long story - and long story later...)
Wouldn’t it be easier to use JSDB directly or to create a very lightweight executable that provides a REPL interface to it? (Unless you’re also using Kitten as a web server) :)
PS. JSDB: https://codeberg.org/small-tech/jsdb
http://anggtwu.net/2024-find-tryit-links.html
I will try to write something like that for kitten this evening. It will be very prototype-ish, as I only started using kitten yesterday, but whatever... =)
A question: is there an easy way to make kitten display its requests, like "Requested foo/ - generating page from foo.page.md"?
Note: I am running kitten from a shell inside emacs, with no global configurations at all...
A space for Bonfire maintainers and contributors to communicate
