[OSM-dev] Implementing 'undo' in Potlatch

[Chris Fleming]

Richard Fairhurst wrote:
> Tom Hughes wrote:
>   
>> The problem is that Potlatch commits changes to the database in real
>> time so the two get conflated together somwehat.
>>     
> Yes, and I'm not keen to change that to a "click Save to upload"  
> model, because a) it complicates the UI in itself, b) you basically  
> need to implement conflict resolution and I don't think that can be  
> implemented in a manner simple enough for the target userbase. (Nor  
> necessarily simple enough for the target programmer to implement  
> without fouling up the db. :| )
>
> Don't forget that Potlatch already has a limited "abort current  
> changes" function (press ESC, does admittedly need to be more visible)  
> so in most circumstances you don't need to commit misclicks to the db.
>   
I agree that the "no need to save" is a nice feature, and it makes it 
much easier to get started,  but agree that it may make things a little 
scary when getting started. It also means that if the browser 
crashes/connectivity is lost then no changes would be lost.

I suspect that someone who starts out using Potlatch would take it for 
granted and if the switch to JOSM will  find the whole download/upload 
save thing very passe.

Cheers
Chris

-- 
http://www.chrisfleming.org/