20,741
edits
Howto:Start core development: Difference between revisions
Jump to navigation
Jump to search
Howto:Start core development (view source)
Revision as of 16:49, 17 September 2013
, 17 September 2013→JPEGFactory
Philosopher (talk | contribs) m (pedantry: internal links et grammar) |
|||
| Line 289: | Line 289: | ||
{{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}} | {{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}} | ||
{{cquote|<nowiki>It's turned off for build reasons, not because it's new or untested. I believe | |||
many people have used it exactly the way you describe. If you encounter | |||
problems, they should be easy to fix and patches are welcome! | |||
(The build reasons could actually be solved by using OSGDB to write out the | |||
files instead of using libjpeg directly - this would mean the feature could be | |||
enabled all the time, i.e removed from CMake, and also we could write out PNGs | |||
instead of JPEGs if desired - if you have any interested in doing this, I can | |||
point you at examples since the screenshot code was converted to do the same | |||
thing recently -it's probably a couple of hours hacking at most) | |||
</nowiki><ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg40749.html|title=<nowiki>Re: [Flightgear-devel] --jpg-httpd command line option</nowiki>|author=<nowiki>James Turner</nowiki>|date=<nowiki>Tue, 17 Sep 2013 04:17:15 -0700</nowiki>}}</ref>|<nowiki>James Turner</nowiki>}} | |||
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). | ||