982
edits
User:Callahanp: Difference between revisions
Jump to navigation
Jump to search
→Flightgear - Study Group
mNo edit summary |
|||
| Line 32: | Line 32: | ||
I'm continuing to think about the idea of organizing and participating in a study group for flightgear coding, I want to consider current work on Flightgear proceeding on | I'm continuing to think about the idea of organizing and participating in a study group for flightgear coding, I want to consider current work on Flightgear proceeding on [http://gitlab.com/flightgear Gitlab] as fodder for study. | ||
The study group idea was prompted by my thinking about the codebase itself and why I found it so difficult to understand. I'm sure others have at least some of the same challenges if they share my goal of becoming a regular flightgear contributor. If so, we are likely to find common ground in meeting those challenges. | |||
These points are challenges in learning how FlightGear works, writing code and documentation, and debugging. | These points are personal challenges in learning how FlightGear works, writing code and documentation, and debugging. | ||
* Object-oriented programming - Don't get me started. I agree with Alan Kay. | * Object-oriented programming - Don't get me started. Based on secondary sources I agree with Alan Kay's thoughts on it.<ref> | ||
[https://wiki.c2.com/?AlanKaysDefinitionOfObjectOriented Alan Kays Definition Of Object Oriented]</ref> Alan appears to live nearby. Maybe I'll get up the nerve to ask him personally. Finally, I am pretty sure I am not "a can of Coke<ref> [http://www.johno.se/book/oops.html OOPs - nasty traps in Object Oriented Programming]</ref>." | |||
* C++, when I learned C++, the STL was new. New as in "Do you need a container? Please feel free to write an implementation as homework". There has been significant progress since then, but I never actually wrote any C++ professionally, so I'm catching up on the changes in C++98, 03, 11, 14, 17, and 20. | * C++, when I learned C++, the STL was new. New as in "Do you need a container? Please feel free to write an implementation as homework". There has been significant progress since then, but I never actually wrote any C++ professionally, so I'm catching up on the changes in C++98, 03, 11, 14, 17, and 20. | ||
* Specific Aircraft simulations are implemented mostly in XML, AC files, and Nasal, not in C++. | * Specific Aircraft simulations are implemented mostly in XML, AC files, and Nasal, not in C++. | ||
| Line 44: | Line 45: | ||
* The property tree is a global data store used for most intercommunication between subsystems, but it has no concept of messaging or data flow management. Everything is done with callbacks on individual properties. It's like watching an ant colony. | * The property tree is a global data store used for most intercommunication between subsystems, but it has no concept of messaging or data flow management. Everything is done with callbacks on individual properties. It's like watching an ant colony. | ||
None of the above should be taken as a suggestion that FlightGear development take any specific direction in the future. That will come from me only after I've become a regular and | None of the above should be taken as a suggestion that FlightGear development take any specific direction in the future. That will come from me only after I've become a regular and significant contributor of C++, Nasal, and FlightGear data. Nor should it be taken as criticism of what has been done so far in the 28-year history of the project. | ||
{{reflist}} | |||
== Getting an Giving Help == | == Getting an Giving Help == | ||