delta/navit.git/.travis.yml, branch maptool_turn_restriction_threading github.com: navit-gps/navit.git Refactoring:Xmlconfig:Moving layout definition in their own .xml file (makes main navit.xml file lighter) (#559) 2018-11-18T21:59:14+00:00 lains lains@caramail.com 2018-11-18T21:59:14+00:00 e70a28963ff9754d3257361fad93aebf59edee08 Layouts contain quite heavy xml code, and there are many layouts available for navit. They are all inserted inside the main navit.xml, which makes it hard to edit because of its size, even if changes or customizations by users are very rarely on the layout code. I have thus moved the layout code away from navit.xml, each layout having its own xml definition file, called navit_layout_*.xml These files are inserted inside the main navit.xml file by using the already existing xi:include mechanism, this also allow for backwards compatibility (old monolithic navit.xml files are still valid and can be used). The other advantage for this is that f the user wants to have his/her own customized navit.xml, he/she can still include the shipped layout files, making their xml lighter. This also allow to enable/disable specific layouts easily by including or not each layout file. It is also easier to perform side-by-side comparison between two layout files. 
Layouts contain quite heavy xml code, and there are many layouts available for navit.
They are all inserted inside the main navit.xml, which makes it hard to edit because of its size, even if changes or customizations by users are very rarely on the layout code.
I have thus moved the layout code away from navit.xml, each layout having its own xml definition file, called navit_layout_*.xml
These files are inserted inside the main navit.xml file by using the already existing xi:include mechanism, this also allow for backwards compatibility (old monolithic navit.xml files are still valid and can be used).
The other advantage for this is that f the user wants to have his/her own customized navit.xml, he/she can still include the shipped layout files, making their xml lighter. This also allow to enable/disable specific layouts easily by including or not each layout file.
It is also easier to perform side-by-side comparison between two layout files.
 fix: working sailfish build on circleci using machine executor (#709) 2018-10-29T22:37:21+00:00 Patrick Höhn hoehnp@users.noreply.github.com 2018-10-29T22:37:21+00:00 df9ec3f5e8703c8894887da3447c3ccbb490c91e * fix: working sailfish build on circleci using machine executor * remove travis integration as no longer needed for sailfish build 
* fix: working sailfish build on circleci using machine executor
* remove travis integration as no longer needed for sailfish build
 add:sailfish:added script to build a package for Sailfish OS (#679) 2018-10-21T18:08:42+00:00 Patrick Höhn hoehnp@users.noreply.github.com 2018-10-21T18:08:42+00:00 f6db3ba495964985a0e7ddddaec6a8e070d70d85 Currently needs to be built via Travis instead of CircleCI ( see https://discuss.circleci.com/t/non-reproducable-build-results/25864 for details ) 
Currently needs to be built via Travis instead of CircleCI ( see https://discuss.circleci.com/t/non-reproducable-build-results/25864 for details )