Back when Levente approached this, we had a detailed discussion about it. I think we should all go back and read that before introducing a SystemAuthor class.
Personally, I wouldn't mind just having
Smalltalk authorInitials "answers a String"
until we decide we need to support multiple concurrent Author objects with more than just name and initials..
And this makes sense anyway -- Smalltalk's current #author.
I struggle with having a whole class (SystemAuthor) when we cannot take proper advantage of it and only really need one String field at this time, not a heavy-weight, value-holder singleton.
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