it is working as expected usign the default settings (no fancy shader/effect stuff or Rembrandt/ALS tested, yet), without any technical problems - it's a fairly minimal set of changes that add a getter method to the built-in FlightGear view-manager to calculate the camera specified view settings and use those to render to an FBO/RTT offscreen context, the corresponding image is then used by a custom Canvas::Element sub-class that makes the whole thing available as a conventional Canvas rendering "primitive" (analogous to paths, text and raster images). The only "input" (property) the new element actually needs is the view-number that is to be used for the off-screen camera - other than that, all standard Canvas::Element properties are supposed to work "as is".
Other than that, the only technical thing that came as a surprise is the fact that the camera needs to be explicitly updated by setting the element-specifiic update property to "update" the texture - otherwise, it would stay static. Not sure if that got sorted or not - but it wasn't much of a problem, I think we were using a timer based update loop to update the view.
From an architecture standpoint, this is primarily about understanding FlightGear Canvas system and its rendering primitives - if in doubt, see:
http://wiki.flightgear.org/Canvas_DevelopmentUnder the hood, it's a conventional RTT/FBO cam that is using standard OSG code.
For the FlightGear specific camera stuff, the built-in view manager is used to compute the view matrix:
http://wiki.flightgear.org/View_managerThe summary is, there is working code that can be used "as is" - it's certainly much more compelling than just a proof-of-concept - I'd even say, it's basically "finished" - just not integrated (reviewed/discussed). However, Stuart offered to help with that, once the corresponding code is put up for review, even saying that it would not need to be "perfect"
People able to patch/build SG/FG from source, ideally familiar with git and C++/OSG should get in touch with Icecode GL for the set of patches.
Please let me know if he should be n/a, so that I can share the patches here. My only request then would be that the people working with the code, actually do set up a public git repo with the corresponding patches, because this seems to be a recurring question/request
And obviously, it would be really helpful if you could help us update the wiki article accordingly, to document your journey/progress.
PS: What exactly is it that you are working on, cryfer ?