In order to facilitation third-party additions to the core Flight Map, we are
thinking of designing a Layer system, wherein logically related data to be
displayed will belong to a layer. Layers would be able to draw items on the
map, react to events and be enabled, disabled and/or configured through user
preferences.
Typical layers might include:
- Airports
- Airspaces
- Navaids
- Terrain
- Weather
- Sectional charts
- etc.
Prior to any refactoring, we need to write a design doc sketching how this
approach would operate. In particular, it should address issues related to
extensibility and performance.
Original issue reported on code.google.com by aristi...@google.com on 31 Jan 2011 at 7:05
Original issue reported on code.google.com by
aristi...@google.comon 31 Jan 2011 at 7:05