orsjb
commented
8 years ago - Sending code didn’t work, just at one point during the entire day. I think this was possibly due to changing project whilst in IntelliJ (i.e., open Project A, load plugin, then open Project B, then load plugin again - plugin seems to get the right path to the compiled classes, but didn’t send anything over).
- Sometimes massive hang or freeze when loading plugin. Also occasional spinning wheels of doom at various points. Not a big problem, but quite clunky.
- Plugin GUI elements and text appear TINY! in Windows. Maybe if we just knew where the user can zoom on these then that would be good (or maybe we need to implement our own zoom behaviour over the entire GUI?).
- Sometimes plugin devices list resets. I think that when an element is added to the list this might prompt the list to be rebuilt and the status messages get reset to “status unknown”.
- Devices list should permanently show the device ID. (And allow you to manually set it).
- Requested: option to send code to one specific device.
- Device should ‘latch’ onto a controller and not allow itself to connect to another controller.
- Requested: kind of auto-send behaviour so that when the file is changed it automatically sends. And/or a key command that sends the currently open file (how does the plugin know which is the currently open file? Presumably an action event is created with the file as an argument).
- Add behaviour to the plugin to just ‘flash’ the current compiled code to the device.
- Plugin should auto-reload the default (or last) known_devices file when it opens up.
- The list item height should probably be fixed.
- Request: be able to make more than 1 simulated Pi (that will require quite a bit of reimplementation).
- Also a note: we are currently hashing devices by their device name (= usually hostname). This will be problematic whenever devices do not have unique device names.
hokey
