Updated proposal for Sensor API #46
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is new API proposal that tries to account for the various issues raised so far, notably problems around discoverability. Please bear with the quickly cobbled together document. I'm really trying to get the big picture right here, before diving into the details once the basic outline settles.
You can read it in full here for the time being.
Here's what a UML-ish representation would look like (for those of you to which these things speak):
Alternative solution
Note that another API design option merges
SensorandSensorObservertogether and addstart()andstop()methods to it (thus allowing creating newSensorobjects without immediately polling the sensors).And again, for the more visual among us:
Extensibility
Here's what extending either of these proposals would look like to create, for example, a proximity sensor: