Advanced scripting

[matlo]

The_ LUA script should be provided with the following data:

• the complete device list
• the accumulated device events for previously active controls
• the new device events
• the previous controller state
• the current controller state

The LUA script should return the following data:

• the new controller state
• device events to push next refresh period

The straightforward way to do this seems to push everything on the LUA stack. It may be overkill, maybe using the registry is better.

The LUA script should be checked:

• sandbox: whitelist only necessary functions (adjust the script environment)
  • print
  • math.*
  • anything else?
• no bytecode
• limit number of CPU cycles
• limit memory usage

[matlo]

LUA scripting seems overkill and raises security concerns when run from an elevated process.

The network API allows controlling a GIMX instance from another process, e.g. a python process. The client could request all devices, and then the server could notify the device events, the controller status, the output reports (rumble, force feedback, leds, wheel range...), and the update period ticks.

Currently GIMX only allows either network input or device input. It could be possible to have both at the same time.