MC and cs need to work together.
The first (maybe?) easy problem. How to reorganize
class catagories only when necessary and in an MC
friendly manner.
What is the purpose of ClassName reorganize?
After I have added/removed/changed a method in a class
at the end of the changeset there will be a doit to
reorganize the entire list of class catagories.
This is THE major stumbling block to using changesets
with Monticello. Loading an even sllightly out of date
change set can upset MC's delicatly maintained idea of
which methods belong to which packages. The result is
lost methods. And harried and tired release teams.
Filing out goodies (single methods or classes) AFAIK
does not produce these reorganize doits. And somehow
they can be read in and squeak can adjust to whatever
catagory they are supposed to be in.
So why the massive reorganization? Can anyone here say
or point me to the authority on this?
Thanks for your help.
Yours in service and curiosity, -- Jerome Peace
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
Locked
