Howto:Add new fgcommands to FlightGear: Difference between revisions

Jump to navigation Jump to search
m
Line 137: Line 137:
= Adding new commands =
= Adding new commands =
All new commands must have the previously described signature, the functions should then be added to the list of built-in commands, beginning in line [http://gitorious.org/fg/flightgear/blobs/next/src/Main/fg_commands.cxx#line1467 1467]. The list of built-in commands maps the human-readable names used in README.commands to the names of the internal C++ functions implementing them.
All new commands must have the previously described signature, the functions should then be added to the list of built-in commands, beginning in line [http://gitorious.org/fg/flightgear/blobs/next/src/Main/fg_commands.cxx#line1467 1467]. The list of built-in commands maps the human-readable names used in README.commands to the names of the internal C++ functions implementing them.
When you send patches or file merge requests for new fgcommands, please also make sure to send patches for README.commands, too - so that your new commands are documented there.


This was just an introduction intended to get you started, most of the missing information can be learned by referring to the plethora of existing fgcommands and see how they implemented and working.
This was just an introduction intended to get you started, most of the missing information can be learned by referring to the plethora of existing fgcommands and see how they implemented and working.

Navigation menu