| Time |
Nick |
Message |
| 03:06 |
MTDiscord |
<wsor4035> for yall talking about lua api docs in such, https://github.com/luanti-org/docs.luanti.org/issues/303 food for thought. obviously its wuzzy being wuzzy and ranting, but if the lua api is transformed into something, should take into account the previous minetest docs stuff |
| 05:00 |
|
MTDiscord joined #luanti-docs |
| 06:43 |
MTDiscord |
<a.corp.serot> the API spec probably could only absorb information from docs.luanti.org about a limited set of things. For now, i think my interest is specifying just the types and functions that Luanti provides and uses. |
| 06:43 |
MTDiscord |
<a.corp.serot> in the future, perhaps the spec could describe formspec syntax, texture modifiers, l-system trees, schemas (world format, settings/confs, schematics, networking, etc. but that's definitely not gonna be things considered until the "main" API has been decided. smaller steps seem more approachable for all of us i think. |
| 06:54 |
MTDiscord |
<a.corp.serot> hmm, i hadn't really considered about how to include examples and admonitions into the spec |
| 06:55 |
MTDiscord |
<a.corp.serot> or if not desired to lump examples into it, then a way to describe examples of things in use |
| 09:22 |
|
Warr1024 joined #luanti-docs |
| 09:47 |
|
Warr1024 joined #luanti-docs |
| 10:46 |
|
mrcheese joined #luanti-docs |
| 11:36 |
|
mrcheese joined #luanti-docs |
| 13:40 |
MTDiscord |
<sheriff_u3> Some docs that I have used with before: https://github.com/Bloxdy/code-api (you may want to note that this docs is written for an API in a JavaScript/Typescript environment.) |
| 13:41 |
MTDiscord |
<sheriff_u3> It may not be a bad idea to look into other docs formatting to see what qualities we wish for ours. |
| 16:03 |
|
Desour joined #luanti-docs |
