20,741
edits
m (→Summary) |
|||
Line 47: | Line 47: | ||
Some of the steps involved are detailed below: | Some of the steps involved are detailed below: | ||
* integrate with navaid/radio code[https://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg38787.html] | |||
* rebase against git HEAD (next) {{Not done}} | * rebase against git HEAD (next) {{Not done}} | ||
* modify build system to make the feature entirely optional via build-time option that defaults to disabled {{Not done}} | * rebase into a set of smaller self-contained patches [https://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg38837.html] {{Not done}} | ||
* modify build system to make the feature entirely optional via build-time option that defaults to disabled [https://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg38797.html] [https://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg38825.html] {{Not done}} | |||
* Address issues pointed out by TorstenD on the devel list {{Not done}} | * Address issues pointed out by TorstenD on the devel list {{Not done}} | ||
* provide a startup option to enable/disable the system [https://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg38826.html] [https://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg33722.html] {{Done}} | |||
* implement SGPropertyChangeListener to change the SGSubsystem and make the feature runtime-configurable [[Howto:Create new subsystems]] {{Not done}} | * implement SGPropertyChangeListener to change the SGSubsystem and make the feature runtime-configurable [[Howto:Create new subsystems]] {{Not done}} | ||
* investigate | * add a setting to the realism dialog[https://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg38825.html] {{Not done}} | ||
* explore allowing aircraft developers to specify and customize a "radio equipment" profile (e.g. 747 vs. c172p antenna/power etc) [https://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg38827.html] {{Not done}} | |||
* support different propagation models by coming up with an interface: | |||
** https://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg33692.html | |||
** https://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg38798.html | |||
** https://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg38907.html | |||
** https://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg40534.html | |||
** https://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg40537.html | |||
* turn the whole thing into a dedicated SGSubsystem[https://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg33736.html] | |||
* explore what is involved in allowing fgcom-standalone to use the same system [https://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg33735.html] | |||
* investigate potential threading/HLA benefits {{Not done}} | |||
* investigate exposing a [[Nasal/CppBind]] interface for people working on features that benefit from having a radio propagation model [[Canvas Radar]] {{Not done}} | * investigate exposing a [[Nasal/CppBind]] interface for people working on features that benefit from having a radio propagation model [[Canvas Radar]] {{Not done}} | ||
* add unit tests to the cmake build system {{Not done}} | |||
==Using Flightgear as a general purpose, 3D, radio signal propagation and terrain analysis tool== | ==Using Flightgear as a general purpose, 3D, radio signal propagation and terrain analysis tool== |