Forum Discussion
The SDK is too object oriented
Admittedly, I don't have a Rift, and I'm trying to use the SDK blind. But I'm not really liking this SDK's structure, or the structure of the samples. It looks like it was designed to be complicated a...
If Oculus does provide a lower level C layer, not only is binding more sensible for other languages, but some dependencies can be removed. No need to have libstdc++ linked in, and no need for built-in threading. Threading can be provided by the application if it so desires threaded device or sensor handling... OR, the higher level C++ SDK with bells-and-whistles can be used. I think a simple C layer using HIDAPI would be a good basis for the larger SDK, but that might just be me. The hardware abstraction needed is tiny. What the SDK provides is closer to the beginnings of an app.
Regardless, this is the low level API I'm cobbling together (on hold until Rift arrives, so I can see that I've got HID stuff right). What I come up with will likely be just enough for my needs, and potentially troublesome with new hardware... so official support for a lean API would be very welcome!
Regardless, this is the low level API I'm cobbling together (on hold until Rift arrives, so I can see that I've got HID stuff right). What I come up with will likely be just enough for my needs, and potentially troublesome with new hardware... so official support for a lean API would be very welcome!