CPDLC: Difference between revisions

138 bytes added ,  16 October 2020
(Proposing CPDLC for the 2020 Hackathon)
 
Line 13: Line 13:
* write the Nasal to exchange the right data with the outside system;
* write the Nasal to exchange the right data with the outside system;
* involving core dev's at least for the design choice, a way to get rid of the middleware eventually, e.g. allow Nasal connections to FG-approved servers (like irc.flightgear.org) or integrate specific accesses in the C++ code base (sort of the same history as FGCom, going from standalone executables to an option in the FG menu)?
* involving core dev's at least for the design choice, a way to get rid of the middleware eventually, e.g. allow Nasal connections to FG-approved servers (like irc.flightgear.org) or integrate specific accesses in the C++ code base (sort of the same history as FGCom, going from standalone executables to an option in the FG menu)?
* can someone create a sketch of a block diagram of the elements that need to communicate and the connections between them? -- p callahan


[[Category:Hackathon 2020 Ideas]]
[[Category:Hackathon 2020 Ideas]]
930

edits