Re: [Viking-devel] Export via GPSbabel
There is many things to do now. For example, allowing such export feature at the File-Export level. I also realized that this is one more export sub-menu entry. From the simple user point of view, a single Export dialog would certainly be better, allowing export to GPX, KML and any other file format known by gpsbabel or viking. My opinion is that GPX is the one true format, and the others are useful but can also be distracting. So I think export to GPX should be able to happen with no adtitional barriers. Perhaps if gpx is preselected so you can just hit return once the file is specified that's ok. Basically I'm saying that logically I see options as export as gpx export to some other format, with a dialog to choose it pgppDDbw30Dlh.pgp Description: PGP signature -- November Webinars for C, C++, Fortran Developers Accelerate application performance with scalable programming models. Explore techniques for threading, error checking, porting, and tuning. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60136231iu=/4140/ostg.clktrk___ Viking-devel mailing list Viking-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/viking-devel Viking home page: http://viking.sf.net/
Re: [Viking-devel] Export via GPSbabel
Guilhem Bonnefille wrote: In order to unlock some users, here is a patch. patch applied to latest git.. *OK* on ubuntu13.10 thx! have a nice day Wolfgang 2013/11/6 Guilhem Bonnefille guilhem.bonnefi...@gmail.com 2013/11/5 Robert Norris rw_nor...@hotmail.com Yes I was incorrectly reading the SHA for the commits in the output from gitg (since it shows parent SHA too) So gnome-autogen.sh was doing something useful after all, copying or linking: gnome-doc-utils.make gtk-doc.make omf.make xmldocs.make It seems the latest gnome-common (3.10) in Debian has fixed the previous dodgy automake version checking. I suggest reverting back to the old autogen.sh script which uses gnome-autogen.sh script. It could be a solution. As other solution, I propose: - use autoreconf (directly related to other autotools) - directly call gtkdocize from our autogen.sh (single line) - concert help from DocBook to Mallard: Mallard is simple and non-linear, modern approach to user documentation. I'm thinking about the last item of my list since long time now. This can be the good occasion. The most notable lost of feature is that I do not know how to generate a single PDF from a collection of mallard files. http://projectmallard.org/ Furthermore, I feel that gnome-autogen.sh is going to be deprecated, like DocBook is. https://wiki.gnome.org/GnomeDocUtilsMigrationHowTo https://wiki.gnome.org/GnomeGoals/NewDocumentationInfrastructure What should we do? -- Guilhem BONNEFILLE -=- JID: gu...@im.apinc.org MSN: guilhem_bonnefi...@hotmail.com -=- mailto:guilhem.bonnefi...@gmail.com -=- http://nathguil.free.fr/ signature.asc Description: PGP signature -- November Webinars for C, C++, Fortran Developers Accelerate application performance with scalable programming models. Explore techniques for threading, error checking, porting, and tuning. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60136231iu=/4140/ostg.clktrk___ Viking-devel mailing list Viking-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/viking-devel Viking home page: http://viking.sf.net/
