20,741
edits
Addon: Difference between revisions
Jump to navigation
Jump to search
no edit summary
(Created page with "{{Stub}} Torsten ended up using a fairly clever method to come up with this idea for implementing addon support via PropertyList-XML overlays loaded via the --config argument...") |
No edit summary |
||
| Line 1: | Line 1: | ||
{{Stub}} | {{Stub}} | ||
ATC chatter was removed in 2015, see fgdata commit: [https://sourceforge.net/p/flightgear/fgdata/ci/81607f734e13add9be02816ddaec305d05bc4e47/ 81607f734e13add9be02816ddaec305d05bc4e47] | |||
and the devel list messages referenced in the commit log. | |||
the other relevant commit is this: b60736ba7add2a7cd39af3d8a974d5be3ea46e8b | |||
It would not be very difficult to restore this functionality, or even generalie/improve it significantly (which was the scope of the original discussion on the devel list)<ref>{{cite web | |||
|url = https://forum.flightgear.org/viewtopic.php?p=288388#p288388 | |||
|title = <nowiki> Re: Whatever happened to radom radio </nowiki> | |||
|author = <nowiki> Hooray </nowiki> | |||
|date = Jun 11th, 2016 | |||
|added = Jun 11th, 2016 | |||
|script_version = 0.40 | |||
}}</ref> | |||
The restored functionality could be distributed as a tarball that is extracted into $FG_ROOT - alternatively, into $FG_HOME, because Nasal files there are treated as overlays, which basically means that you can install user-specific extensions there without having to tamper with $FG_ROOT, it would only take very minor changes to turn the chatter feature into a corresponding "addon" - not unlike fgcamera ...<ref>{{cite web | |||
|url = https://forum.flightgear.org/viewtopic.php?p=288392#p288392 | |||
|title = <nowiki> Re: Whatever happened to radom radio </nowiki> | |||
|author = <nowiki> Hooray </nowiki> | |||
|date = Jun 11th, 2016 | |||
|added = Jun 11th, 2016 | |||
|script_version = 0.40 | |||
}}</ref> | |||
Torsten ended up using a fairly clever method to come up with this idea for implementing addon support via PropertyList-XML overlays loaded via the --config argument - however, that also brings with it all the power for conflicting with stuff you are loading using the same mechanism, and/or any defaults you have customied. So just be aware of how this works - and again, kudos to Torsten for coming up with such a fancy approach to make this work, despite people arguing for the better part of a decade that FlightGear would not have "proper addon/modding" support" ... ;-) | Torsten ended up using a fairly clever method to come up with this idea for implementing addon support via PropertyList-XML overlays loaded via the --config argument - however, that also brings with it all the power for conflicting with stuff you are loading using the same mechanism, and/or any defaults you have customied. So just be aware of how this works - and again, kudos to Torsten for coming up with such a fancy approach to make this work, despite people arguing for the better part of a decade that FlightGear would not have "proper addon/modding" support" ... ;-) | ||