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...
I absolutely agree. The SDK is obviously being built as a larger suite of tools, using typical C++ idioms. So the resulting code is about 2% "hardware abstraction" while being a lot of boilerplate and support for flexible device enumeration, messages, threads, and even their own "stdlib" of containers, math, etc.
I've been going through it separating out pieces into 3 categories:
1. low-level hardware interface
2. high-level interpretation (sensor fusion)
3. cruft that really exists in any application anyway
The goal is to have a low-dependency (no threading, for one!) C library for abstracting the hardware (1), with tools (2) for building a higher level abstraction in whatever OS/language with your application's resources (threading/messages/etc).
I have my doubts about any maintainability of this, however, because the SDK is obviously going to change a lot and the changes will not be easily merged.
I've been going through it separating out pieces into 3 categories:
1. low-level hardware interface
2. high-level interpretation (sensor fusion)
3. cruft that really exists in any application anyway
The goal is to have a low-dependency (no threading, for one!) C library for abstracting the hardware (1), with tools (2) for building a higher level abstraction in whatever OS/language with your application's resources (threading/messages/etc).
I have my doubts about any maintainability of this, however, because the SDK is obviously going to change a lot and the changes will not be easily merged.