20,741
edits
Canvas wrappers: Difference between revisions
Jump to navigation
Jump to search
m
no edit summary
m (→MFD: typo) |
mNo edit summary |
||
| Line 14: | Line 14: | ||
== 2D Instruments parser == | == 2D Instruments parser == | ||
The 2D panel module will reimplement the existing 2D panel functionality in Canvas/Nasal space, so that the legacy C++ code can be slowly phased out: | |||
{{cquote|<nowiki>I'm even more convinced now that we should move the 2D panel and HUD rendering | |||
over to this approach, since that would get rid of all the legacy OpenGL code | |||
besides the GUI.</nowiki><ref>{{cite web |url=http://www.mail-archive.com/flightgear-devel@lists.sourceforge.net/msg37868.html|title=<nowiki>Re: [Flightgear-devel] Switching from PUI to osgWidget</nowiki>|author=<nowiki>James Turner</nowiki>|date=<nowiki>Tue, 24 Jul 2012 10:36:26 -0700</nowiki>}}</ref>|<nowiki>James Turner</nowiki>}} | |||
<references/> | |||
Also see [[Howto:Creating_fullscreen_Canvas_applications#Parsing_Instruments_and_Texture_Mapping]] | Also see [[Howto:Creating_fullscreen_Canvas_applications#Parsing_Instruments_and_Texture_Mapping]] | ||
| Line 113: | Line 123: | ||
== MFD == | == MFD == | ||
The MFD module will provide a wrapper on top of the canvas system specifically designed for building MFD-type displays (PFD, ND, EICAS etc). The MFD module will be largely based on the hard coded displays currently available in FlightGear, in particular the NavDisplay: [[Navigation display]]. What about CDUs, shall these be also covered by this module, or separately? | The MFD module will provide a wrapper on top of the canvas system specifically designed for building MFD-type displays (PFD, ND, EICAS etc). The MFD module will be largely based on the hard coded displays currently available in FlightGear, in particular the NavDisplay: [[Navigation display]]. What about CDUs, shall these be also covered by this module, or separately? | ||