20,741
edits
Howto:Start core development: Difference between revisions
Jump to navigation
Jump to search
m
→JPEGFactory
m (→JPEGFactory) |
|||
| Line 292: | Line 292: | ||
== JPEGFactory == | == JPEGFactory == | ||
{{cquote|actually the entire JPEGFactory option could likely be removed, and replaced with using the osgDB Image plugins to create a JPEG or PNG. And then it wouldn't need to be a CMake option at all. If anyone would like to attempt this, please ask and I can suggest where to start, it's a nice small project<ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg40211.html|title=<nowiki>Re: [Flightgear-devel] Enabling JPEG factory causes fgfs/GIT to fail compiling</nowiki>|author=James Turner|date=Tue, 11 Jun 2013 22:40:38 -0700}}</ref>|James Turner}} | |||
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. | |||
* [[Howto:Use a Camera View in an Instrument]] | |||
* [[Canvas_Properties#Serializing_a_canvas_to_a_buffer_or_file]] | |||
<references/> | <references/> | ||