When i started working on the new Gaucho, i tried to use/understand the current 
change model without success. 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! 


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.


> 
>> 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

Reply via email to