High-Level Architecture: Difference between revisions

no edit summary
No edit summary
No edit summary
Line 6: Line 6:


{{FGCquote|1= Moving toward a new modular HLA architecture offers a number of possibilities. One of these is that different modules, or subsystems, can effectively become independent binaries. |2= {{cite web  | url    = http://sourceforge.net/p/flightgear/mailman/message/34196458/  | title  = <nowiki>Re: [Flightgear-devel] Policy Document and V4.X Roadmap</nowiki>  | author = <nowiki>Durk Talsma</nowiki>  | date  = Jun 11th, 2015  }}}}
{{FGCquote|1= Moving toward a new modular HLA architecture offers a number of possibilities. One of these is that different modules, or subsystems, can effectively become independent binaries. |2= {{cite web  | url    = http://sourceforge.net/p/flightgear/mailman/message/34196458/  | title  = <nowiki>Re: [Flightgear-devel] Policy Document and V4.X Roadmap</nowiki>  | author = <nowiki>Durk Talsma</nowiki>  | date  = Jun 11th, 2015  }}}}
{{FGCquote
|1= In terms of integration with the property tree, I'm thinking that in the short term all the different components that we split out into separate threads or executables will simply use their own properties trees, and use the RTI to reflect the particular (minimal) data that needs to be passed between components.
|2= {{cite web
  | url    = http://sourceforge.net/p/flightgear/mailman/message/34632142/
  | title  = <nowiki>Re: [Flightgear-devel] HLA developments</nowiki>
  | author = <nowiki>Stuart Buchanan</nowiki>
  | date  = Nov 19th, 2015
  }}
}}


{{FGCquote
{{FGCquote