936
edits
User:Callahanp: Difference between revisions
Jump to navigation
Jump to search
m
no edit summary
mNo edit summary |
|||
| Line 1: | Line 1: | ||
== What I'm doing: == | == What I'm doing: == | ||
While I participate very marginally in flightgear-devel, I'm ramping up my C++11 skills, learning more about git, getting to know a few editors, IDEs, Build and Debugging tools. I hope to eventually be able 24-7 to build and effectively debug flightgear on any operating system, and to be able to support anyone else wishing to do so. | While I participate very marginally in flightgear-devel, I'm ramping up my C++11 skills, learning more about git, getting to know a few editors, IDEs, Build and Debugging tools. I hope to eventually be able 24-7 to build and effectively debug flightgear on any operating system, and to be able to support anyone else wishing to do so. | ||
At the same time, I'm trying to form a coherent view of Flightgear's structure as an application. Not as a user, but as a developer. This involves gaining knowledge of the various subsystems that make up flightgear, the underlying technologies each subsystem uses and the flow of control and data between these subsystems. | |||
The techniques are the same as any other developer faced with a new 'job' with unfamiliar tools, a new programming language, and a new social environment. Select some tools from among those used by others on the project. Learn the ins and outs of those tools. Get a look at every menu item, configuration item, dialog or other interface and get a good sense of how that fits with the tasks of a developer. Find a small problem to examine and perhaps solve, get some advice, try different approaches, ask about the approaches used by others. Learn or deepen your knowledge of the prevailing coding language or languages. Study the way people on the project behave. Find out what's important, Find out what's not. Try to understand where the group is headed and how they think they'll get there. | |||
Technically, dig in to the code to learn how it is built, debugged and run. Know about all the configuration items. Find all the big pieces in its hierarchy of objects. Some of them are important to know well. Others it is important to know of their existence. Some you can just be marginally aware of. Any that deal with subsystems, creating visual elements, communication between subsystems or keeping things running correctly from cycle to cycle are important. Fine details can wait till later. | |||
http://wiki.flightgear.org/User:Callahanp/fg-from-scratch Callahanp - Flightgear From Scratch] | |||
[http://wiki.flightgear.org/User:Callahanp/Flightgear_Technical_Manual Callahanp - Flightgear Technical Manual] | [http://wiki.flightgear.org/User:Callahanp/Flightgear_Technical_Manual Callahanp - Flightgear Technical Manual] | ||
[http://wiki.flightgear.org/User:Callahanp/Flightgear_and_Simgear_Code Flightgear and Simgear Code] | [http://wiki.flightgear.org/User:Callahanp/Flightgear_and_Simgear_Code Flightgear and Simgear Code] | ||
[http://wiki.flightgear.org/User:Callahanp/FlightgearWorkingGroups Callahanp - Flightgear Working Groups] | [http://wiki.flightgear.org/User:Callahanp/FlightgearWorkingGroups Callahanp - Flightgear Working Groups] | ||
[[https://github.com/c172p-team/c172p C172P Team on Github ]] | [[https://github.com/c172p-team/c172p C172P Team on Github ]] | ||
=== Development Operations === | === Development Operations === | ||