On 3 November 2011 14:41, Max Leske <[email protected]> wrote: > We manage our source code with Monticello and I have never had to use the > .changes file to get my code back. > As I've said before: as far as I'm concerned, .sources and .changes have > outlived their usefulness (not sure about the android and iPhone ports > though. There might be an advantage regarding memory / disk space?)
I'm tempted to say that if you've never had to use your .changes file to recover, you're not working hard enough :) Even without doing extra tricky things, consider your image open on your laptop. You shut the lid, having realised your train's just about to arrive at your stop. You get to where you're going and your laptop's decided to switch off. (Or your laptop battery runs flat.) Your .changes file lets you recover your work. frank > Max > > > On 03.11.2011, at 15:08, Igor Stasenko wrote: > >> On 3 November 2011 12:57, Guido Stepken <[email protected]> wrote: >>> I always thought, the IMAGE *is* already an OO database!?? >>> >> >> Yes, storing all sources in image should be also possible. >> The only problem with it, if your image crashes, you losing everything >> you did without chance of restoring it. >> That's why storing sources externally is better idea, at least from >> safety point of view. >> >> But again, it should be possible to choose where to store sources, not >> like today, when you have only .source and .changes. >> >> >>> Guido Stepken >>> >>> Am 02.11.2011 um 15:27 schrieb Igor Stasenko <[email protected]>: >>> >>>> How about new source code management? >>>> >>>> In terms of: >>>> - better abstraction of source code access in image >>>> - create a shared repository (database) , which can be used to browse >>>> the history of all source code of Pharo and its predecessor up to >>>> Squeak 1.0. >>>> >>>> We are discussed this idea couple times, and we already having some >>>> pieces of puzzle , like Ring. >>>> Also, there is already a project made by someone (forgot the name) , >>>> who already storing all source code in database and managing it there. >>>> >>>> -- >>>> Best regards, >>>> Igor Stasenko. >>>> >>> >>> >> >> >> >> -- >> Best regards, >> Igor Stasenko. >> > > >
