Excerpts from Dimitris Chloupis's message of 2015-12-07 08:24:13 +0100: > > 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.
> There are versions already for methods. So the functionality is there. only if i save them in monticello though, and i can't just switch the version of a single method, only the whole changeset at once. in git i can limit browsing to a specific file, and then copy an old version of a file into the current workspace. it is a bit crude, but it can be done. i don't see that kind of functionality in pharo. the data is there, but the tools to use the data in this specific manner are not. > I think that changes file was created for the > precise scenarios of an image crash/ lockdown. indeed, i agree, changes are to recover from an image crash, and less useful to browse old versions of code. > 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. true, but that's not enough to use as an argument to "sell smalltalk" so i am afraid, all we can say about in-image versioning is: it's possible, but current tools don't support it. (note that i have no issue with the current state. dreaming about what we could do is nice, but it is important to be aware of what is currently well supported, and what isn't so that we avoid to oversell features that aren't practically usable.) greetings, martin. -- eKita - the online platform for your entire academic life -- chief engineer eKita.co pike programmer pike.lysator.liu.se caudium.net societyserver.org secretary beijinglug.org mentor fossasia.org foresight developer foresightlinux.org realss.com unix sysadmin Martin Bähr working in china http://societyserver.org/mbaehr/
