Hi Bill, I have a good machine now... I'm running Ubuntu 9.04, 64 bits. I agree with you that OB is slow for some tasks like adding a package. I also lost code when not saving a method, going to another browser to change another method and going back to the original or things like that... I'll try to reproduce them and fix them.
Hernan. 2009/6/27 Schwab,Wilhelm K <[email protected]> > Hernan, > > I've had some hangups, some of which I think were OB related; either it > took a terribly long time to respond, or it got confused over package names > - not sure which - I finally recovered what I could and started a new > image. A few times, I have successfully broken out of an apparent lockup. > BTW, > that's another argument for keeping notifiers - why add add an extra second > or two for the full debugger to open when a notifier is enough to let the > user know the interrupt was "seen." > > The other place I have lost work is accepts in either the debugger or (less > of a problem) a browser going into the ether. In the case of the browser, I > wonder whether the category or other context was correctly set?? > > Concerns over response times aside, which OS are you using? > > Bill > > > > ------------------------------ > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Hernan > Wilkinson > *Sent:* Saturday, June 27, 2009 2:24 PM > *To:* [email protected] > *Subject:* Re: [Pharo-project] [ANN] Fix to issue 825 > > > >> > With this fix, all changes made to classes like adding instance >> > variables, class variables, changing method categories, changing >> > class package, etc. are saved to the changes file. I spend some time >> > trying to find the best way to do it, like Stef said some time ago, >> > the code is not easy to understand, so I decided to do it the >> > simplest way. So each method that changes something in the class, it >> > also logs the change. The good thing is that no matter where the >> > change is made, it is saved. >> >> Did you pay attention that certain operation are silent (do not add to >> the change) > > > right now is saving all the changes to the log. I saw something about doit > silent but I do not understand why a change should not be save, why is that? > > >> >> >> > The drawback is that when changing a class from the browser's code >> > panel, it saves the definition twice. All the changes are saved as >> > "doit", so no change to the file in was necessary. >> >> What do you mean by doit? >> Normally only class def (which is a mistake) are saved like doit. > > > I agree that it is a mistake, but I think that the first steep is to save > everything. The next one should be to change the format. > I needed this fix becuase I lost a lot of work because pharo hanged on me > many times... > > >> >> > Ironically, I had a power down issue when testing it, so I did not >> > loose anything! (and help me to find a bug). >> > All the changes are tested. See ClassOrganizerTest, ClassTest and >> > StandardSourceFileArrayTest >> >> Hernan can you open an issue in the Bugtracker > > > I did, it is the 825, it is in the subject :-) > > > >> >> >> Stef >> > >> > Bye, >> > Hernan. >> > >> > >> > _______________________________________________ >> > Pharo-project mailing list >> > [email protected] >> > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> [email protected] >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >
_______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
