| Time |
Nick |
Message |
| 01:59 |
|
mrcheese joined #luanti-docs |
| 04:20 |
|
Blockhead256 joined #luanti-docs |
| 04:21 |
Blockhead256 |
hey, does this project/the engine have a tech stack diagram? |
| 04:21 |
Blockhead256 |
Was wondering if this thing I made has any value https://old.reddit.com/r/Luanti/comments/1pxhi5d/luantis_current_tech_stack_with_paths_so_you_can/ |
| 04:23 |
MTDiscord |
<wsor4035> i dont? think so |
| 04:23 |
MTDiscord |
<wsor4035> the engine dev section might something |
| 04:23 |
MTDiscord |
<wsor4035> that chart is kinda funny since it talks about opt depends, but never hard depends |
| 04:24 |
MTDiscord |
<wsor4035> this thing exists https://docs.luanti.org/images/minetest-0.3-dfd-visio.webp |
| 04:28 |
Blockhead256 |
well it was meant to bew interpreted (optional-) as.. well, optional. i.e. "dependencies" and "optional dependencies" |
| 04:28 |
Blockhead256 |
"Horribly many things" lol |
| 04:30 |
Blockhead256 |
s/bew/be |
| 04:31 |
Blockhead256 |
well if ye think my diagram or something like it would be helpful, I could do it up properly |
| 04:33 |
MTDiscord |
<wsor4035> here is an idea |
| 04:33 |
MTDiscord |
<wsor4035> https://cdn.discordapp.com/attachments/926231483155378176/1454693603317252241/image.png?ex=6952047d&is=6950b2fd&hm=147a7ea4002b7a6c8b080ec38127c0fd64a82c98f7b5c02d57c9cbf64b567a18& |
| 04:34 |
MTDiscord |
<wsor4035> but idk, sure |
| 04:34 |
Blockhead256 |
that makes some sense I guess yeah |
| 04:35 |
Blockhead256 |
If I do it up as an SVG, we should be able to embed it into a page properly, with selectable text |
| 04:35 |
MTDiscord |
<wsor4035> dunno if you can in markdown with hugo |
| 04:35 |
MTDiscord |
<wsor4035> there is one rule, it needs to look like a mspaint product :juanchi_face: |
| 04:36 |
Blockhead256 |
yeah if you make it look too good, people might assume it's meant to be definitive. Like prototyping a UI |
| 05:00 |
|
MTDiscord joined #luanti-docs |
| 05:09 |
|
Blockhead256 joined #luanti-docs |
| 06:38 |
MTDiscord |
<a.corp.serot> Blockhead256 You could try mermaid diagrams |
| 09:22 |
|
Warr1024 joined #luanti-docs |
| 09:47 |
Blockhead256 |
that syntax looks similar to DOT |
| 09:47 |
|
Warr1024 joined #luanti-docs |
| 11:09 |
|
mrcheese joined #luanti-docs |
| 16:15 |
MTDiscord |
<exe_virus> +1 for standard mermaid diagrams, use them professionally all the time. Though I hate the new org that has taken over the product, very clearly trying to take it closed source |
| 16:40 |
Krock |
draw.io would be an open-source (trademarked) alternative |
| 16:41 |
Krock |
or is only the client open-source? I don't know. |
| 17:00 |
MTDiscord |
<mark.wiemer> draw.io is super generic and would need a big style guide to make things consistent, I much prefer Mermaid. Plus draw is GUI, Mermaid is text based 🙂 No idea about this new company in charge of Mermaid but worst case we use a community fork, the open source version is already mature and stable |
| 17:12 |
MTDiscord |
<exe_virus> Basically yep, my thoughts and company's thoughts as well |
| 17:17 |
MTDiscord |
<mark.wiemer> For anyone curious, "Mermaid Chart" is the company in charge and also the name of a new product https://docs.mermaidchart.com/blog/posts/mermaid-chart-the-evolution-of-mermaid |
| 19:49 |
MTDiscord |
<a.corp.serot> Ah i was not aware of the company, or that it even had a company and not a community thing |
| 19:52 |
MTDiscord |
<a.corp.serot> The appeal for me is mostly being something resembling code that i could reasonably recommend putting into a git repo :) |
| 22:05 |
|
mrcheese joined #luanti-docs |
