You don't provide much of a motivation for this, in terms of use cases, so I suppose the motivation exploring minimalistic hypertext design, right?
Konrad Hinsen
03/30/2025, 6:50 AM
The tacit design decisions are: (1) Hypertext is a set of pages in the same file system and (2) Lua as a dependency of the hypertext is fine. The second one is more fundamental here, because you could probably add over-the-wire links easily and compactly if your platform provides networking for you.
k
Kartik Agaram
03/30/2025, 6:52 AM
Yeah, I mentioned one approach that led me down this path in a recent devlog post: making codebases easier to explore by using a tiny markup implementation and also integrating some graphics. But I'm not entirely sure where I want to go myself. So this is all very exploratory.
Kartik Agaram
03/30/2025, 6:53 AM
I think the networking is easy to add. Depends on the use case. For my use cases so far the help browser is self-contained and doesn't need to download any resources over the network. But that will change.
Kartik Agaram
03/30/2025, 6:56 AM
I should clarify "help browser": If you try out the download at the bottom of OP above, it's a help browser that tries to document some bare essentials for programming on top of Lua Carousel, LÖVE and Lua.
Kartik Agaram
03/30/2025, 6:57 AM
So the hypertext browser is 600 lines of code, but there's also 700 lines of hypertext you can bounce around in.
k
Konrad Hinsen
03/30/2025, 7:35 AM
So the current/first use case is software documentation. That's a good one I'd say, given that I am doing that as well in my current project :-)