Canvas MFD framework: Difference between revisions

Jump to navigation Jump to search

Canvas MFD framework (view source)

Revision as of 18:32, 1 June 2014

361 bytes removed ,  1 June 2014
no edit summary
No edit summary
No edit summary
Line 22: Line 22:
{{Note|Please also see [[Howto:Coding a simple Nasal Framework]]}}
{{Note|Please also see [[Howto:Coding a simple Nasal Framework]]}}


'''TheTom:'''I'm also doing some work on my C-130J cockpit and therefore have got nearly the same problems^^ There are currently five screens with a lot of pages which can be freely placed on any of the screens. I'm not yet sure on how to setup this system in detail. If displays/windows/etc. show exactly the same thing they should also use the same canvas. One approach would be to use a canvas for each page and add one ore more placements to it depending on where it should be displayed.
{{cquote
Another approach would be to use a canvas for each screen and either reload each page on switching or after loading once hide the according group.
  |<nowiki>If the coders here at FG spent their time (1000 hrs) making the apps / tools that take all the coding out of making stuff, then the modders those with little coding knowledge would spend the 3000 hrs doing the rest.</nowiki>
A completely different approach (which probably also will require some core changes) is to allow moving groups between different canvasses and also just to a storage location to move pages around as needed.
  |{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=211072#p211072
 
    |title=<nowiki>Re: Does FlightGear has Multiplayer Combat mode?</nowiki>
    |author=<nowiki>Bomber</nowiki>
    |date=<nowiki>Thu May 29</nowiki>
  }}
}}


'''Hooray:''' Basically, my idea was to generalize the ND code some more and come up with helper classes for 1) SGSubsystems, 2) MFD instruments and 3) image generators, 4) displays and display switches/selectors. Introducing a handful of helper classes would allow us to support all important use-cases that are common in modern glass cockpits, including switching between different FMCs or PFDs/NDs. I would really prefer to closely coordinate things here - we really don't want to have people come up with hugely different approaches for different types of MFDs.
'''Hooray:''' Basically, my idea was to generalize the ND code some more and come up with helper classes for 1) SGSubsystems, 2) MFD instruments and 3) image generators, 4) displays and display switches/selectors. Introducing a handful of helper classes would allow us to support all important use-cases that are common in modern glass cockpits, including switching between different FMCs or PFDs/NDs. I would really prefer to closely coordinate things here - we really don't want to have people come up with hugely different approaches for different types of MFDs.
Retrieved from "https://wiki.flightgear.org/Special:MobileDiff/72167"

Navigation menu