Design OOP API for vertical slice

[epage]

Refactor the skeleton API to be OOP

• Create Examples for minimum API vertical slice #22 API is sufficient for examples
• Basic session properties
• Session sub-properties
• Evaluate adding hierarchy to the properties
• Read/write API

[epage]

For the read/write API, the thing I'm considering

We define a BytesBuffer and FloatBuffer. Reading raw frame and reading of signals will use these and return the values contained in them. Compared to these read functions, we'll have read_into functions that take in the buffers. We then manipulate them as needed for the number of samples requested to use in our calls. This allows buffer reuse for performance.

If possible, these buffer objects would mimic enough of numpy that read/write need for numpy to be a drop in replacement, if needed, without having a hard dependency on numpy.