Hi a new release. It's more less a bug fix release as the BRouter Web API changed. Additionally a few other quirks are fixed, too.
But there are at least two new features. Henri did a great job enhancing the workspace search. Now, you can weed out your geocaches or tracks in the workspace by searching for properties such as length ascent or tags. See https://bitbucket.org/maproom/qmapshack/wiki/AdvDataHandling#markdown-header-searching-data-in-the-workspace for a detailed description. And Karl added a calculator for cyclist to derive their energy consumption on the base of a recorded track. Just go to the track edit dialog and you will see the little button in the left bottom right where the track summary is shown. It expands to a quite impressive dialog with all parameters to play with. Now to a less pleasant topic: Some of might have heard that Bitbucket drops Mercurial support. Well I am not particular a huge fan of Mercurial but compared to GIT it's way more easy to use. Plus it comes with a nice GUI tool TortoisHg. This makes it easy even for no full time software developers to use it and to contribute. That's why I favor it over GIT for a project like QMapShack. I can't blame Bitbucket to drop it. But I am more than pissed by the way they do it. "We drop it in 10 month. Find out how to migrate everything on your own. Do not bother us." The easiest way seems to be to import the Bitbucket/Mercurial repository into GitHub as GIT repository. And import it back to Bitbucket as a new project..... but wait! Once it is on GutHub why not using GitHub? They seem to be a bit more professional if it comes to migrating repositories. I tested it and it works out...quite well. 1. Migrating the repository is done very well preserving all important information. 2. Migrating the wiki is possible. The only thing that breaks is the TOC of each page. We need to find a solution for that. 3. Migrating the issue tracker is kind of shitty. There are scripts but they have a problem to preserve the user information for obvious reasons as most of the users are not registered by the very same nick name at GitHub. So it ends up with everything attached to anonymous or my nick. Probably I will copy manually some of the issues that I really see fit to be handled in the future. The rest will be dropped. After all most of them are ignored since ages. Not depended on GitHub but GIT the workflow will change quite a bit. It will be more professional and by that a bit harder for those not used to it. So far the policy to contribute to the project was quite sloppy. Now we have to follow something called GIT Flow. I won't exercise it to the detail but it will be more or less like that. Roughly said no one, including me, commits directly to the master or development branch. We are creating feature branches from the development branche, start a merge request and that will go to development branch. Each code contribution will need a ticket in the future that is referenced by the merge request. Only exception are documentation (wiki). And translations. Translations will be a merge request, too. But no ticket is needed. This is just to prepare you about what's coming up. Once the merge is done I hope I have the time to write a tutorial you can work with. Until this is done no new code contribution is accepted. I have to keep the repositories stable. In the meanwhile enjoy the release! Oliver V 1.13.2 [Issue #446] Advanced Filtering System [Issue #491] Skip saving of geo search [Issue #493] "Clone Waypoint and Move Clone" does not Respect Chosen Units [Issue #488] Printing Preview [Issue #494] BRouter segments download error [Issue #499] Screen overflow German localisation on a Notebook with 1.600 x 900 pixel [Issue #500] Tab order in Filter Cycle dialog is confused [Issue #498 ] BRouter setup issue (Windows) Add: Computation of "Energy Use Cycling" (consumption) for cycling tours _______________________________________________ Qlandkartegt-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qlandkartegt-users
