Hi fellow wiki editors!

To help newly registered users get more familiar with the wiki (and maybe older users too) there is now a {{Welcome to the wiki}} template. Have a look at it and feel free to add it to new users discussion pages (and perhaps your own).

I have tried to keep the template short, but meaningful. /Johan G

Difference between revisions of "Talk:Canvas PFD Framework"

From FlightGear wiki
Jump to: navigation, search
m (response)
 
Line 7: Line 7:
 
: Using the MVC approach, you can hook up different back-ends to different front-ends, just like the [[FG1000]] is currently doing via Richard's [[Emesary]] framework. But, don't bother looking at any of that, if you've only just begun with Nasal/Canvas coding - it introduces a fair amount of abstractions and sophisticated concepts that will all seem like gibberish to you and not make much sense. For starters, what would make more sense is to to come up with 2D drawing helpers specifically for creating PFDs/HUDs - i.e. a library of common elements and helpers to animate those. See Thorsten's existing shuttle work for example: https://forum.flightgear.org/viewtopic.php?f=71&t=33108
 
: Using the MVC approach, you can hook up different back-ends to different front-ends, just like the [[FG1000]] is currently doing via Richard's [[Emesary]] framework. But, don't bother looking at any of that, if you've only just begun with Nasal/Canvas coding - it introduces a fair amount of abstractions and sophisticated concepts that will all seem like gibberish to you and not make much sense. For starters, what would make more sense is to to come up with 2D drawing helpers specifically for creating PFDs/HUDs - i.e. a library of common elements and helpers to animate those. See Thorsten's existing shuttle work for example: https://forum.flightgear.org/viewtopic.php?f=71&t=33108
  
: This would basically be the first step - using either helpers to procedurally create such elements, or a combination of Nasal helpers and SVG/XML files for creating common elements that can be easily customized. --[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 04:50, 26 January 2018 (EST)
+
: This would basically be the first step - using either helpers to procedurally create such elements (think altitude ladder, speed tapes, compass rose etc), or a combination of Nasal helpers and SVG/XML files for creating common elements that can be easily customized. --[[User:Hooray|Hooray]] ([[User talk:Hooray|talk]]) 04:50, 26 January 2018 (EST)

Latest revision as of 07:28, 26 January 2018

How would this actually work?

I have created 2 Canvas PFDs so far, the Airbus A3XX PFD, and the McDonnell Douglas MD-11 PFD. This has lead me to realize that you can't have a framework for a PFD, as each airplane has a very different working PFD, and use different internal systems (especially autoflight design). How is this actually supposed to work?

Kind Regards, It0uchpods (talk) 20:14, 25 January 2018 (EST)

Using the MVC approach, you can hook up different back-ends to different front-ends, just like the FG1000 is currently doing via Richard's Emesary framework. But, don't bother looking at any of that, if you've only just begun with Nasal/Canvas coding - it introduces a fair amount of abstractions and sophisticated concepts that will all seem like gibberish to you and not make much sense. For starters, what would make more sense is to to come up with 2D drawing helpers specifically for creating PFDs/HUDs - i.e. a library of common elements and helpers to animate those. See Thorsten's existing shuttle work for example: https://forum.flightgear.org/viewtopic.php?f=71&t=33108
This would basically be the first step - using either helpers to procedurally create such elements (think altitude ladder, speed tapes, compass rose etc), or a combination of Nasal helpers and SVG/XML files for creating common elements that can be easily customized. --Hooray (talk) 04:50, 26 January 2018 (EST)