On Cees de Groot wrote:
However, this is not 'fiddling with system
innards'.
Everything you do is logged in a changeset, and you can thus see what
you
changed, undo your changes, file them out to a text file and
throw
them at a version repository, etcetera. Yes, programming in an image-based Smalltalk is different from programming most other languages,
but
don't let that stop you from writing good code.
On the subject of changes is it possible if you could you go into a little more detail about how people handle version control with Squeak?
So, I gather, from what you're saying, that people file out the classes they've created (and the existing one's they've modified) out of Squeak and store them into their Version Control program on a periodic basis? Thus, providing the way to bring back individual classes or methods in an image to an earlier state (beyond what undo allows- especially after quitting and reopening Squeak). No?
Thanks,
Anthony
__________________________________ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo. http://search.yahoo.com
On Thu, 1 May 2003, Anthony Adachi wrote:
So, I gather, from what you're saying, that people file out the classes they've created (and the existing one's they've modified) out of Squeak and store them into their Version Control program on a periodic basis? Thus, providing the way to bring back individual classes or methods in an image to an earlier state (beyond what undo allows- especially after quitting and reopening Squeak). No?
Right.
For more info on one way this gets done, see: http://beta4.com/squeak/aubergines/docs/dvs.html
squeak-dev@lists.squeakfoundation.org