> > well, i wouldn't need or even want it in memory, so on disk is fine. the > problem is more likely management of the same. browsing the changes is not > really convenient. ideally i'd like to see versions in the class-browser > and > in the debugger, where on error i could then take a look at older versions > for > comparison, and switch to them to see if maybe the last change was the > cause of > the error. > > greetings, martin. > > There are versions already for methods. So the functionality is there.
I disagree however with you, I think that changes file was created for the precise scenarios of an image crash/ lockdown. In that case you may want to go back through the code and dont remember which method was triggered or what else was defined and created. In the case going chronologically which is how the changes file is already organised is far more useful than going method and class based. But I do agree it would be useful to extend the tools working with changes , but then none stop anyone from doing so and is not that hard to do.
