Hi, Thanks for all these comments.
2011/9/8 Robert Norris <rw_nor...@hotmail.com>: > > Some observations for further discussion and unfortunately larger (re)work. When coding this feature, I also realized all the limits you spotted about current implementation. But I imagined that it is significant work to implement all this. So, I decided to create a simple solution, perhaps not trivial for user, but simple. Please, found some more details in-text. > A. It is slightly annoying one may specify the 'file type' twice (especially > when it's a choice of over 150 kinds!) > > i.e. One goes into file selection dialog, chooses a filter, then picks a file. > But then need to set the file type to be used in our Import File dialog. > Or vice versa - set a file type but then is not used as the filter when > actually picking a file. > > Obviously files can be called anything and have any file type - which we have > to tell gpsbabel. > > It might be better to order the Import File dialog like this: > 1. File Type > 2. Filename Selection > 3. Track/Route/Waypoint options > > Then on choosing the file type, this can auto set the default used for the > file selection. One matter: two lists are not simmetrical as some file types does not have file extension. IMHO, if we have to change part of this, we have to implement something that preset the file type when a file is selected. > B. Be wary of the track/route/waypoint options not doing what you think they > should do! > > I thought if I deselected the waypoint or track options and opened a gpx or > kml file then I would *not* get that type of information. > This does not seem to be the way GPSBabel works - especially on file > conversions - or the behaviour is dependent on the file format used. > > I think track/route/waypoint options mainly apply to the serial data formats > not the file conversions. > > Some options in order of difficulty: > 1. Add GUI visible statement that they only work on some file formats (but > which ones???) > 2. Remove these track/route/waypoint options > 3. Perform automatic post processing ourselves to remove the kinds of data > the user doesn't want. Yes, it seems that -t/r/w options do not already work the same way for all file type. For example, I use these options to convert magellan files to gpx and gpx to magellan format. I know I need these options to "route" gpsbabel to the right format to produce, as magellan does not mix track, route and waypoint in the same file. I have to check more. But note we know which feature is supported by which file type. The choice we have to decide is the scenario: - do we filter the available options following the selected file type - do we filter the available file types following the selected options I'm not sure what an user will prefer. > C. Importing files this way don't get stored into the recently opened file > list. [It would be difficult to open them as nothing is stored about what > type it is - it is possible an auto guess based on filename extension could > work for some but not all files.]. > > I'm OK with not going into the recently opened list. Yes, it is currently an "import", not a file openning. > D. Slight aside, but whilst in the area - we should probably use the '-p ""' > option to override users gpsbabel .ini defaults. > > See http://www.gpsbabel.org/htmldoc-1.4.2/inifile.html Thanks for this. > ---------------------------------------- >> Date: Wed, 7 Sep 2011 22:05:41 +0200 >> From: guilhem.bonnefi...@gmail.com >> To: viking-devel@lists.sourceforge.net >> Subject: [Viking-devel] Import file via gpsbabel >> >> Hi, >> >> As many of you already know, viking uses gpsbabel for many features. >> Most of them concern format conversions. But, currently, only some >> formats are offered via viking. I not really know why viking does not >> support all formats supported by gpsbabel. And recently, I discovered >> that gpsbabel is able to list all the formats and options it knows. >> >> I made many changes on viking. Before merging them on viking's master >> branch, Any comments are welcome: >> http://repo.or.cz/w/viking/guyou.git/shortlog/refs/heads/import-via-gpsbabel >> -- Guilhem BONNEFILLE -=- JID: gu...@im.apinc.org MSN: guilhem_bonnefi...@hotmail.com -=- mailto:guilhem.bonnefi...@gmail.com -=- http://nathguil.free.fr/ ------------------------------------------------------------------------------ Doing More with Less: The Next Generation Virtual Desktop What are the key obstacles that have prevented many mid-market businesses from deploying virtual desktops? How do next-generation virtual desktops provide companies an easier-to-deploy, easier-to-manage and more affordable virtual desktop model.http://www.accelacomm.com/jaw/sfnl/114/51426474/ _______________________________________________ Viking-devel mailing list Viking-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/viking-devel Viking home page: http://viking.sf.net/
