Re: [Qpegps-devel] Developing Qpegps

[Graham <gr...@4o...>]

Ralf Haselmeier wrote:
> Hi Graham,
>
> I'm sorry for the late reply.
>   
Hi Ralf, and everybody else on the list.
My name is Graham Jones - grahamj on oesf forums.
>> I am looking a new 
>> versions of gpsd and some alterations to do with multiple ma
>> p folders.
>>     
> Please post your ideas and the "why, what and how" on
> the qpegps-devel mailing list to avoid that several peaple are working
> on the same issue.
>   
My main thoughts were to update to latest gpsd, using the lib interface, 
hopefully making the communication to gpsd cleaner. It also offloads the 
work of interpreting the gps info to the expert library so qpegps can 
get on with displaying it. There seems to be a number of extra pieces of 
information gpsd will report (such as position errors) so I am thinking 
about finding ways to display those without cluttering the interface.

> And it would be nice, if you post your interests and skills as well
> (like knowledge about C++, Qt, map projections, map datum, NMEA,
> languages (translations), docu, ....).
>   
As for my skills and interest - I have been programming in C/C++ for a 
number of years now, and also use whatever other languages are 
useful/necessary at appropriate times. I have been using the Zaurus 
since the 5500 series and follow developments quite closely. I have done 
some programming in Qt, mostly for my own interests, but a few things 
which, when I have time to complete them, may see the light of day.
I have to admit I don't have a huge amount of knowledge in map 
projections, datum or NMEA, but I am learning. A little while ago I 
produced a way to get Google maps into qpegps (simple use of Google maps 
and investigation to find the best parameters).
I became interested in using a GPS unit to help me find my way around, 
naturally using the Zaurus, found and liked qpegps and would like to see 
it continue to evolve if possible.

>> If you have any other comments about further development of
>> qpegps I would be interested to hear.
>>     
> "multiple map folders" why ? (can't it be done via the profiles ? Please check 
> the latest CVS code)
>   
Interesting, I haven't seen a qpegps built/released with any of this 
code. Did any of the earlier releases include profiles? (and any of the 
other differences between CVS code and latest builds).

I keep an eye on the project regularly but until recently hadn't started 
to build the code for myself. I was probably, perhaps foolishly, 
assuming the ipk's contained all the latest code, especially since the 
CVS source was last altered over a year ago. Since the most recent files 
distributed on SourceForge are from Jan when 0.9.2.3.3 was posted I 
didn't compare against CVS since that had not been updated for sometime 
before.

I have checked it out and will see what the profiles do for me.

My original thought behind multiple map folders was to be easily able to 
swap in and out different sets of maps without editing a central copy of 
maps.txt. Profiles may be a slightly different thing, though until I 
have built the code and tried it I don't know whether I can achieve the 
same effect.

My observation on coming to this project with an interest in 
contributing is that the code in CVS does need to be unified with the 
"release" code so that there isn't confusion over the features in future.

Anyway, I now need to look at the different versions of the source and 
decide how and where to continue.

Graham