<br><br><div class="gmail_quote">On Wed, Apr 21, 2010 at 3:51 PM, Joshua Judson Rosen <span dir="ltr"><<a href="mailto:rozzin@geekspace.com">rozzin@geekspace.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">John Stowers <<a href="mailto:john.stowers.lists@gmail.com">john.stowers.lists@gmail.com</a>> writes:<br>
><br>
> I was interested to see the announcement of foxtrotgps.<br>
><br>
> I am the author of the mapping library osm-gps-map<br>
> ( <a href="http://nzjrs.github.com/osm-gps-map/" target="_blank">http://nzjrs.github.com/osm-gps-map/</a>) which I originally developed<br>
> from the tangoGPS codebase when I forked it a few years ago<br>
> (for many of the same reasons I suspect you did).<br>
</div>[...]<br>
<div class="im">> I suspect you could recreate the whole of tangoGPS UI/app in less than a few<br>
> thousand lines of C, or a few hundred of python. Additionally v0.5.0 is<br>
> available in the lucid repositories.<br>
<br>
</div>John,<br>
<br>
Thanks for letting us know about osm-gps-map.<br>
<br>
At a glance, it looks like osm-gps-map did in fact retain a *huge*<br>
portion of the functionality of tangoGPS--much of which it'd be<br>
appropriate to call `core competency', and much of which does in fact<br>
overlap overlaps with what foxtrotGPS does; and I wouldn't be<br>
surprised if there are even similarities in *ways* that we're doing<br>
things, right now (especially given our common lineage...). Though,<br>
some things *did* certainly change (or get added) in tangoGPS between<br>
when you forked-off and our 0.99.3 base, so I'll have to allocate some<br>
time to give osm-gps-map a fair look.<br>
<br>
There are some changes in the works for foxtrotGPS to open things up<br>
architecturally, generalise some things, and probably integrate some<br>
of the new newer features (like `friend'-tracking) with some of the<br>
older features (like self-tracking); we've also been talking about<br>
pursuing things like different autocentre modes, and smarter<br>
tile-downloading strategies (like downloading all of the tiles along a<br>
path). So, I'm curious about how those plans interact with the idea of<br>
switching to osm-gps-map--how much stuff osm-gps-map would want to<br>
manage itself, and basically to what extent the library is<br>
parameterised.<br>
<br>
Also at issue, of course, is that I'd rather not run the other direction<br>
from what Marcus Bauer is doing in tangoGPS `just for the sake of it',<br>
right now--there's enough higher-priority work right now that doing<br>
a mapper-engine transplant might not likely be an immediate task anyway.<br>
<br>
I'm planning on spending most of my free time this week doing<br>
`reverse engineering' work on our GUI module to turn the autogenerated<br>
C code back into an actual GladeXML file, but I'm going to try<br>
to find some time between now and next week to look at the osm-gps-map<br>
API and internals.<br></blockquote><div><br></div><div>Sure, let me know when you have taken a look. I am happy to answer any questions about osm-gps-map and help you integrate it if you wish.</div><div><br></div><div>John</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<br>
Thanks,<br>
<br>
-rozzin.<br>
<font color="#888888"><br>
--<br>
"Don't be afraid to ask (ëf.((ëx.xx) (ër.f(rr))))."<br>
</font><div><div></div><div class="h5">_______________________________________________<br>
This message is sent to you from <a href="mailto:FOSS-GPS@lists.osgeo.org">FOSS-GPS@lists.osgeo.org</a> mailing list.<br>
Visit <a href="http://lists.osgeo.org/mailman/listinfo/foss-gps" target="_blank">http://lists.osgeo.org/mailman/listinfo/foss-gps</a> to manage your subscription<br>
For more information, check <a href="http://wiki.osgeo.org/wiki/FOSS-GPS" target="_blank">http://wiki.osgeo.org/wiki/FOSS-GPS</a><br>
</div></div></blockquote></div><br>