This release contains a lot of “under the hood” improvements and some work on making the UI more consistent and easier to use. In particular the following changes have been made
The full change log is available here http://code.google.com/p/osmeditor4android/source/list
We will be updating the documentation to include the new features as soon as possible.
There are a few points that you may want to consider when upgrading from previous versions of Vespucci:
Comment from Stalfur on 25 March 2014 at 09:08
Many thanks for this. For the next release maybe I’ll have finished the Icelandic translation!
Comment from nfgusedautoparts on 25 March 2014 at 15:10
i appreciate the ongoing effort; i have a copy on my nexus 7 and have played with it a bit. the main thing, though, is that i have found it a little difficult to follow along with the evolving UI. for example, right now i’m looking at a node representing a fire hydrant, and if i tap on it, i get “unlock to edit”. i am quite unable to figure out how to “unlock” a node. i think vespucci has a lot of promise but it needs better documentation going forward.
Comment from nfgusedautoparts on 25 March 2014 at 15:11
and i just found the tutorial, so that helps a lot, but it took a bit of clicking around to locate the link to it.
Comment from CoreyFarwell on 25 March 2014 at 21:41
Great work! Ever consider migrating to GitHub with the source code + issues? Google Code is a true PITA
Comment from SimonPoole on 25 March 2014 at 21:45
Not my decision, I’m not the projects maintainer and while some things are slightly painful with google code it is not at a level that it would warrant a fork.
Comment from derstefan on 27 March 2014 at 12:27
I am happy that Vespucci is also available via F-Droid - e.g. for people that don’t use Google on their Android smartphone.
Great work, keep on going!
Comment from SimonPoole on 28 March 2014 at 09:31
Unluckily the version available on F-Droid is not coordinated with what we actually release.
They provided a build of 0.9.4 before we did (which surely caused/causes a lot of pain to its users because it was by far not release ready) , and the folloing builds tend to have been made at a random point in time, as a consequence I can’t really recommend F-Droid for now.