Steve, For me, communication via this list is just fine. Not fancy, but simple and serving the purpose. As for the contribution support work, what I miss most in OSN is a reliable track saving. On average, 50% of my tracks are lost and never reach OSM, although I upload the track every 20 minutes or so. Can the track be saved locally before uploading it to OSM, saved as it is recorded? This near real-time saving is desired because OSN is still fresh and crashes frequently. While, we will all be trying hard to make it more stable, I'd love not to loose my tracks in meantime.
droidguy 2010/5/30 steve brown <[email protected]> > Hey all > > As you may know, my first week's task was to work on the contribute > interface in OSN. > > As MyTracks is open source now, and has a good deal of code specifically > working around the weirdness of the Android platform, I used a good deal of > their newly opened code. > > See http://www.youtube.com/watch?v=rav9Bz40Uu0 for a video demo. > > It's still work-in-progress, owing to being right in the middle of exam > season (done two, next week one on thursday one friday) but it is getting > there quickly. > > The hard part is done, and there are just a few last integration bits left, > but the code is all in there, its just not connected up yet :-). > > I'm planning on posting more frequent updates - I don't like going AWOL for > 6 days and then dumping all the work at once - what communication method > would people prefer? > Blog? Twitter? Blog with autotweets? OSM Diary? > > Steve > > _______________________________________________ > Osn-dev mailing list > [email protected] > https://lists.kentgeek.org/mailman/listinfo/osn-dev > > -- Stan Berka (h) 503 977-3813 (c) 503 997-0062
_______________________________________________ Osn-dev mailing list [email protected] https://lists.kentgeek.org/mailman/listinfo/osn-dev
