<br><br>On Fri, Sep 14, 2012 at 9:13 PM, Levente Uzonyi <<a href="mailto:leves@elte.hu">leves@elte.hu</a>> wrote:<br><br><br>>> My feeling is that "Author current" should be the only place where we<br>
>> lazily initialize by asking the user. Then Author>>initials would just<br>>> be a normal accessor, and Author class>>initials would go through<br>>> #current. The tricky bit with that idea is that we'd need a slightly<br>
>> more elaborate UI, so let the user fill in both initials and username.<br>><br>><br>> That doesn't seem to be too hard to do by checking both the initials and the<br>> name and ask for both one after the other if they are missing.<br>
<br>But remember, we'd be checking for the presence of an author object, and creating one from scratch, rather than checking each field separately. So we'd pretty much always have two dialogs in succession, which is a bit awkward. I suppose we could do a single dialog with a template like:<br>
<br><font face="courier new, monospace"> Author<br> username: 'Your Name'<br> initials: 'yn'.</font><div><br></div><div><font face="arial, helvetica, sans-serif">That's how most other tools work.</font></div>
<div><br>I just think that if we continue to treat initials and name as separate entities that can be set and queried independently, then there's not much point doing the extraction at all. We're just changing where the globals values are stored.<br>
<br>>><br>>> One idea would be to get rid of #username for now, and have Author<br>>> objects with just initials. Then in 4.5 we we'd flesh things out a bit<br>>> more.<br>><br>><br>> I wanted to separate Author from Utilities, but if we leave #authorName in<br>
> utilities, then it won't happen in 4.4.<br><br>Oh wow, I didn't even know we *had* authorName in Utilities. In that case, extracting it along with #authorInitials makes perfect sense. Strike my suggestion.<br>
<br>> Pharo uses #fullName for what we use #initials for. If we don't want our API<br>> to be compatible at this level, then we can use #fullName instead of<br>> #username.<br><br></div><div>Right, let's not introduce gratuitous incompatibility. How about #properName?</div>
<div><br></div><div>Colin</div>