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

Template:Nasal Efforts

From FlightGear wiki
Jump to: navigation, search

Recent Efforts

Tutorials & Missions

  • set up a gitorious repo with shared access for all contributors [1] This is a link to the FlightGear forum. 30}% completed
  • helicopter missions 70}% completed (Marius_A [2] This is a link to the FlightGear forum.)
  • Walk View support 80}% completed (Marius_A [3] This is a link to the FlightGear forum.)
  • AI scenarios support 10}% completed (Marius_A [4] This is a link to the FlightGear forum.)
  • NPC support 70}% completed (DFaber [5] This is a link to the FlightGear forum.)
  • self-steering AI vehicles 50}% completed (DFaber [6] This is a link to the FlightGear forum.)
  • extend the framework to support reloading/restarting tutorials at runtime Priority 50}% completed (Marius_A [7] This is a link to the FlightGear forum.)
  • support dynamic mission objectives instead of just static positions Not done Not done [8] This is a link to the FlightGear forum. [9] This is a link to the FlightGear forum.
  • investigate supporting Nasal blocks for having multiple instances of an AI/model i.e. for vehicle/NPC control [10] This is a link to the FlightGear forum. Not done Not done
  • investigate supporting optional Canvas areas for showing mission objectives via MapStructure (Hooray & ludomotico[11] This is a link to the FlightGear forum.) 30}% completed [12] This is a link to the FlightGear forum.
  • procedurally-created Canvas GUI dialogs, e.g. for interaction with NPCs and mission briefings Not done Not done
  • allowing startup time and environmental settings (weather/METAR string) to be stored as part of the tutorial (e.g. for CAT3 approaches at night time) Not done Not done


Canvas MapStructure

Type Work item Progress
Layer FIX 80}% completed
LOD support LOD handling (i.e. range awareness) needs to be finalized and applied to all existing symbol files 60}% completed
New Layer Navaids (meta layer for VOR, DME, NDB) Done Done
Traffic Layer TFC 90}% completed
New Layer DATA (needs label decluttering [13] This is a link to the FlightGear forum.) Not done Not done
New Layer HISTORY Done Done
New Layer cached GRID (lat/lon) [14] This is a link to the FlightGear forum. 20}% completed
New Layer tiled maps/SAT (online [15] This is a link to the FlightGear forum., [16] This is a link to the FlightGear forum.) 10}% completed
Controller zoom Done Done
New Controller interactive/editing [17] This is a link to the FlightGear forum. 10}% completed
New Controller magnetic (see navdisplay.mfd & unify!) Not done Not done
New Controller center on acft (see navdisplay.mfd & unify!) Not done Not done
New Controller acft hdg up (see navdisplay.mfd & unify!) Not done Not done
New Controller panning/translating (see $FG_ROOT/canvas/map/generic-canvas-dialog.xml) Not done Not done


Canvas NavDisplay

  • allow layers to be configured per aircraft ticket 1388
  • use switches hash to procedurally create a GUI dialog with buttons for each toggle_action (TFC,CTR,WXR etc) Not done Not done
  • make sure that the frameworks with properly with time-warp, sim-rate speed-up and replay Not done Not done
  • remove (old) disabled layers Done Done
  • use MapStructure options hash to encode things like nav/comm stuff (anything referencing /instrumentation/) Not done Not done
  • make the timer update interval configurable via constructor Not done Not done
  • consider adding hooks to generalize those huge conditionals in update() some more Not done Not done
  • use foreach() to hide()/show() or setVisible() groups of symbols Not done Not done
  • make this more aircraft agnostic by getting rid of 747/Boeing specific assumptions Not done Not done
  • unify switch/case|default handling (again, huge conditionals in there) Not done Not done
  • on_update() helper should probably support global listeners and timers, too - i.e. via a hash spec ? Not done Not done
  • the whole symbol lookup needs to cleaned up (getElementById etc) Not done Not done
  • introduce a common "compute" field in the update/predicate hash and make its results available to is_true/false etc Not done Not done
  • use io.include to include boeing specific stuffDone Done (see navdisplay.styles for now)
  • NDSourceDriver should be generalized and combined with MapStructure's aircraftpos.controller Not done Not done
  • the radio/autopilot listeners need to be set up in the lcontroller file, they're just empty stubs for now Not done Not done
  • there are 3 foreach loops in newMFD() setting up symbols currently-we only need ONE: loop 2+3 should be removed and use the loop #1 method Not done Not done
  • clean up the ctor and generalize the newMFD() method Not done Not done
  • move stuff out of the update() method into the aircraft-specific configuration hash Not done Not done
  • generalize/extend on_update() method to support other (global) properties and/or listeners/timers to run predicates Not done Not done
  • identify opportunities for improving the framework Not done Not done
  • support multiple routes (WPT/RTE), as per the Nasal Flightplan API (Hooray) Not done Not done
  • move the config hash out of the navdisplay.mfd file and use io.include instead Not done Not done
  • document SVG symbols currently assumed to be available in the ctor Not done Not done
  • consider using some of the SGCondition/StateMachine stuff in SG Not done Not done