Re: [osg-users] create a OSG wiki: (it was OpenSceneGraph Oculus Rift integration )

Hi, As someone who as worked (on and off) with OSG for last 12 years I would like to share my opinion. My principal belief is that splitting code and documentation (wiki) would inevitable lead to problems with keeping them in sync. Just look at the current tutorials which do not longer

[osg-users] iOS: flickering problem when changing orientation and using AutoLayout

Hi, I'm experiencing a problem related to orientation changes on iOS and AutoLayout. Specifically, in InterfaceBuilder I created a UIView where I render OSG stuff, I made this view a subview of the ViewController's main view, then if I add some constraints among those views (in order to resize

Re: [osg-users] create a OSG wiki: (it was OpenSceneGraph Oculus Rift integration )

Hi Björn, My idea is actually closely related with your point 2: the in depth documentation of OSG. As far as I know however, doxygen is generated from the comments in the source code, so everyone who wants to add or say something about any function would have to do it in the source code

Re: [osg-users] create a OSG wiki: (it was OpenSceneGraph Oculus Rift integration )

Here's another option to consider... For osgEarth we use ReadTheDocs. You store your documentation right in the source repo alongside the code. That's nice - it keeps everything in one place and lets you revision the documentation as you would anything else. Docs are in RST format, making them

Re: [osg-users] create a OSG wiki: (it was OpenSceneGraph Oculus Rift integration )

Sounds like a cool system... however can people add, edit or comment on anything in the documentation without learning github (or whatever is rep system is used) checking out the source and pushing changes? I think it is very important that this is possible, or else many people may find it too