Time Nick Message 00:01 MTDiscord even with <1> syntax, it wants it to be ordered 00:02 MTDiscord That's what I saw, we can probably just manually number them outside the code block though and not use the fancy syntax there 00:02 MTDiscord so the table thing I showed above 00:03 MTDiscord or a horizontal d-list 00:03 MTDiscord a what now 00:07 MTDiscord https://cdn.discordapp.com/attachments/926231483155378176/928439530980270110/unknown.png 00:07 MTDiscord https://cdn.discordapp.com/attachments/926231483155378176/928439624609718312/unknown.png 00:07 MTDiscord the lone + says "attach this to the previous block" 00:09 MTDiscord ah 00:15 MTDiscord https://cdn.discordapp.com/attachments/926231483155378176/928441614303653938/unknown.png 00:16 MTDiscord I think that works 00:16 MTDiscord now my question is, what does the docbook output look like? 00:17 MTDiscord how do I figure that out 00:17 MTDiscord https://docs.asciidoctor.org/asciidoctor/latest/docbook-backend/ 00:25 MTDiscord https://cdn.discordapp.com/attachments/926231483155378176/928444016951984148/unknown.png 00:25 MTDiscord It is easier to parse from code though, being XML? 00:25 MTDiscord ie, will it be easier to drop it into an XML parser and use that in tooling? 00:26 MTDiscord Im sure node has a decent XML parser 00:26 MTDiscord So that's a "maybe" 00:26 MTDiscord anything easier than what we have, yeah? 00:27 MTDiscord true 00:27 MTDiscord html output works 00:30 MTDiscord So are we cool with this format? 00:30 MTDiscord it gets my vote 00:31 MTDiscord if I want custom macros do I need to do some ruby stuff 00:31 MTDiscord for real fancy stuff yeah 00:31 MTDiscord I like how it looks. 00:32 MTDiscord I'll probably set up some editor macros for right now 00:32 MTDiscord Are the numbered lists contributing anything? 00:32 MTDiscord overloads 00:32 MTDiscord only used if there are multiple return cases 00:32 MTDiscord leave them out otherwise? 00:32 MTDiscord yeah 00:32 MTDiscord Gotcha. 00:39 MTDiscord https://cdn.discordapp.com/attachments/926231483155378176/928447548870520852/unknown.png 00:39 MTDiscord https://cdn.discordapp.com/attachments/926231483155378176/928447606886129724/unknown.png 00:39 MTDiscord https://cdn.discordapp.com/attachments/926231483155378176/928447696996552744/unknown.png 00:40 MTDiscord https://cdn.discordapp.com/attachments/926231483155378176/928447812797091860/unknown.png 00:40 MTDiscord (ignore the incorrect return values on vehicle new) 00:40 MTDiscord Where can I find these minetest docs or are they not available yet? 00:41 MTDiscord we're making them right now 00:41 MTDiscord Soon™️ 00:42 MTDiscord Can you have a snippets section on each page? It doesn't have to be filled in rn, but they can be collected (automatically?) and snippets make coding so much easier 00:43 MTDiscord theres a snippet on the last one 00:43 MTDiscord its right there 00:43 MTDiscord The psage section is a good start 00:43 MTDiscord big red letters "Example 1" 00:43 MTDiscord I see that but ignored it because in was about vehicles, not minetest XD 00:44 MTDiscord Ok, that good! 00:44 MTDiscord the example is related to Minetest more than you'd think :] 00:44 MTDiscord but we will have collections of more snippets externally linked probably 00:44 MTDiscord but thats for later 00:45 MTDiscord I really need some macros for this 00:46 MTDiscord I really wish that there were ways to make basic macros that carried actual syntax 00:48 MTDiscord there is a hack to do it 00:48 MTDiscord https://stackoverflow.com/a/37397532 00:48 MTDiscord its gross though :] 00:49 MTDiscord Not the worst, I think I had a similar idea a while back but want to avoid includes everywhere 00:50 MTDiscord you could substitute the include 00:50 MTDiscord hack the hack 00:50 MTDiscord Nope 00:50 MTDiscord include:: is a preprocessor macro 00:50 MTDiscord darn 00:50 MTDiscord it works differently and before the main asciidoc stuff, that's why it's able to insert actual syntax 00:51 MTDiscord We can just make the table header it's own includable adoc file ofc 00:51 MTDiscord wdym? 00:52 MTDiscord make an include/ptable.adoc and include it 00:52 MTDiscord it would have the table header in it 00:52 MTDiscord the [] thing? 00:52 MTDiscord include::file[] is the include macro, file being the file you wish to include 00:52 MTDiscord I mean the table header 00:52 MTDiscord its the [%auto, frame] thing right? 00:53 MTDiscord yeah 00:53 MTDiscord and possibly the |=== 00:53 MTDiscord really, the rows themselves are fine 00:53 MTDiscord and honestly, if we could set the default table properties then I'd be fine 00:54 MTDiscord how do you put newlines in variables :thonking: 00:54 Desour_ (btw, if someone wants to see the vehicle example in ldoc: https://0x0.st/ozfP.zip ) 00:55 MTDiscord Is vehicle going to be a special type of minetest object optimized for attachment? 00:56 MTDiscord its just out example, for the template 00:56 MTDiscord *our 00:56 MTDiscord MisterE, you know this project is to revamp the existing documentation, right? 00:57 MTDiscord yes 00:57 MTDiscord @GreenXenith append + to the end of the line, after a space 00:57 MTDiscord But you gave me a teaser and it teased me 00:57 MTDiscord note that you will have to inset an extra blank line to make something a new paragraph/block 00:58 MTDiscord can you not use variables for table headers 00:58 MTDiscord or am I just doing something wrong 00:58 MTDiscord not afaik, but I have an idea 00:59 MTDiscord darn, {begin-table} | foo | bar {end-table} would have been nice :/ 00:59 MTDiscord Desour_: The main reason we dont want to use DSL like ldoc is because of how difficult it is to write 00:59 Desour_ yeah, maybe you should use something as example of which people will think less likely that it will really be added to minetest, what about VoxelEntity? 01:00 MTDiscord sscsm is clearly the way to go then /s 01:00 MTDiscord The point is its supposed to be fake 01:00 MTDiscord its a template 01:00 MTDiscord im leaving it as vehicle 01:00 MTDiscord It's a joke, green 01:00 MTDiscord I wasnt responding to your joke 01:00 MTDiscord his is a joke 01:01 Desour_ :] 01:01 MTDiscord VoxelEntity doesn't exist and probably never will :-) 01:01 MTDiscord Not in the engine, anyways 01:01 MTDiscord (as the creator of the only VoxelEntity implementation worth beans, I take offense to that) 01:02 MTDiscord anyway whats your idea for table stuff 01:02 MTDiscord How about 'meme' 'meme.new' 01:02 erlehmann how about omskbird 01:03 erlehmann bring back oerkki 01:03 MTDiscord Yeah actually this prob isn't helping 01:03 MTDiscord I was thinking that maybe having it insert a passthrough block would work, but it doesn't seem to be 01:03 erlehmann VoxelEntity is not real it can't hurt you 01:04 MTDiscord VoxelEntity: https://github.com/GreenXenith/lvae/ 01:04 erlehmann GreenXenith btw, did you make some ship or airship mod with that? 01:04 MTDiscord I have not ported my original ship mod to it yet 01:04 MTDiscord Maybe ill work on that this week 01:05 erlehmann wait you have an original ship mod that is similar? 01:05 MTDiscord The first version of the mod was for making ships, before I turned it into a general api 01:05 MTDiscord I might have a screenshot somewhere, but #minetest-irc 01:18 MTDiscord So, any other ideas @Benbob0329 ? 01:18 MTDiscord or should I figure out how to ruby this 01:22 MTDiscord I don't have any other ideas, I expect we'll be using the diagram plugin anyways for some stuff so plugins aren't a bad thing 01:22 MTDiscord so should I ruby it? 01:23 MTDiscord meh, that looks complicated ? 01:44 MTDiscord I might try my hand at it sometime, I don't think we need it right now 02:10 MTDiscord Did we decide what property tables should look like? 02:11 MTDiscord Some properties may be self-documented so a def list doesnt really work 02:28 MTDiscord True, c++ supporter voxel entities will probably become a thing in minetest, someday. They'd be restricted in size, probably represented as a mapblock, and have a pre-calculation pass like the terrain so that it behaves as one .obj like object until built onto 02:28 MTDiscord #minetest-irc for further vae please 02:29 MTDiscord Sorry, just musing in my one minute I have today to spare. 02:29 MTDiscord ? 17:40 MTDiscord Fun fact: docs.microsoft.com is running on markdown 17:40 MTDiscord With a lot of customizations haha. 17:53 MTDiscord haha noice 17:53 MTDiscord https://cdn.discordapp.com/attachments/926231483155378176/928707739071430686/unknown.png 17:54 MTDiscord btw, any preferred ways for me to document the default values? if noone feels strongly about this, i will do it in a bullet point, under the internal/field type 18:27 MTDiscord also, benrob, what do you mean by "Use a named example block please."? 18:43 MTDiscord @Luatic the default values i put are the ones in object_properties.h, i dont have the the to dig into the minetest pit to find out if it is changed elsewhere 18:43 MTDiscord Well sorry that's incorrect 18:43 MTDiscord Because we're documenting the Lua API 18:44 MTDiscord So you have to look at the defaults that are set if the values aren't set in the Lua table 18:44 definitelya Oh right, there's no ilbot here. 18:44 definitelya cya 19:25 MTDiscord I mean to use an example block, and give it a name 19:25 MTDiscord https://docs.asciidoctor.org/asciidoc/latest/blocks/example-blocks/#delimited 19:33 MTDiscord I see 19:35 MTDiscord You can place a source block inside an example if its delimited 19:35 MTDiscord Will fix that tmr(i think) 22:23 MTDiscord Maybe I can find where other default values are set.