Howto:Start core development: Difference between revisions

Jump to navigation Jump to search
Line 296: Line 296:
We could probably also look at using the [[Canvas]] system with some additional hooks, i.e. for getting a handle to the osg::Image, so that it can be serialized through Nasal and some cppbind glue, that would make it possible to depreciate the JPEGFactory code and use the Canvas system instead (i.e. unifying the 2d rendering backend).  
We could probably also look at using the [[Canvas]] system with some additional hooks, i.e. for getting a handle to the osg::Image, so that it can be serialized through Nasal and some cppbind glue, that would make it possible to depreciate the JPEGFactory code and use the Canvas system instead (i.e. unifying the 2d rendering backend).  


Being able to render camera views to a canvas texture has been previously requested a number of times, and getting a handle to the buffer for serialization purposes would also allow us to reimplement the screenshot feature on top of canvas/Nasal, and even serve live image data through the httpd component.
Being able to render camera views to a canvas texture has been previously requested a number of times, e.g. for implementing "mirrors" or tail cameras (A380) [http://flightgear.org/forums/viewtopic.php?f=6&t=13798] [http://flightgear.org/forums/viewtopic.php?f=37&t=20057&p=184301#p184284] [http://www.flightgear.org/forums/viewtopic.php?f=6&t=13798&hilit= ]
[http://www.flightgear.org/forums/viewtopic.php?f=6&t=6184&hilit= ] [http://www.flightgear.org/forums/viewtopic.php?f=4&t=3353&p=31252&hilit=#p31252 ], and getting a handle to the buffer for serialization purposes would also allow us to reimplement the screenshot feature on top of canvas/Nasal, and even serve live image data through the httpd component.


* [[Howto:Use a Camera View in an Instrument]]
* [[Howto:Use a Camera View in an Instrument]]

Navigation menu