Howto:Start core development: Difference between revisions

Jump to navigation Jump to search
Switch to the {{forum url}} and {{forum link}} templates for all forum links.
(Switch to the {{forum url}} and {{forum link}} templates for all forum links.)
Line 1: Line 1:
{{out of date}}
{{out of date}}


''01/2012: I have taken my [http://flightgear.org/forums/viewtopic.php?f=18&t=14870#p146436 forum response] and copied/pasted it here. Everybody is invited to contribute. While we do have a [[Volunteer]] page, we don't currently have a page dedicated to people wanting to contribute to the C++ source code, so this is an attempt to get something like this started.''
''01/2012: I have taken my {{forum link|p=146436|text=forum response}} and copied/pasted it here. Everybody is invited to contribute. While we do have a [[Volunteer]] page, we don't currently have a page dedicated to people wanting to contribute to the C++ source code, so this is an attempt to get something like this started.''


= How the Project works (Suggested reading!) =
= How the Project works (Suggested reading!) =
Line 7: Line 7:
* [[http://home.flightgear.org/flightgear-policy-document/ | Flightgear Policy Document briefly covering what will be expected of a contributor]]
* [[http://home.flightgear.org/flightgear-policy-document/ | Flightgear Policy Document briefly covering what will be expected of a contributor]]
* [[http://home.flightgear.org/info/ | Other Information to be Aware Of]]
* [[http://home.flightgear.org/info/ | Other Information to be Aware Of]]
* [[https://forum.flightgear.org/viewtopic.php?f=42&t=15267#p149971 | Forum article on Flightgear Development]]
* {{forum link|p=149971|title=Flightgear Development}}
* [[How the FlightGear project works]]
* [[How the FlightGear project works]]


Please see this short essay here: http://flightgear.org/forums/viewtopic.php?f=42&t=15267#p149971
Please see this short essay here: {{forum url|p=149971}}


Also see [[Implementing new features for FlightGear]]
Also see [[Implementing new features for FlightGear]]
Line 180: Line 180:
* expect [[FGPanel|FGPanel standalone panel rendering]] functionality to be merged back into the main fgfs code base, provided through [[FGViewer]]
* expect [[FGPanel|FGPanel standalone panel rendering]] functionality to be merged back into the main fgfs code base, provided through [[FGViewer]]
* expect more work towards better system-wide reinit/reset support: http://wiki.flightgear.org/Reset_%26_re-init
* expect more work towards better system-wide reinit/reset support: http://wiki.flightgear.org/Reset_%26_re-init
* expect more and more launcher features to be integrated and provided as part of FlightGear [http://flightgear.org/forums/viewtopic.php?f=35&t=21004&p=191451&hilit=#p191451]
* expect more and more launcher features to be integrated and provided as part of FlightGear {{forum link|p=191451}}
* expect FDMs to become re-initializable at runtime, expect support for multiple FDMs per session
* expect FDMs to become re-initializable at runtime, expect support for multiple FDMs per session
* expect more subsystem to become re-initializable at runtime, so that they can be dynamically enabled/disabled to facilitate the fgviewer and headless efforts: http://wiki.flightgear.org/FlightGear_Run_Levels
* expect more subsystem to become re-initializable at runtime, so that they can be dynamically enabled/disabled to facilitate the fgviewer and headless efforts: http://wiki.flightgear.org/FlightGear_Run_Levels
Line 203: Line 203:
Also, there's another outdated category titled "Code Cleanup": http://wiki.flightgear.org/Category:Code_Cleanup
Also, there's another outdated category titled "Code Cleanup": http://wiki.flightgear.org/Category:Code_Cleanup


Another option would be taking a look at the "Google Summer of Code" category which also lists project ideas collected over the years:  [[GSoC: Candidate Projects]]. We also have a separate sub forum for GSoC here: http://flightgear.org/forums/viewforum.php?f=38
Another option would be taking a look at the "Google Summer of Code" category which also lists project ideas collected over the years:  [[GSoC: Candidate Projects]]. We also have a separate sub forum for GSoC here: {{forum url|f=38}}


In other words: '''pick your poison :)'''
In other words: '''pick your poison :)'''
Line 226: Line 226:
There's a fully searchable archive available here: http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/
There's a fully searchable archive available here: http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/


In addition, the FlightGear forums are increasingly used for interesting development related discussions, please note though that these are usually not specific to FG core development, but instead general development (aircraft, scenery, shaders, scripting): http://flightgear.org/forums/
In addition, the FlightGear forums are increasingly used for interesting development related discussions, please note though that these are usually not specific to FG core development, but instead general development (aircraft, scenery, shaders, scripting): {{forum url}}


If there's something particular that you are interested in, it's always a good idea to search these resources (wiki, forum, mailing list) to find related discussions.
If there's something particular that you are interested in, it's always a good idea to search these resources (wiki, forum, mailing list) to find related discussions.
Line 389: Line 389:
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, 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= ]
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) {{forum link|t=13798}} {{forum link|p=184284}} {{forum link|t=13798}} {{forum link|t=6184}} {{forum link|p=31252}}, 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.
[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