Hi all,
I've published this package in http://www.squeaksource.com/mc
Definition: Allows to selectively merge changes which are without conflicts
among different version of one package.
Applicability: To be able to reject non conflictive and poor quality code. An
example can be a tired developer commiting bad parts of code due to distraction
or exhaustion and mergers are able to reject that parts preserving the quality
of the branch and that developer's health and best success :)
Note: if you install UI Enhancements from Gary, this package will also make you
able to use diff tools merger choosing, for each change, which is the winner and
the looser of the merge (which, IMHO, is the most useful tool for that this
days).
Sebastian Sastre, Apr, 2008
Hi all,
From the Sapphire web site I read:
Sapphire wants to take a fresh look at the Smalltalk philosophy and
current implementations. The idea is to produce high quality
open-source packages that will be loadable on a micro kernel.
As some of you know, I was a Smalltalk fan&developer in the last
twelve years. I have stopped working on smalltalk years ago... anyway,
I am happy to look forward the Squeak Smalltalk Community from time to
time.
I have republished an article on my blog, posted by me on
SqueakPeople, over 4 years ago:
http://blog.objectsroot.com/blog/2008/apr/29/boosting-squeak-rocksolid-imag…
The reason of this republish is simple: I am very happy to see a
Squeak code fork called "Sapphire" which share most of my thoughts.
I do not love code forks, and I avoided carefully them while working
for the Squeak Community.
Anyway, after some discussion I have seen on the list, I think
Sapphire is a good idea, and it should work nicely with Squeak main
code trunk, and vice-versa.
I will take a look to Sapphire, and you will find my throughts in the
next months on my blog.
You are free to leave comment on my blog.
My 1,25 cent (but they are euros, so I can say "my 2 (U.S.)
cents"... byeeee :-)
--
Giovanni Giorgi
Software Architect -- Senior Consultant
http://blog.objectsroot.com/
I have commands that I would like to make undoable. Is it possible to wrap
the commands within an "undoable" environment as suggested in
http://www.ceteva.com/forum/viewtopic.php?t=17
I imagine something like this (but wouldn't know where to start):
A>>setFoo: aFoo
Undoable newOn: [ foo := aFoo ]
A>>setBar: aBar
Undoable newOn: [ bar := aBar ]
a := A new foo: 0; bar: 0; yourself.
a setFoo: 5.
a setBar: 10.
Undoable undo. "a bar == 0"
Undoable undo. "a foo == 0"
Undoable redo. "a foo == 10"
Thanks - Sophie