On 21 Nov 2013, at 22:58, Chris Muller asqueaker@gmail.com wrote:
What's wrong with a dependency on System?
Because a dependency on system is a dependency on everything that system depends on... which is most of the image.
Is your overall goal to completely remove System from the system?
Not really. I want to give it a serious hair trim and break it up into pieces that make sense. Right now it's a bucket of things, without a coherent story. When you reply to this saying "it's the smalltalk environment" my reply is "no, the image is". System is the God Class antipattern applied to packages.
frank
On Thu, Nov 21, 2013 at 4:33 PM, Frank Shearar frank.shearar@gmail.com wrote:
On 21 November 2013 21:20, commits@source.squeak.org wrote:
Frank Shearar uploaded a new version of MonticelloConfigurations to project The Trunk: http://source.squeak.org/trunk/MonticelloConfigurations-fbs.118.mcz
==================== Summary ====================
Name: MonticelloConfigurations-fbs.118 Author: fbs Time: 21 November 2013, 9:20:19.085 pm UUID: aaba44a1-8cfd-4147-8d94-69d5fc5ac571 Ancestors: MonticelloConfigurations-cmm.117
Move the #upgradeIsMerge preference to MCConfiguration.
=============== Diff against MonticelloConfigurations-cmm.117 ===============
Just by the way, MonticelloConfigurations depends on System for one thing only now: Utilities' author stuff. I'm knocking up a completely lame minimal mimic-existing-stuff SystemAuthor that I will hopefully finish tomorrow. I plan to sever this dependency, and then remove all the references to Utilities authorName/Initials with SystemAuthor current, and then we can think about any other stuff we might do with this.
frank