Generalized Object Modules Design
Richard A. O'Keefe
ok at cs.otago.ac.nz
Wed Mar 6 23:06:23 UTC 2002
Concerning my proposal for change-set being associated with Browser,
"Lex Spoon" <lex at cc.gatech.edu> wrote:
It doesn't solve the case I usually run into. I'll do inst-var-defs and
then do implementors-of three times, and spot some code that I'd like to
change. If that code is in a different module, I still have to choose a
different changeset manually. I don't want to have to go find that method
in a different browser, either. The code is there, I'd like to change it and
have it go to the right changeset. In a lot of cases, this can be done.
I must admit I don't understand this, because I don't understand Squeak's
new modules yet (and this time I _did_ read all the pages I could find on
the Swiki).
I'm assuming that a group of related changes made as part of a single
"task" should go in the same changeset.
The rule is:
- a Project has a change set
- a Browser has a change set
- whenever you create a Browser, it starts with the same change set
as the thing you started it from.
So you're in a browser, whose changes go into change set X.
You see some code you want to change, so you spawn a new browser
from _within_ the browser where you're working.
The new browser will put its changes into change set X too.
If you want a browser to put its changes somewhere else,
open the new browser from the project background.
As far as I can see, it's never less convenient than the current
approach, and often more convenient.
More information about the Squeak-dev
mailing list
|