Here's [ http://www.cincomsmalltalk.com/publicRepository/VB-Sketch-DontModeMeIn.html] the description: An experimental tweak of the Refactoring Browser to support modeless editing. With this installed, it is possible to go to a different method or class within the same browser. while a method is being edited The "postponed" edit appears as an icon at the bottom of the browser. Clicking it will jump back to the edit in progress. NOTE: Close all browser windows before or immediately after loading this package. This package is currently unloadable and is should not be loaded into image that has RB_Tabs loaded (or vice versa). -- Best regards, Dennis Schetinin 2013/9/4 Dennis Schetinin <chaetal@gmail.com>
There were an addon named DontModeMeIn for VisualWorks browser which I believe did the same thing. It was written by Vasilii Bykov and there was an article on it in his blog, but I can't find that blog in the new Cincom's site, and can't find that article in WaybackMachine either⦠The only reference I can find is here [ http://scg.unibe.ch/download/wasdett/wasdett2008-paper03.pdf]. Hopefully, the addon is still in Cincom's Public Repositoryâ¦
--
Best regards,
Dennis Schetinin
2013/9/4 Norbert Hartl <norbert@hartl.name>
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