Am 03.09.2013 um 15:07 schrieb Igor Stasenko <siguctua@gmail.com>:

>
> this is most annoying to me, that UI interrupts you in very strange manner
> and asks you to make a decision:
> ��- accept, or discard the method, or cancel the action.
>
> often, you are in the middle of typing new stuff and source code
> can be even not syntactically correct.. so, you have to discard or die :)
>
> what i think the solution could be is that browser should allow you to switch contexts
> at any moment without asking you anything.Instead it should remember your
> unsaved changes in special 'drafts' collection, which later you can get back on,
> when you finish what you wanted to do.
>
> And the only time when you want unaccepted edits to not get lost forever is when you closing
> a browser window.. (but of course, drafts can be stored globally somewhere,
> then it also not a big deal, since you can simply return to your draft in different window).

We have method versions. I don't see a reason why uncommited methods can not go just on the list. They could be marked as unsaved/unommited (in fact they are not compiled so different per se) or even better the method version list should be a timeline where the current version is the present and everything else is a past or a potential future version.

Norbert