User:Callahanp/Flightgear and Simgear Code/From Command Line to Holding Short: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
Line 1: Line 1:
Recently I began the effort to fully understand the skills needed to contribute to the Flightgear project's codebase.  I know c++ from a course in the early 90's.  I'm looking at Kdevelop and QTquick as development tools.
=== Flightgear Codebase ===
My area of interest is in Flightgear's code includes:
* telnet
* phi
* reset & re-initialize
* any method to set or get a property
* the property tree itself
* configuration files
* command line parameters
I'm beginning to look through various parts of the Flightgear code-base to understand how the parts fit together and how supporting libraries are used in the project.  I'd like to learn how aircraft data and graphics are integrated into the working program, and how, why and where Nasal scripting is used.  To this end, I have
* Built a full debug version of the next branch
* Installed
** [https://gdbgui.com/ gdbgui]
** [https://atom.io/ atom] for basic code exploration.
Later I'll try QtCreator


I start by stepping through bootstrap and other modules until flightgear is up and running.
I start by stepping through bootstrap and other modules until flightgear is up and running.
I'm making some notes.  There are three sections:
I'm making some notes.  There are three tables below:


* '''Path''' will trace the path through modules that provide significant functionality to the Simulator until the aircraft is shown holding short or parked somewhere. only the module's source path and a brief explanation or list of why it's on the "path".
* '''Path''' will trace the path through modules that provide significant functionality to the Simulator until the aircraft is shown holding short or parked somewhere. only the module's source path and a brief explanation or list of why it's on the "path".
Line 45: Line 22:
  * connections to multiplayer servers are made
  * connections to multiplayer servers are made
  * a scene is established as a "view" with scenery, Airport data and the Aircraft
  * a scene is established as a "view" with scenery, Airport data and the Aircraft
  * an event loop is started to adjust the view based on changes in controls, weather, aircraft position and attitude
  * an event loop is started to finish the initialization, display a splash screen.  The event loop then shows the first frame and then adjust the view as time goes on, based on changes in controls, weather, aircraft position, speed, attitude and time.


{| class="wikitable"
{| class="wikitable"
936

edits

Navigation menu