The current way of laying out lua scripts (with individual editing fields for each element/event) is intended to simplify things, but actually makes them more confusing for anyone who knows lua.
It also makes it a lot harder to move scripts to/from the game environment (eg for unit testing or offline-development).
It would be far better if a lua script author could view the contents of a controller as a single Lua file, with each individual handler actually shown as a handler in the source (with appropriate naming conventions to identify the purpose of each handler).
This would allow direct copying/pasting of the script into other environments.
Even better, if would be ideal if this script was stored in a known location on disk (see #6).
samdeane
commented
3 years ago
The current way of laying out lua scripts (with individual editing fields for each element/event) is intended to simplify things, but actually makes them more confusing for anyone who knows lua.
It also makes it a lot harder to move scripts to/from the game environment (eg for unit testing or offline-development).
It would be far better if a lua script author could view the contents of a controller as a single Lua file, with each individual handler actually shown as a handler in the source (with appropriate naming conventions to identify the purpose of each handler).
This would allow direct copying/pasting of the script into other environments.
Even better, if would be ideal if this script was stored in a known location on disk (see #6).