[OSM-talk] Potlatch :-)

[Brent Easton]

>In this case, the user probably clicked somewhere somehow, changes took
>place, and then he was clueless how to rectify the changes and left with
>a bad feeling.  I'm pretty sure he did not do the change intentionally.
>
>If something strange happens while editing in JOSM, you can simply close
>the application without saving and re-start it.  Thus you may loose your
>edits, but you do not damage data already entered.
>
>Potlatch surely needs a explicit save button.  I do not know whether
>such a button exists.


Yes, I have to agree with this. 

I have grown to love Potlatch and now use it preference to JOSM for things like tracing rivers, but I find it very disconcerting that my edits are applied automatically to the live data and that if something 'goes wrong', I have to take action to fix it.

For a newbie who has just stuffed something, the natural response is to close the browser window and hope it that will make the problems 'go away'!

For a newbie friendly editor, I think it is essential that the standard mode is that edits are NOT applied to the database UNLESS you take action i.e. pressing the Save button.

As a power-user, I would feel much safer also :)

Cheers,
Brent.


____________________________________________________________
Brent Easton                       
Analyst/Programmer                               
University of Western Sydney                                   
Email: b.easton at uws.edu.au