I don't have voting rights. I appreciate your efforts on 'LuaRT Studio'. However, to allow you to focus more on improving the 'LuaRT' core library, I suggest letting VS Code handle the IDE aspect. You could provide a VS Code LSP (Language Server Protocol), and the community can implement features like syntax highlighting and intelligent suggestions based on it. This way, you won't need to spend time designing the IDE's style, interaction, multilingual support, and other issues.
In fact, if we expect the following features in VS Code:
- Syntax highlighting: Currently, I configure '.wlua' files to be treated as '.lua' to get this functionality.
- Running and compiling: I currently use the runner plugin to call wluart for quick execution, and use the command line for compilation.
- Method and property suggestions for libraries: I haven't found a way to do this, and it doesn't seem to be implemented in 'LuaRT Studio' either.
- Breakpoint debugging: If writing native Lua code, breakpoint debugging can be achieved in VS Code using 'actboy168.lua-debug'.
.vscode/settings.json
{
"code-runner.executorMapByGlob": {
"*.lua": "cd $dir && wluart $fileName ",
"*.wlua": "cd $dir && wluart $fileName "
},
"files.associations": {
"*.wlua": "lua"
}
}
