Canvas MapStructure: Difference between revisions

Jump to navigation Jump to search

Canvas MapStructure (view source)

Revision as of 18:03, 25 June 2014

477 bytes removed ,  25 June 2014
→‎Porting the map dialog
Line 328: Line 328:


{{FGCquote
{{FGCquote
   |the recent GUI work committed by TheTom means that we can phase out the PUI map-canvas.xml dialog and create the whole dialog procedurally using a native canvas window, because we really only need two types of widgets: buttons and checkboxes, which are both supported now, thanks to the new "Aircraft Center".
   |the recent GUI work committed by TheTom means that we can phase out the PUI map-canvas.xml dialog and create the whole dialog procedurally using a native canvas window, because we really only need two types of widgets: buttons and checkboxes, which are both supported now, thanks to the new "Aircraft Center":
 
[[File:Native Canvas MapWidget Dialog.png|450px|thumb|Native Canvas MapWidget dialog using just Canvas Widgets, the Map has been turned into a Canvas Widget itself, so that it can be easily embedded in other dialogs (obviously the whole thing still needs to be cleaned up, layouting isn't currently used yet).]]
 
   |{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=213083#p213083
   |{{cite web |url=http://forum.flightgear.org/viewtopic.php?p=213083#p213083
     |title=<nowiki>Re: NavDisplay & MapStructure discussion (previously via PM)</nowiki>
     |title=<nowiki>Re: NavDisplay & MapStructure discussion (previously via PM)</nowiki>
Line 344: Line 347:


While map.nas is deprecated, it probably isn't worth it (yet) to port the airport selection dialog yet, but creating a map dialog should be easy now - as long as we ignore panning/translating for the time being, and the flightplan. We should get adequate performance right now, but I will need to check with the 747, 777 to make sure.
While map.nas is deprecated, it probably isn't worth it (yet) to port the airport selection dialog yet, but creating a map dialog should be easy now - as long as we ignore panning/translating for the time being, and the flightplan. We should get adequate performance right now, but I will need to check with the 747, 777 to make sure.
Hooray is currently pushing master to the canvas-team clone (kinda forgot to keep it sync, and all the recent stuff is adding up, really need to set up a cron job to keep it up to date), but we should have a fresh branch based on fgdata:master in a few minutes, I will then also add the existing map-canvas.xml dialog there so that we can check what's missing. I agree, looking at airport.xml only makes sense once map-canvas.xml works as expected. flightplan stuff should actually be there, i.e. Gijs' code is showing routes just fine. panning/translating should be a matter of adding a handful of custom map controllers - that part should be more straightforward than actually porting airport.xml, because that's using a ton of non-generic Nasal code, even without the ugly map.nas stuff


Performance-wise, we really only need to add two optional systime() statementss at the controller level to see if there's anything heavy remaining, which would then be a candidate for SymbolCache.
Performance-wise, we really only need to add two optional systime() statementss at the controller level to see if there's anything heavy remaining, which would then be a candidate for SymbolCache.
Retrieved from "https://wiki.flightgear.org/Special:MobileDiff/73240"

Navigation menu