On Wed, Jul 22, 2009 at 2:25 PM, Alexandre Bergel<alexandre@bergel.eu> wrote:
This package, in the last core image is modified but not commited so when following the steps from the HowToContribute wiki page, in the part of creating a mcz package with the change the mcz generate will include the other uncommited changes. Should I use a changeset instead in order to not commit changes that I don't want?
First, you should update your image. It should be a core. Your change must be produced for Core. Then, implement your fixe. If more than one package is touched, then produce a slice. You should save your fix in PharoInbox using Monticello. Last step, make sure your fix load in a fresh and updated core image; add an issue in the google website; send an email to the mailing list.
Yes, I know, that is what I was doing. My confusion was when opening the changes windows in the monticello browser for the morphic package. I saw not just the change of my changeset, but also the last changes to the package, that is because I thought that were uncommited packages Now I have checked the generated mcz following the process and indeed it only contains my change. I will push it to PharoInbox.
What is the goal with the Author class?
A reification of author. Authors should not be strings passed around.
Author has name and initials, what will be the intended use of them?
It is true that we should not use initials anymore, but essentially for legacy purpose, we cannot remove them. We could envision future version of the class Author that includes email, squeak source account, ...
Yes but I mean, in a clean core image, on first method save it asks for the initials, this is stored on the initials inst var of the singleton Author. But on the World Menu, the set author name, it stores (in a firstname.lastname format) the value entered in the name inst var So, setting one, doesn't set the other. Also, the messages are different for each one (rightly, because are different things) but I want to know what is the inteded behavior from now on to trying to do the changes. Is the user only asked for name (forcing a format like firstname.lastname) and the initials are calculated accordingly? Are the initials doomed to disappear, and the only interface will be the name (and possibly the email and other fields mentioned) to identify a person? This means to modify all the senders to initial methods and point them to name methods. With the time, the initials inst var will be droped from the Author class. Thanks for your answers, Miguel Cobá
I can unify all the message sends to Author in the core image, also I can unify the initials and name usage, but I need to know the intended goal for this class.
The only use of Author is for managing the name/initial used in the .changes and monticello.
Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel  http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project