936
edits
User:Callahanp: Difference between revisions
Jump to navigation
Jump to search
m
no edit summary
mNo edit summary |
|||
| Line 48: | Line 48: | ||
=== IDEs === | === IDEs === | ||
Working on Configurations for Visual Studio, Visual Studio Code, Atom, Eclipse and QTCreator IDEs | Working on Configurations for Visual Studio, Visual Studio Code, Atom, Eclipse and QTCreator IDEs and other tools for working with FlightGear Data. | ||
The day to day work of a FlightGear Developer will include the use of a variety of software to work on various kinds of FlightGear material. | |||
The material includes Source Code written in C and C++, Scripts written in Nasal, Build procedures using CMake and in scripting languages of 3 operating Systems, Data Files representing Airports, Runways, Taxiways, Airport Markings, Navigation Beacons, Instrument Landing System Transmitters, Taxiway and Runway Lighting, Buildings, Roadways, | |||
The workflow for all of these has a few basic steps. | |||
* Get copies of the original source material | |||
* Establish a fork repository for your changes to the materials | |||
* Make a local copy of the materials | |||
* Change the materials | |||
* Check the Validity of Changes | |||
* Deliver changed materials to your fork | |||
* Request that the changes be accepted and merged with the original source materials. | |||
The workflows differ based on the true owners of the originating material and the materials format. | |||
These are the basic tasks that a developer will need to complete | |||
* Setting up forks of FlightGear Git Archives | |||
* Identifying non-git Open Source Resources for use with Flightgear and establishing forks for them | |||
* Downloading appropriate tools for working on the kind of files that make up the FlightGear application and it's data | |||
* Configuring these tools and FlightGear itself to operate in one or more modes | |||
* Learning the steps to use inside and outside the tools | |||