feature: lua 'script_templates'

[howhow2315]

a simple addition that adds a plugin (tool) which dynamically imports solid Lua script_templates
as apart of this i refactored the lua_repl into a subfolder so the two plugins can coexist

if theres script_templates that are included somewhere in the source code that i missed thatd be very awkward! but i considered that while making this and thought it might be more user friendly to have it be optional like this

[gilzoide]

Hi @howhow2315, thanks a lot for the contribution! Sorry it took me so long to review, lots of stuff happened these last weeks 😅

if theres script_templates that are included somewhere in the source code that i missed thatd be very awkward

There's the LuaScriptLanguage::_get_built_in_templates method that returns script templates. Right now it only ships the "Default" and "Empty" templates.

I think rather than adding a separate plugin that copies script templates to the project's script template folder, a simpler approach would be to change LuaScriptLanguage::_get_built_in_templates to return the built-in templates read dynamically from the addons/lua-gdextension/lua_script_templates folder (we then remove the hard-coded ones and transfer them to there).

---

Another thing, what's the use case for the Object/metatable.lua template? It doesn't seem like it would go well attached to Godot Objects, since they rely on plain tables instead of Godot's object model. I mean, creating an instance with LuaScript.new vs _CLASS_.new would return pretty different things. Is it supposed to be used for creating "pure Lua classes"? If that's the case, I guess it's fine. Maybe it should have some documentation, though, users could get confused about when to use this vs "usual" LuaScripts.

[howhow2315]

the reason theres mostly comments on my thought processes rather than fact checking is 70% of this was done on a plane without wifi lol
no worries or rush at all, and I apologize for a lot it being messy! this was just a quick solution i thought of without digging. dynamically reading it was exactly the original thought i hoped for. and yeah the Object/metatable.lua template is for pure Lua classes which i believe have a solid usecase especially when using LuaJIT. it does fall away from the Godot object model but i think leaving it there with some basic documentation would be good

[gilzoide]

no worries or rush at all, and I apologize for a lot it being messy!

Hey @howhow2315 , don't worry. We are all here to make Lua GDExtension the best it can be and I really appreciate the the help! We should definitely have better support for script templates, so I'm sure we can make something that works for not only both of us, but for all users in general =]

the Object/metatable.lua template is for pure Lua classes which i believe have a solid usecase especially when using LuaJIT

I don't think LuaJIT would be any different from Lua here. If you do, I'm really curious to know why (although you don't need to bother explaining if you don't want to).