Several partners we have been talking to would like to have OTA update mechanisms going from Workbench->mobile->IoT device (over BLE). The idea here is to enable this by using our regular hyper reload mechanism, but instead of triggering a reload in the Viewer, we call a javascript hook so that the Evothings application can handle the new file in whichever way it pleases.
The evothings.json could have an entry pointing at directories that should have this alternate syncing behavior (no reload trigger but instead call a callback in the viewer).
Several partners we have been talking to would like to have OTA update mechanisms going from Workbench->mobile->IoT device (over BLE). The idea here is to enable this by using our regular hyper reload mechanism, but instead of triggering a reload in the Viewer, we call a javascript hook so that the Evothings application can handle the new file in whichever way it pleases.
The evothings.json could have an entry pointing at directories that should have this alternate syncing behavior (no reload trigger but instead call a callback in the viewer).