|
Hello,
I’m ecstatic to hear that the Open Reality SDK’s documentation may be receiving an overhaul. It does need one drastically. I’ve been exposed to Open Reality for approximately 2 weeks now and have a plethora of questions that do not seem to be readily accessible.
Personally I feel two things are paramount:
Beef up the glossary with all terms that are used in both the application and the API itself. One question I have to answer for myself is what a ‘connection’ is. Class declarations, too, should have more than a ‘brief description’ that often sounds like someone looked at the name and scribbled a sentence-form meaning to page.
Once I think the glossary is strengthened, the searching capabilities can be improved. For example, I would like to find an object that will tell me how to access the current time in the timeline. I have used the Class List to infer a helpful class, but without closely examining the APIs within, I can not be certain.
So in reference to your specific list, I think the biggest thing is to get a ‘big picture’ for a programmer. I would love to see how a particular feature in MotionBuilder directly maps in the API class-wise. (e.g. Transport Control -> FBTransportControl class, etc.). Many of us work from an angle of seeing how MotionBuilder does it and seeing how we can control that through code.
Hope this helps.
Kevin
| 
