[josm-dev] josm-ng progress

[Ulf Lamping]

Frederik Ramm schrieb:
> Hi,
>   
>> Here is how is it meant to work. Please look at it and try to find weak
>> points where the scheme would broke.
>>     
> This freaks out many users because they think they have just lost
> their edits. From a user perspective, they would much rather have JOSM
> go through all their edits from earliest to latest and upload them; if
> uploading stops, they know exactly where they are (and command history
> would only be cleared up to the point where the upload stopped).
>   
I guess the problem here is not the "history lost" here, but giving the 
user not enough information in such cases. I mean, how would a user 
today *know* that the changes are not lost.

When the user uploads stuff, there's no real need for the undo history 
any longer - so it's not the problem with the cleared history, it's the 
problem with lack of user feedback and a guideline what to do now.

Instead of complicating this upload mechanism even further, it might be 
easier (and better) to extend the user interface in a way, that the user 
knows what has happened and what to do now.

Extending the error dialog when the upload has failed with something 
like "Your changes are not lost, please try to upload again (maybe 
later)" and put something like "<241 changed elements needs uploading>" 
in the statusbar could do the trick much better than a highly 
sophisticated and therefore hard to understand, implement and maintain 
history implementation ...

Regards, ULFL