Closed toggledbits closed 5 years ago
Work is in progress. Slated for v2.0 (major version change)
I ended up doing this in v1.5. I've now changed my opinion on actions, and realize that a built-in scene editor is a necessity for Reactor. This is slated for 2.0.
At the moment, I'm thinking that duplicating Vera's scene editor to create Reactor's own "Action" tab would be a large code increment for a relatively small benefit. Basically, doing it would just reimplement Vera's existing scene actions. So, I'm leaning away from doing it that way, because I think I can fix the two biggest problems with Vera scenes: (a) they don't complete if Vera reboots/Luup reloads, and (b) you can't stop them during execution.
So, my current plan is for Reactor to have its own scene execution, but leave the editing/creation of scenes in the hands of the existing Vera UI. You would create your scene in the existing Vera UI, but rather than specify the ReactorSensor as a trigger for the scene, you will configure the ReactorSensor to run the scene from within Reactor's configuration tabs.
As always, discussion around this idea is welcome. I can go either way, I'm just leaning toward keeping Reactor as lightweight as possible, to maximize its utility on older hardware, and keep its performance up on all platforms.