Re: [Viking-devel] Bug squashing for v1.0
Guilhem Bonnefille writes: > Others reported that sharing cache with other GPS applications (like > tangoGPS) could be useful. It seems that there is only minor > differences, and viking can be updated to drop these differences. > > So, I propose to split and rename the root directory. Currently, this > root directory is called something like tsz > New name t/. > > As you notice, I suggest to remove the information. I think > this information is not useful. But perhaps I am wrong. > What is your opinion about this? Any info against removing? I don't understand what scale means differently from zoom. Using zoom seems to line up with how tile providers think. > Other question: should I add a conversion/import utility to > automatically rename directories from old scheme to new one? I don't think it's worth it compared to other things; clearing the cache when connected is not that traumatic. pgpBGfu5kl3EI.pgp Description: PGP signature -- Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev___ 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] Bug squashing for v1.0
An other change comes to my mind before 1.0: cache hierarchy tree. Some users reported that current scheme is not easy to understand (and so, not easy to interact with cached tiles). Others reported that sharing cache with other GPS applications (like tangoGPS) could be useful. It seems that there is only minor differences, and viking can be updated to drop these differences. So, I propose to split and rename the root directory. Currently, this root directory is called something like tsz New name t/. As you notice, I suggest to remove the information. I think this information is not useful. But perhaps I am wrong. What is your opinion about this? Any info against removing? Other question: should I add a conversion/import utility to automatically rename directories from old scheme to new one? 2010/1/5 Guilhem Bonnefille : > As you probably know, the future release will be 1.0. I hope to > release it before end of the month. -- Guilhem BONNEFILLE -=- JID: gu...@im.apinc.org MSN: guilhem_bonnefi...@hotmail.com -=- mailto:guilhem.bonnefi...@gmail.com -=- http://nathguil.free.fr/ -- Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev ___ 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] Bug squashing for v1.0
Guilhem Bonnefille wrote:
> An other significant bug, IMHO, is the #2766373: GPS on ttyUSB3 is not
> accessable
> https://sourceforge.net/tracker/?func=detail&aid=2766373&group_id=83870&atid=570954
>
> One solution is to change the current PARAM_PORT parameter nature.
> Currently, it is an integer, used as index for a predefined list of
> ports. I suggest to replace it with raw string, storing the effective
> port value ("/dev/ttyUSB3" for example).
>
> Such change will brake compatibility between versions. Perhaps can we
> find a way to stay ascendant compatible.
Do we need that at all?
If I remember right you should be able to request a list of known devices from
gpsd - you could display these then. Configuring gpsd properly to use devices is
nothing viking should need to do.
See http://gpsd.berlios.de/gpsd.html - the command is ?DEVICES for the new
protocol. Actually I'm not sure if theres a proper replacement for that in the
old protocol, also I think it doesn't make much sense to be backward compatible
forever, so probably just drop the device selection when building viking with an
old libgps, instead just use the data as it comes from gpsd without any
filtering by device.
--
Bernd ZeimetzDebian GNU/Linux Developer
http://bzed.dehttp://www.debian.org
GPG Fingerprints: 06C8 C9A2 EAAD E37E 5B2C BE93 067A AD04 C93B FF79
ECA1 E3F2 8E11 2432 D485 DD95 EB36 171A 6FF9 435F
--
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
___
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] Bug squashing for v1.0
2010/1/15 Bernd Zeimetz :
> Guilhem Bonnefille wrote:
>> An other significant bug, IMHO, is the #2766373: GPS on ttyUSB3 is not
>> accessable
>> https://sourceforge.net/tracker/?func=detail&aid=2766373&group_id=83870&atid=570954
>>
>> One solution is to change the current PARAM_PORT parameter nature.
>> Currently, it is an integer, used as index for a predefined list of
>> ports. I suggest to replace it with raw string, storing the effective
>> port value ("/dev/ttyUSB3" for example).
>>
>> Such change will brake compatibility between versions. Perhaps can we
>> find a way to stay ascendant compatible.
>
> Do we need that at all?
> If I remember right you should be able to request a list of known devices from
> gpsd - you could display these then. Configuring gpsd properly to use devices
> is
> nothing viking should need to do.
> See http://gpsd.berlios.de/gpsd.html - the command is ?DEVICES for the new
> protocol. Actually I'm not sure if theres a proper replacement for that in the
> old protocol, also I think it doesn't make much sense to be backward
> compatible
> forever, so probably just drop the device selection when building viking with
> an
> old libgps, instead just use the data as it comes from gpsd without any
> filtering by device.
Humh... I'm tthink there is a misunderstood. The stuff I modified is
not related to gpsd. It is the stuff related to direct upload/dowload
with gps device. This feature uses gpsbabel.
--
Guilhem BONNEFILLE
-=- JID: gu...@im.apinc.org MSN: guilhem_bonnefi...@hotmail.com
-=- mailto:guilhem.bonnefi...@gmail.com
-=- http://nathguil.free.fr/
--
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
___
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] Bug squashing for v1.0
On Wed, 13 Jan 2010 10:19:26 -0500 Greg Troxel wrote: > It doesn't make sense to encode pathnames to special files anyway, > because it isn't portable. On NetBSD, it's /dev/dtyU0 or /dev/ttyU0 > instead. So I agree that having a string and removing the magic list > makes sense. Seconded. I use viking on NetBSD. I had to link /dev/tty03 to /dev/ttyS0 to get the GPS layer to work. The GPS layer properties offers only a select box with Linuxish device names. This fails miserably on anything non-Linux. -- tschüß, Jochen Homepage: http://www.unixag-kl.fh-kl.de/~jkunz/ -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ 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] Bug squashing for v1.0
One solution is to change the current PARAM_PORT parameter nature.
Currently, it is an integer, used as index for a predefined list of
ports. I suggest to replace it with raw string, storing the effective
port value ("/dev/ttyUSB3" for example).
Such change will brake compatibility between versions. Perhaps can we
find a way to stay ascendant compatible.
It doesn't make sense to encode pathnames to special files anyway,
because it isn't portable. On NetBSD, it's /dev/dtyU0 or /dev/ttyU0
instead. So I agree that having a string and removing the magic list
makes sense.
Probably gpsd should be the main documented approach anyway.
pgpMh369CAygW.pgp
Description: PGP signature
--
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev ___
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] Bug squashing for v1.0
An other significant bug, IMHO, is the #2766373: GPS on ttyUSB3 is not
accessable
https://sourceforge.net/tracker/?func=detail&aid=2766373&group_id=83870&atid=570954
One solution is to change the current PARAM_PORT parameter nature.
Currently, it is an integer, used as index for a predefined list of
ports. I suggest to replace it with raw string, storing the effective
port value ("/dev/ttyUSB3" for example).
Such change will brake compatibility between versions. Perhaps can we
find a way to stay ascendant compatible.
Any other idea?
--
Guilhem BONNEFILLE
-=- JID: gu...@im.apinc.org MSN: guilhem_bonnefi...@hotmail.com
-=- mailto:guilhem.bonnefi...@gmail.com
-=- http://nathguil.free.fr/
--
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
___
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] Bug squashing for v1.0
One significant bug is that ^Q writes the data file, when human interface guidelines say that it should simply quit, perhaps promting whether or not to save the file if modified. The notion of ^S - save file associated with current window ^W - close current window, prompting if modified. exit if this is the last one. ^Q - close all windows and exit, prompting if modified is very well established as the right behavior for programs, and I don't see any good reason that viking should diverge. pgpRqB7s1x42Z.pgp Description: PGP signature -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Viking-devel mailing list Viking-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/viking-devel Viking home page: http://viking.sf.net/
[Viking-devel] Bug squashing for v1.0
Hi, As you probably know, the future release will be 1.0. I hope to release it before end of the month. As 1.0 can be a notable step, I suggest a bug squash period. So, if you have any time to offer to Viking, perhaps can you fix a bug, or help to reproduce/fix bugs. You can check the list of open bugs at: http://sourceforge.net/tracker/?limit=10&func=&group_id=83870&atid=570954&assignee=&status=&category=&artgroup=&keyword=&submitter=&artifact_id=&assignee=&status=1&category=&artgroup=&submitter=&keyword=&artifact_id=&submit=Filter&mass_category=&mass_priority=&mass_resolution=&mass_assignee=&mass_artgroup=&mass_status=&mass_cannedresponse= Happy hacking! -- Guilhem BONNEFILLE -=- JID: gu...@im.apinc.org MSN: guilhem_bonnefi...@hotmail.com -=- mailto:guilhem.bonnefi...@gmail.com -=- http://nathguil.free.fr/ -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev ___ Viking-devel mailing list Viking-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/viking-devel Viking home page: http://viking.sf.net/
