20,741
edits
FlightGear Newsletter May 2014: Difference between revisions
Jump to navigation
Jump to search
→A Canvas-based Map dialog
| Line 100: | Line 100: | ||
One major addition that can already be seen in the screen shot below is that styling support is now becoming a key concept of the [[MapStructure]] framework, which means that symbols and appearance can be easily customized by non-programmers just by changing some values for things like font, font size, colors, line width etc. Sooner or later, we're also hoping to support replacing image sets completely, e.g. by using the vector artwork provided by Michat and pommesschranke. | One major addition that can already be seen in the screen shot below is that styling support is now becoming a key concept of the [[MapStructure]] framework, which means that symbols and appearance can be easily customized by non-programmers just by changing some values for things like font, font size, colors, line width etc. Sooner or later, we're also hoping to support replacing image sets completely, e.g. by using the vector artwork provided by Michat and pommesschranke. | ||
Internally, the code rendering the screen shots shown below is 100% identical with the back-end code by Gijs' [[NavDisplay]] for rendering mapping layers, and it's already making use of symbol instancing, i.e. caching, to support faster updates and better frame rates/performance. Also, we can already show multiple '''independent''' instances of such dialogs/maps/instruments at the same time. | Internally, the code rendering the screen shots shown below is 100% identical with the back-end code used by Gijs' [[NavDisplay]] for rendering mapping layers, and it's already making use of symbol instancing, i.e. caching, to support faster updates and better frame rates/performance. Also, we can already show multiple '''independent''' instances of such dialogs/maps/instruments at the same time. | ||
Furthermore, we're also exploring the possibility of supporting interactive layers, these would be layers that respond to GUI events (mouse for now). Initially, this will be primarily needed for supporting zooming/panning functionality, which is already supported by the existing airport selection dialog. But we've also seen some interesting discussions on the forum about extending the new Canvas-based [[Map]] dialog to include navigation tools for flight planning purposes, like for example having an interactive protractor. | Furthermore, we're also exploring the possibility of supporting interactive layers, these would be layers that respond to GUI events (mouse for now). Initially, this will be primarily needed for supporting zooming/panning functionality, which is already supported by the existing airport selection dialog. But we've also seen some interesting discussions on the forum about extending the new Canvas-based [[Map]] dialog to include navigation tools for flight planning purposes, like for example having an interactive protractor. | ||