Because in the script manager has a save capability, would it be difficult to write the changes into the changes files ?
the problem is that the change files logic is old and it works 'well' for what it should but extending it will break other part. This is why slowly we will have to think to get something better.
Do you mean improving the change scanner parsing or throwing away and going for something different?
Hi eliot our vision is that we would like to have - all the code of all the squeak and pharo version in a queryable service available from the web. for that we want a source code metamodel a la ginsu or famix Use this metamodel to aggregate several meta models: pseudo class/rb make sure that when possible this model as a compative API with the one of classes and friends => tools reuse Veronica is working on that. Hernan will probably join. May be Colin should join. We could have a nice momentum. - for the changes we would like to have something else than a chunk format because invoking the parser to know if we are manipulating a class definition is bad (with token at: 2 do that and token at: 3 do that). Again it will take time but we should have a good (why not 'exquise') infrastructure so that we extend and build new tool easily. Stef