Talk:Radio propagation: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 4: | Line 4: | ||
* integrate with navaid/radio code[https://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg38787.html] | * integrate with navaid/radio code[https://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg38787.html] {{Done}} | ||
* rebase against git HEAD (next) {{Not done}} | * rebase against git HEAD (next) {{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}} | * rebase into a set of smaller self-contained patches [https://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg38837.html] {{Not done}} | ||
| Line 17: | Line 17: | ||
* add a setting to the realism dialog[https://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg38825.html] {{Not done}} | * 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 for their aircraft (e.g. 747 vs. c172p antenna/power etc) [https://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg38827.html] {{Not done}} | * explore allowing aircraft developers to specify and customize a "radio equipment" profile for their aircraft (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: | * support different propagation models by coming up with an interface: {{Done}} | ||
** https://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg33692.html | ** 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/msg38798.html | ||
| Line 23: | Line 23: | ||
** https://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg40534.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 | ** 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] | * turn the whole thing into a dedicated SGSubsystem[https://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg33736.html] {{Done}} | ||
* 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] | * 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] {{Done}} | ||
* investigate potential threading/HLA benefits {{Not done}} | * 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}} | * add unit tests to the cmake build system {{Not done}} | ||
Revision as of 08:26, 27 February 2014
Roadmap
We are currently looking into updating the code base, to ensure that things still work with FG 3.0+ Some of the steps involved are detailed below:
- integrate with navaid/radio code[1]
Done - rebase against git HEAD (next)
Not done - rebase into a set of smaller self-contained patches [2] Not done
- modify build system to make the feature entirely optional via build-time option that defaults to disabled [3] [4] Not done
- Address issues pointed out by TorstenD on the devel list: Not done
- provide a startup option to enable/disable the system [8] [9] [10] [11] Done
- implement SGPropertyChangeListener to change the SGSubsystem and make the feature runtime-configurable Howto:Create new subsystems Not done
- add a setting to the realism dialog[12] Not done
- explore allowing aircraft developers to specify and customize a "radio equipment" profile for their aircraft (e.g. 747 vs. c172p antenna/power etc) [13] Not done
- support different propagation models by coming up with an interface: Done
- 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[14] Done
- explore what is involved in allowing fgcom-standalone to use the same system [15] Done
- 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
- add unit tests to the cmake build system Not done