Ok, so after QOrbiter has hit the general user populace, a huge glaring problem has shown its face. location that it actually exists in.
As it stands now
*Rooms that one not might want set to manual, are set to manual, with new ea's added for the new media targets.
This presents a problem of both clutter in the old ui (EA's are treated as rooms, thus every device shows up as an additional room) Its really bad and I dont know how to fix it.
*When I play media on an android tablet, I get lights dimming and such. This is more likely not the desired action in this _new_ context. So its something else to be considered.
I have made changes to the qorbiter DT to allow for specifying what form factor it is (workstation, tablet, phone, md, god knows what else will be invented. watches you say?)
Now, the 'solution' i have for the moment is that they should all exist in a room called 'Mobile Orbiters' or something.
This would let them operate independent of a location they may or may not be tied to re: the automation options.
Users could still choose other rooms as normal, but this one would be specific to mobile devices.
It doesn't do much for the longer list of 'Rooms' on the old orbiter. they assume a 1 to one mapping and it doesn't seem i can change that.
And finally, I need seriously help writing the mysql queries to
*Make the 'Mobile Orbiters' Room show up when people add a QOrbiter, then add the subsequent new EA in that room
*Look at how we branch to do this as well OrbiterGen. Right now its done in php, which is fine with me for prototyping, but I feel like it would be messy to leave orbitergen spread over two places.