20,741
edits
Canvas glass cockpit efforts: Difference between revisions
Jump to navigation
Jump to search
m
→XML Framework
m (http://forum.flightgear.org/viewtopic.php?f=71&p=212029#p212029) |
m (→XML Framework) |
||
| Line 30: | Line 30: | ||
== XML Framework == | == XML Framework == | ||
{{cquote | |||
|<nowiki>Given the recent trend of MFD-related effort without any kind of collaboration among contributors going on here (PFD, ND, Avidyne Entegra R9, EFB), I have started working on a generic MFD framework that is purely XML-based, inspired by discussions we've had over the last couple of weeks, and lessons learnt from the missions subsystem.</nowiki><br/><nowiki> | |||
</nowiki><br/><nowiki> | |||
The whole thing works with building blocks like a screen, buttons, modes, pages, and page elements</nowiki> | |||
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=212029#p212029 | |||
|title=<nowiki>Framework-centric aircraft-agnostic avionics development</nowiki> | |||
|author=<nowiki>Hooray</nowiki> | |||
|date=<nowiki>Sat Jun 07</nowiki> | |||
}} | |||
}} | |||
{{cquote | |||
|<nowiki>It is intended to:</nowiki><br/> | |||
*<nowiki> support multiple independent instances</nowiki><br/> | |||
*<nowiki> be totally aircraft agnostic</nowiki><br/> | |||
*<nowiki> support a pure dialog-driven mode</nowiki><br/> | |||
*<nowiki> support skinning/theming</nowiki> | |||
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=212029#p212029 | |||
|title=<nowiki>Framework-centric aircraft-agnostic avionics development</nowiki> | |||
|author=<nowiki>Hooray</nowiki> | |||
|date=<nowiki>Sat Jun 07</nowiki> | |||
}} | |||
}} | |||
{{cquote | |||
|<nowiki>This is supposed to support modeling complex avionics like a PFD, ND, EFB, CDU etc - and, eventually, also the Avidyne Entegra R9.</nowiki><br/><nowiki> | |||
</nowiki><br/><nowiki> | |||
It's currently just a prototype, but it gets away with very little code and we really only need a few more "skins" for common avionics.</nowiki><br/><nowiki> | |||
I am willing to extend this over time and help maintain it if people can agree to use something like this.</nowiki><br/><nowiki> | |||
</nowiki><br/><nowiki> | |||
It should be straightforward to allow such "MFDs" to be reloaded from disk at run-time, i.e. for more rapid prototyping.</nowiki><br/><nowiki> | |||
</nowiki> | |||
|{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=212029#p212029 | |||
|title=<nowiki>Framework-centric aircraft-agnostic avionics development</nowiki> | |||
|author=<nowiki>Hooray</nowiki> | |||
|date=<nowiki>Sat Jun 07</nowiki> | |||
}} | |||
}} | |||
{{Note|This is work in progress - the idea is to identify required building blocks to easily specify most MFD functionality in a generic fashion, without requiring a ton of custom Nasal code and without being specific to a single type of MFD. The whole concept is based on [[FlightGear_Missions_and_Adventures#XML_Extension_Framework]], i.e. providing a Nasal-space mechanism to expose and re-define building blocks to XML space. | {{Note|This is work in progress - the idea is to identify required building blocks to easily specify most MFD functionality in a generic fashion, without requiring a ton of custom Nasal code and without being specific to a single type of MFD. The whole concept is based on [[FlightGear_Missions_and_Adventures#XML_Extension_Framework]], i.e. providing a Nasal-space mechanism to expose and re-define building blocks to XML space. | ||