...
- Not MVP, but additional contributions sought for
- Provide SDK Tool plugins to facility developers
The Java Device Service SDK today is operated by command line execution. That is, in order to create a new device service, the user must edit configuration settings in a file, then go to the command line and execute an SDK operation, and then finally manually import the new generated project into the tool of choice. In the future, for the Java SDK as well as other language versions of the SDK, it is preferred to have some sort of plugin (example: Eclipse Plugin) or UI driven tool (“wizard”) to assist developers by providing a more user-friendly facility to capture their configuration options, generate the new device service and load it into to development tool of choice.
SDK download (non-GitHub oriented)The Device Service SDK today is available through GitHub. Developers not working on the actual open source products may not be familiar with GitHub and/or may prefer not to have to use Git tools to pull down and work with the SDK. As an alternative, we could make the SDK (and any necessary elements like libraries) available through a Web site for download.
- Provide SDK Tool plugins to facility developers
- Provide new and/or updated Device Services
- Real BACnet or BLE
- Additional DS (i.e. Zigbee, OPC-UA, CANBus, …)
- Reduce/optimize Java DS (remove Spring Framework, etc.)
- Updates to SDK get propagated back out to existing DS via common shared libraries
- Provide new and/or updated Device Services
...