Time Nick Message 03:20 Louder Hello 03:21 Louder guy's, I starter to learn minetest modding, is there anyone here willing to help me with some very simple questions? 05:18 MTDiscord This channel is for C++ dev. You should try #minetest 05:26 LoneWolfHT nvm they left 11:49 pgimeno Louder: this channel is for engine development, not mod development. Try #minetest instead. 11:53 Louder Hello. Is there anybody who can help me with a some questions about minetest modding? 12:06 pgimeno Louder: this channel is for engine development, not mod development. Try #minetest instead. 12:59 jingkaimori Which version of irrlicht are we use 13:01 jingkaimori Do minetest use the newest version of irricht? 13:04 jingkaimori Do minetest use the newest version of irricht? 13:07 sfan5 yes 13:07 sfan5 which is irrlicht 1.8 13:09 jingkaimori I need to modify this class to add IME input support 13:09 jingkaimori minetest\src\gui\intlGUIEditBox.cpp 13:11 sfan5 you probably need to modify code inside irrlicht too 13:12 jingkaimori But it seemed to be an irrlicht class.Are something needed to edit irrlicht module? 13:12 sfan5 it might be easier to defer to a framework like GTK to implement IME support 13:12 jingkaimori Such as export the change to irrlicht svn repo 13:14 jingkaimori but import a heavy lib only for IME is unnecessary,so handle IME directly will help 13:16 sfan5 true 13:16 sfan5 but it could be easier 13:18 jingkaimori Developer and player in linuxfolks had talked this issue, they think it will be hard to draw gtk component above irrlicht context 13:19 sfan5 you can display a borderless window with a text input field at the same position 13:26 celeron55 integrated IME would be impressive but is it practically possiblw? 13:26 celeron55 e* 13:26 jingkaimori hack into irrlicht and it will be possible 13:26 jingkaimori but irrlicht is host on a svn repo,not git 13:27 jingkaimori I'm cloning this repo using `git svn` 13:30 jingkaimori Current verson of irrlicht don't return anything about IME, so adding an SEvent called IMEEvent is the solution 13:31 sfan5 in theory you could reuse text paste handling but that'd be a hack 14:51 zughy[m] Merry Christmas https://forum.minetest.net/viewtopic.php?f=7&t=25909 15:18 pgimeno reminds me of this: https://irc.minetest.net/minetest/2019-04-11#i_5527894 15:18 pgimeno @zughy[m] ^ 15:20 sfan5 didn't we have a PR for redoing the mainmenu yet? or was that just drafts? 15:22 rubenwardy just drafts 15:24 pgimeno by the way, I am pleased to say after seeing the progress in the last few months, that this is no longer true https://irc.minetest.net/minetest/2019-04-11#i_5527952 - thanks everyone for their effort 15:50 zughy[m] sfan5 I've been waiting for 5.4 to roll out, but having time during the holidays I felt like exploring first 15:54 sfan5 uhh, why wait? 15:55 rubenwardy big features can sometimes take more than one release cycle to be merged 15:56 MTDiscord I see 13 PRs with one approval https://github.com/minetest/minetest/pulls?q=is%3Apr+is%3Aopen+label%3A%22One+approval%22 16:01 Krock soon some more. checking a few of them... 16:02 MTDiscord most seem mergeable, starting with the oldest: #7840 16:02 ShadowBot https://github.com/minetest/minetest/issues/7840 -- Degrotate support for mesh nodes by numberZero 16:45 zughy[m] because 1) I feel like core devs are already overwhelmed by issues/PRs and 2) I want to be sure to know what I'm doing 16:46 sfan5 we are overwhelmed but if there's agreement that something is particularily important we can prioritize it 16:46 zughy[m] in fact I'm trying to understand if a soft transition could be viable (today I was making a few sketches) 16:58 zughy[m] oh yes, I also forgot about the roadmap, saying UI improvements 16:59 zughy[m] which I guess it'll become official after 5.4.0 21:24 v-rob About IME input: SDL2 supports this natively with its event system, another reason to use it 21:31 v-rob The question is, if we decide to use our own fork of Irrlicht to use SDL2, which should we use? Irrlicht 1.8.4, 1.9, a fork? 21:32 v-rob To clarify, a 1.9 development version 21:34 rubenwardy why is 1.9 still in-dev? 21:39 v-rob Uhh, because they haven't released it yet? 21:45 sfan5 a fork of 1.9 from before the changes that broke current master were made 21:45 sfan5 basically this exact revision https://github.com/zaki/irrlicht 21:47 v-rob What did break? 22:19 v-rob Would that revision of 1.9 likely have more or less bugs than 1.8.4? 22:20 v-rob It would probably be best to aim for the least buggy version 22:22 sfan5 v-rob: last time I tested some x11 stuff we usually do was broken on the newest rev 22:22 sfan5 generally 1.9 is hopefully less buggy than 1.8 23:23 pgimeno hm, maybe it's just that some things are done differently, I wouldn't call that broken (especially if they are identified and easy to fix)