Time Nick Message 02:13 ghoti Anyone here in a position to comment on whether contributions to the minetest wiki are welcome? I could add a bit if I had an account.. 02:58 MTDiscord via the wiki itself https://wiki.minetest.net/Wiki_guidelines https://forum.minetest.net/viewtopic.php?f=3&t=10473 source found under contributing to the wiki: https://wiki.minetest.net/Main_Page 03:17 ghoti Thanks. 03:20 ghoti Heh. The forum post that describes account creation states "You can also ask for an account on IRC. 03:20 ghoti " 03:30 MTDiscord i noticed that lol, probably no one who can make one is free right now shrug 11:02 pgimeno ghoti: ping Calinou 11:37 Calinou ghoti: send me a message with your email address and desired username (note that it will start with an uppercase character due to MediaWiki limitations) 11:37 Calinou /msg Calinou 12:00 ghoti Will do, thanks. 20:02 v-rob Let's assume for a moment that the GUI API is rubenwardy's proposed Lua table DSL. How would the API look for dynamically updating elements? 20:02 rubenwardy probably give an id, and then replace it 20:03 rubenwardy I feel like dynamically updating elements is a sscsm thing 20:06 v-rob If we do create GUIs from the ground up with a new syntax, there will probably be a big push for dynamic updating 20:07 v-rob Especially since SSCSM doesn't seem like a reality anytime soon. 20:08 v-rob I would love to use SSCSM for this, but I don't know how likely it is 20:08 v-rob Anyway, how would styling work? Like HTML+CSS where styles are global, or like what we have now where they only affect elements after them? 20:10 rubenwardy I would prefer the former, it's simpler when you're dealing with a tree 20:10 v-rob I agree 20:12 Krock static CSS, and replacing only named elements directly 20:13 v-rob Not sure what you mean 20:14 Krock if you let modders replace styles, then priority will become a problem 20:14 Krock thus, styles would be best to be kept static, and only named elements may be replaced on the fly 20:16 v-rob Ah. So you're basically saying that only inline styles should be updated and not style elements? 20:17 v-rob That makes sense. CSS priority rules are a pain 20:17 Krock I'm not sure if that's what I meant but yes maybe 20:19 Krock though refreshing the entire GUI is way easier than updating it dynamically 20:20 Krock KISS 20:20 v-rob Definitely true 20:22 v-rob TBH, if we make an event system that automatically updates the GUI definition and calls callback functions, you could just edit what you need and reshow that same GUI definition 20:22 v-rob Main problem is that e.g. clicking and dragging a scrollbar will stop when the GUI updates 20:23 v-rob SSCSM would be nice. Splitting a GUI between server and client is a pain 20:27 v-rob Who is working on SSCSM? (if anyone) 20:28 MTDiscord No one wants to because of the supposed politics surrounding it 20:28 v-rob Oh yay 20:32 v-rob Maybe if I developed a new GUI system for CSM with no SSM API, it would entice people to work on SSCSM because they don't want to keep using formspecs. Hmmm... :) 20:41 v-rob The actual result would probably be that people make SSM mods that have CSM dependencies. That would be wonderful... 22:25 numzero Regenerating the GUI sounds nice until you have that actually: 22:26 numzero * If you do it in a simple way like it is done currently, it wipes all the text user entered so far 22:27 numzero (with the current formspecs that happen when the server resends it for whatever reason, when you resize the window, etc.) 22:27 numzero * Doing it in a way preserving user input means there is now some state to be kept, so it may not be in any way easier than to keep the whole GUI tree 22:31 numzero esp. remembering that it should keep not only the input itself but also things like cursor and scroll position 22:31 numzero it would be very annoying otherwise (like it is currently) 22:54 numzero Actually one should *never* change GUI layout while it is open. That races with the user’s mouse. 22:59 numzero Aside that and user-editable content (which shouldn’t be changed for the same reason), little remains: things like button enabled-ness, read-only texts, etc.