From 681de4fb4c352356316bfa8ca15fe8d47e3e5d20 Mon Sep 17 00:00:00 2001 From: gdt Date: Sat, 6 Jun 2015 12:57:58 +0000 Subject: Update to 1.5.2. pkgsrc changes: add bash exorcism for testo upstream changes: Depend on QT, and much rewriting Summary of upstream changes: 1.5.2 Add read support for Google's "gx:track" extension to KML. Ralf Horstmann adds Mynav Map Manager and VDO GP7. White B. Coot adds F90G support. Zingo Andersonadds Energympro sport watches. Support altitude in mainnav. 1.5.1 Add options to discard filter to discard points based on regular expressions. Experimental support for for faster Garmin serial download speeds. 1.5.0 GPSBabel 1.4.x has had a good run. That series has been downloaded over a million times and is widely used by thousands of people a day. But, like many projects entering their teens (I started the code that became GPSBabel in 2001) we've accumulated our share of technical debt and the world around us has changed. GPSBabel 1.5 is about revisiting some of those early, fundamental (and, sometimes, dumb) decisions and rebuilding much of it from the foundation up. We've collected hundreds of changes spanning about a hundred thousand lines of code and we're presenting GPSBabel 1.5. Of course, if you're an existing user, you're looking for new formats and fixes. We happen to have those. Freshly added: Mapbar Garmin G1000 Google Direction API MTK Locus Lowrance USR v4 GlobalSat DG-200 Humminbird v4 We have fixes: GUI now lists help button on main screen and options pages. TODO: list more. By far, our deepest cutting changes are in our infrastructure. We changed the implementation language from C89 to C++03. This lets our developers use modern, object-oriented programming and modern libraries. We moved to the open source Qt toolkit. We've successfully used Qt in the GUI for over five years. This lets us focus on GPSBabel itself and not implementi ng our own OS abstractions from scratch, robust string and time handling, and much more. We replaced time from our old representation that used the number of seconds since 1/1/1970 and had a fractional seconds component bolted onto the side (that was only sometimes used) with a QDateTime which allows us to represent time within millisecond resolution from Jan 2, 4713 BCE to sometimes in the year 11 million. While that sounds crazy (it is!) this lets things like the track filter not mangle data collected by your 10Hz GPS and your placemarks can have dates that, say, buildings were built or cities were founded without worrying about Jan 1, 1970. We replaced all of our XML (GPX, KML, Geo, etc) readers with Qt readers. This reduces the number of data-specific bugs you're likely to encounter. No longer will a waypoint named "]]" (it happens!) crash your data. We're much more robust when reading extended namespaces. We replaced our own XML writers with Qt's XML serializers. This solves a whole class of data-specific issues with specific fields containing data like "<" or "[[