- people are obviously unaware of how often a canvas/element/group is updated, but that would be good to know for troubleshoot/profiling purposes - e.g. they're currently updating some stuff at frame rate, despite being "static" - we've made the same mistake a few times. So it would seem like a good idea expose this info via the property tree, maybe by adding some /status properties ?
- people also seem to be unaware of the amount of RAM required to set up a canvas - in the case of the extra500, there are two fairly massive canvases created - the osg::Image/osg::texture sizes should probably be also exposed
- making the preferred internal image format configurable would seem like a good idea in such excessive cases, at least for Canvas::Image - but probably even for the parent Canvas itself: http://lists.openscenegraph.org/piperma ... 65456.html
- for static raster images, it may help to expose a flag that tells OSG to unref an image afterwards: http://lists.openscenegraph.org/piperma ... 65412.html
- having an optional flag that calls ->setPixelBufferObject() on CanvasImage/Canvas may also be useful to speed up certain textures (especially anything that is heavily referenced, such as "cache" textures)
- to prevent unnecessary speculation, we may also want to extend Canvas::Element such that each update() is wrapped in between two SGTimeStamp::now() calls whose delta_t is exposed via a PropertyObject as part of each element tree
thoughts / ideas ?