The concept of configurable easily creatable "software sensors" through config files is not yet really implemented in iOS. Maybe we could try to improve on the android version a bit.
Because the android implementation conflates two concepts (especailly in the AndroidSensors class):
Hardware Sensors:
need a class in code to access the actual values provided by hardware
need a config file (for the sensor settings and database configuration)
Software Sensors:
need a config file (for the sensor settings and database configuration)
Every HW sensor changed/added will very likely need software changes anyway, so we could argue that the config file is redundant and we could just configure HW sensors in the code.
On the other hand, we should carefully construct a SW sensor abstraction in code, such that creating/changing a new SW sensors only means writing a sensor config and does not need code changes.
I propose:
remove config for hardware sensors and add all the information to the code
create properly separated SW sensor abstraction in code, use config files for this.
The concept of configurable easily creatable "software sensors" through config files is not yet really implemented in iOS. Maybe we could try to improve on the android version a bit. Because the android implementation conflates two concepts (especailly in the AndroidSensors class): Hardware Sensors:
Software Sensors:
Every HW sensor changed/added will very likely need software changes anyway, so we could argue that the config file is redundant and we could just configure HW sensors in the code.
On the other hand, we should carefully construct a SW sensor abstraction in code, such that creating/changing a new SW sensors only means writing a sensor config and does not need code changes.
I propose: