Building the wiki's dom tree in #lisp.
https://github.com/XXIIVV/Oscean/blob/master/scripts/lisp/graph.lisp
@neauoire I hope you don't mind my totally ignorant question. I've been following your transition from Riven to Lisp but this question pops in my mind every time: WHY
What do you do in your blog with Lisp, that is more convenient than just JS?
Because I asume it's work the effort of using a Lisp interpreter just for that... But I don't get it
Feel free to ignore my question though :)
@croqaz that's a fair question! The answer is simple, for fun.
But it's a bit more complex than that in reality. So, here's a better answer:
I use LISP as markup language(the thing to say which word should be bold, how to write tables, and so on.)
So, there's multiple choices for that, here's 3:
HTML: <a href='https://link.com'>some link</a>
MARKDOWN: - [some link](https://link.com)
LISP: (link "https://link.com" "some link")
@croqaz Oscean uses LISP as markup, since it's a lot more flexible than the other two, for instance I can make a link bold, and fetch some dynamic data from the page and print it, and so on.
But I had this stack that existed at the deepest layer of the wiki, all I did was kind of expand its reach, so instead of just being used on the text of pages, it is also used to decide which page should be displayed. It already had all the parts, I just had to push it a bit.
@croqaz I don't do that because it's kind of a pain, but if you're going to make a list of books and things, consider making it in indental so we can aggregate the list in our wiki!
https://github.com/XXIIVV/Oscean/blob/master/scripts/database/glossary.ndtl
Aggregator: https://webring.xxiivv.com/wiki.html