On Sep 5, 2010, at 9:45 AM, Fernando olivero wrote: > When i started working on the new Gaucho, i tried to use/understand the > current change model without success.
yes we can all forget. This part is ugly and brittle > So i chose to use the RB engine ( thanks lukas for nicely maintaining it!) > > In the soon to be released Gaucho1.1 i'm using RB changes to record every > change made to the system, changes that take part during a Gaucho development > session. > So i will be able to provide an insight to the feasability of using RB > changes to record and persist sessions, and easily provide undo's . Maybe > this work could be plugged into a new Pharo changes system! Yes we plan to use RBChange as a foundation infrastructure. I with veronica plan to also have a declarative code model so that we can do decent recentChanges and the rest. BTW there is a nice Undo framework of a couple of classes in sophie I added a first fileout to the bug entry. > > > Fernando > > pd: > BTW, i enhanced the RB changes with AddPackageRefactoring and others related > to the UI, ( in this way i'm also recording every UI event ). After the ESUG > i will try to integrate the relevant ones to RB. what are the UI event? because I would like to replacement SystemChangeNotifier events by announcements (check systemAnnouncement) as in ConfigurationOfRPackage. > > >> >>> Refactoring-Core, but would work independently) >>> Refactoring-Changes (this is currently part of Refactoring-Core, >>> but would work independently) >> >> yes I'm curious to see if/how we could use changes to represent changeset. >> > > > _______________________________________________ > 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
