Canvas GUI: Difference between revisions

Jump to navigation Jump to search
Line 29: Line 29:
* also, one user mentioned being interested in working on an integrated GUI launcher in {{Issue|1295}}
* also, one user mentioned being interested in working on an integrated GUI launcher in {{Issue|1295}}
It would make sense to coordinate all these efforts a little, so if you're working on anything related, please get in touch via the Canvas subforum.
It would make sense to coordinate all these efforts a little, so if you're working on anything related, please get in touch via the Canvas subforum.
}}
{{cquote
  |<nowiki>So far, Canvas/MapStructure have helped make 2D maps available for all needs in FlightGear, and a canvas/Nasal-based parser that processes our existing GUI dialogs/HUDs or 2D panels code would have the same benefits (GUI: 10k, HUD:3k, 2D panels:4k). Generic canvas/Nasal framework for each of those would probably also be under 4k in total. But it is so much easier being NOT consistent.</nowiki>
  |{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=209465#p209465
    |title=<nowiki>Re: scaling instruments in xml</nowiki>
    |author=<nowiki>Hooray</nowiki>
    |date=<nowiki>Wed May 14</nowiki>
  }}
}}
}}


Navigation menu