20,741
edits
FlightGear Newsletter May 2014: Difference between revisions
Jump to navigation
Jump to search
m
→Porting the Garmin GPSMap 196 to Canvas
m (→Project Rembrandt: http://forum.flightgear.org/viewtopic.php?f=71&t=23047&p=209575#p209575) |
|||
| Line 15: | Line 15: | ||
The Garmin 196 is currently in the process of being ported to [[Canvas]] and [[MapStructure]] by F-JJTH. | The Garmin 196 is currently in the process of being ported to [[Canvas]] and [[MapStructure]] by F-JJTH. | ||
Given the generic nature of Philosopher's [[MapStructure]] framework,it only took us 60 seconds to integrate with MapStructure using just 10 lines of [[Nasal]] code - it's a fully working moving map - scale is obviously off here, but it's a matter of setting another style (which can also be used to change color and most symbols) | Given the generic nature of Philosopher's [[MapStructure]] framework,it only took us 60 seconds to integrate with MapStructure using just 10 lines of [[Nasal]] code - it's a fully working moving map - scale is obviously off here, but it's a matter of setting another style (which can also be used to change color and most symbols) | ||
| Line 24: | Line 23: | ||
This is exactly the reason, why we've been working towards an aircraft and GUI agnostic abstraction layer using MVC design concepts - so that reusing and integrating such stuff is really straightforward, without people having to come up with their own custom maps and layers from scratch. | This is exactly the reason, why we've been working towards an aircraft and GUI agnostic abstraction layer using MVC design concepts - so that reusing and integrating such stuff is really straightforward, without people having to come up with their own custom maps and layers from scratch. | ||
Also see [[Garmin GPSMap 196]]. | |||
To learn more, please follow the thread on the forum: http://forum.flightgear.org/viewtopic.php?f=71&t=23047 | |||
=== Canvas Performance === | === Canvas Performance === | ||