Separate neural slot for glasses/keyboard
Opened this issue · 1 comments
Why ?
Glasses can generally be useful for direct development visual feedback, and the most complex programs could make use of it: for example a fly program + keyboard integration fills up the totality of the slots, without the inboard keyboard, it is difficult to navigate, and without glasses, we can't really see the log/state of my programs while doing tests.
This being said user I/O related modules could be just separated from the actual modules and avoid filling up precious module slots in the neural interface, letting the user add functionalities without forcing to make a choice between development quality of life and program functionalities
it would allow the players to make their own iron man style system if you want