- Pharo-dev - lists.pharo.org

Re: [Pharo-project] about

by Damien Cassou

On Wed, Jul 22, 2009 at 10:35 PM, StÃ©phane Ducasse<stephane.ducasse(a)inria.fr> wrote: > Juan pointed to me the following CUIS fixes that could interest us. > Now I feel not able to check that. > Is there somebody good (SIG for example :)) that could spend some time > on that? http://code.google.com/p/pharo/issues/detail?id=970 -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

July 23, 2009

Re: [Pharo-project] about

by StÃ©phane Ducasse

>> > Stef, i wish i could have more than a single life on that :) Me too :) > My current list of employment: > - work on paid project(s) > - work on own small project (will announce soon) > - finish work on VM+Image Process Scheduling refactoring gwenael could be interested in that since he is working on a kind of image virtualization > - work on DeltaStreams with Goran > - continue work on host windows refactoring > - continue work on Moebuis project > .. there could be more , which i missed unintentionally. > > so, i don't want to give any empty promises, that i will take a look > at it in nearest time. :( OK but we never now ;) > >> Stef >> >> >> Kernel: Semaphores, Delays, Processes, WeakReferences >> ------------------------------------------------------------------------- >> 0101-SafeDelay-2-ar.cs >> 0102-DelayTweaks-ar.cs >> 0103-DelayStartup-jmv.cs >> 0104-SemaCritical-ar.cs >> 0130-CreateSemaphoreTest-jmv.1.cs >> 0131-DelayCleanup-ar.1.cs >> 0132-AtomicProcessSuspend-ar.1.cs >> 0133-ProcessTerminateFix-ar.2.cs >> 0134-DelayWaitTimeout-ar.2.cs >> 0135-SignalExceptionFix-ar.1.cs >> 0136-assertFix-jmv.1.cs >> 0137-SemaTests-ar.cs >> 0173-offList-jmv.1.cs >> 0187-DelayWaitTimeout-ar.3.cs >> 0192-WeakMessageSendFixPart1-jmv-M7352.cs >> 0193-WeakMessageSendFixPart2-jmv-M7352.1.cs >> 0207-AvoidCreatingDelays-jmv.1.cs >> 0212-ForkSenders-jmv.1.cs >> 0213-ForkAnswersNil-jmv.5.cs >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > > -- > Best regards, > Igor Stasenko AKA sig. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 23, 2009

Re: [Pharo-project] Author class

by StÃ©phane Ducasse

Yes all that should be filtered :) Stef On Jul 23, 2009, at 11:09 AM, Douglas Brebner wrote: > StÃ©phane Ducasse wrote: >> no space in names >> sorry for van Neumann -> vanNeumann >> >> > Also beware of non-letters like - and ' (dash and apostrophe) which > can > and do appear. >> On Jul 23, 2009, at 12:58 AM, Douglas Brebner wrote: >> >> >>> Miguel CobÃ¡ wrote: >>> >>>> On Wed, Jul 22, 2009 at 2:53 PM, StÃ©phane >>>> Ducasse<stephane.ducasse(a)inria.fr> wrote: >>>> >>>>>> I can unify all the message sends to Author in the core image, >>>>>> also I >>>>>> can unify the initials and name usage, but >>>>>> >>>>>> >>>>> It would be nice :) >>>>> The prompt should ask for firstname.lastname and not initials :) >>>>> >>>>> >>>>> >>>> So I can replace all the prompts to initials for name in the format >>>> you mention. >>>> >>>> Will this format be the prefered/oficial one? >>>> Will other formats be allowed? Maybe asking for firstname and then >>>> for >>>> lastname and >>>> then inside Author concatenating in a firstname.lastname. >>>> >>>> What happens with someone with two firstnames and lastnames, like >>>> me: >>>> >>>> Miguel Enrique CobÃ¡ MartÃnez >>>> >>>> Firstname: Miguel Enrique >>>> Lastname: CobÃ¡ MartÃnez >>>> >>>> yes it is an bad example as I would write: >>>> >>>> Firstname: Miguel >>>> Lastname: CobÃ¡ >>>> >>>> What about spaces? >>>> >>>> >>> Spaces aren't avoidable since some names have them e.g. "von Braun". >>> Other things to consider are some cultures (like japanese) write >>> names >>> lastname, firstname and others have non-letter chars in their names >>> e.g. >>> irish names can have apostrophies like "O'Brien" and double >>> barrelled >>> names can have dashes. >>> >>> The best way to do it might be to just have a field for you to input >>> your name in your preferred form since proper international name >>> handling is complicated. >>> >>> > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 23, 2009

Re: [Pharo-project] Author class

by Douglas Brebner

StÃ©phane Ducasse wrote: > no space in names > sorry for van Neumann -> vanNeumann > > Also beware of non-letters like - and ' (dash and apostrophe) which can and do appear. > On Jul 23, 2009, at 12:58 AM, Douglas Brebner wrote: > > >> Miguel CobÃ¡ wrote: >> >>> On Wed, Jul 22, 2009 at 2:53 PM, StÃ©phane >>> Ducasse<stephane.ducasse(a)inria.fr> wrote: >>> >>>>> I can unify all the message sends to Author in the core image, >>>>> also I >>>>> can unify the initials and name usage, but >>>>> >>>>> >>>> It would be nice :) >>>> The prompt should ask for firstname.lastname and not initials :) >>>> >>>> >>>> >>> So I can replace all the prompts to initials for name in the format >>> you mention. >>> >>> Will this format be the prefered/oficial one? >>> Will other formats be allowed? Maybe asking for firstname and then >>> for >>> lastname and >>> then inside Author concatenating in a firstname.lastname. >>> >>> What happens with someone with two firstnames and lastnames, like me: >>> >>> Miguel Enrique CobÃ¡ MartÃnez >>> >>> Firstname: Miguel Enrique >>> Lastname: CobÃ¡ MartÃnez >>> >>> yes it is an bad example as I would write: >>> >>> Firstname: Miguel >>> Lastname: CobÃ¡ >>> >>> What about spaces? >>> >>> >> Spaces aren't avoidable since some names have them e.g. "von Braun". >> Other things to consider are some cultures (like japanese) write names >> lastname, firstname and others have non-letter chars in their names >> e.g. >> irish names can have apostrophies like "O'Brien" and double barrelled >> names can have dashes. >> >> The best way to do it might be to just have a field for you to input >> your name in your preferred form since proper international name >> handling is complicated. >> >>

July 23, 2009

Re: [Pharo-project] [ANN] 10388 new core image released

by StÃ©phane Ducasse

Yes marcus was trying to fix that when his graphic card fall apart dead burn. Stef On Jul 23, 2009, at 9:47 AM, Damien Cassou wrote: > There is a problem with this image: some packages are dirty (they have > unsaved changes in Monticello). > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Lambdas are relegated to relative obscurity until Java makes them > popular by not having them." James Iry > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 23, 2009

Re: [Pharo-project] Author class

by StÃ©phane Ducasse

On Jul 23, 2009, at 12:20 AM, Miguel CobÃ¡ wrote: > On Wed, Jul 22, 2009 at 4:32 PM, StÃ©phane > Ducasse<stephane.ducasse(a)inria.fr> wrote: >>> >>> 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. >> >> Yes this is the mess. >> Can you propose a nice solution? > > Ok, this is the proposal. > > The Author class will use only the name inst var and related methods. > The initials related are to be unused and later droped in a > subsecuent release. > > All the calls to initials methods will be replaced by names methods. > > The format for the name will be free, and suggested by the prompt > message to > > firstname.lastname > > but not enforced. > > It will not allow spaces, just letters and periods in places of > spaces e.g. > > Miguel CobÃ¡ -> miguel.coba > John The Hacker -> john.the.hacker > Peter O'Toole -> peter.otoole or maybe peter.o.toole > > This period in place of space can be discussed because monticello > replaces periods for "_". > Maybe 'firstname_lastname' should be suggested in the prompt. > > Every package not in core that use the initial methods should be > allowed to use the deprecated > initials methods but strongly urged to change to the names methods. use deprecated methods for that. > > At least in core, the initials should not be used anymore. > > What do you think? > > Miguel CobÃ¡ > > >> >>> Is the user only asked for name (forcing a format like >>> firstname.lastname) and the initials >>> are calculated accordingly? >> >> would be good but some people on ss have funky initials because >> theirs >> were taken. >> This is why initials does not scale. >> >>> 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. >> >> I think so. >> >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 23, 2009

Re: [Pharo-project] Author class

by StÃ©phane Ducasse

no space in names sorry for van Neumann -> vanNeumann Stef On Jul 23, 2009, at 12:58 AM, Douglas Brebner wrote: > Miguel CobÃ¡ wrote: >> On Wed, Jul 22, 2009 at 2:53 PM, StÃ©phane >> Ducasse<stephane.ducasse(a)inria.fr> wrote: >>>> I can unify all the message sends to Author in the core image, >>>> also I >>>> can unify the initials and name usage, but >>>> >>> It would be nice :) >>> The prompt should ask for firstname.lastname and not initials :) >>> >>> >> >> So I can replace all the prompts to initials for name in the format >> you mention. >> >> Will this format be the prefered/oficial one? >> Will other formats be allowed? Maybe asking for firstname and then >> for >> lastname and >> then inside Author concatenating in a firstname.lastname. >> >> What happens with someone with two firstnames and lastnames, like me: >> >> Miguel Enrique CobÃ¡ MartÃnez >> >> Firstname: Miguel Enrique >> Lastname: CobÃ¡ MartÃnez >> >> yes it is an bad example as I would write: >> >> Firstname: Miguel >> Lastname: CobÃ¡ >> >> What about spaces? >> > > Spaces aren't avoidable since some names have them e.g. "von Braun". > Other things to consider are some cultures (like japanese) write names > lastname, firstname and others have non-letter chars in their names > e.g. > irish names can have apostrophies like "O'Brien" and double barrelled > names can have dashes. > > The best way to do it might be to just have a field for you to input > your name in your preferred form since proper international name > handling is complicated. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 23, 2009

Re: [Pharo-project] [ANN] 10388 new core image released

by Damien Cassou

There is a problem with this image: some packages are dirty (they have unsaved changes in Monticello). -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

July 23, 2009

Re: [Pharo-project] Author class

by StÃ©phane Ducasse

I would not add a license on a method level. Stef On Jul 22, 2009, at 11:38 PM, Miguel CobÃ¡ wrote: > Also, check this bug in mantis > > http://bugs.squeak.org/view.php?id=6993 > > It can be added to the author class also and unify them in a single > place. > > > On Wed, Jul 22, 2009 at 4:35 PM, Miguel CobÃ¡<miguel.coba(a)gmail.com> > wrote: >> On Wed, Jul 22, 2009 at 2:53 PM, StÃ©phane >> Ducasse<stephane.ducasse(a)inria.fr> wrote: >>>> >>>> >>>> What is the goal with the Author class? I can see that the >>>> Utilities >>>> methods that used to be use to set >>>> author name and initials are being replaced with calls to Author. >>>> Also, they are deprecated in Utilities. >>>> Questions: >>>> >>>> Author has name and initials, what will be the intended use of >>>> them? >>> >>> We should not use initials. >> >> This means that all the methods referencing initials should be >> replaced with calls >> to equivalent name methods? >> >>> We should not use Utilities in the future. >>> >>>> By previous mails in the list I remember >>>> that Pharo doesn't want to use initials (like mcm, lr, avi) but >>>> full >>>> name as hinted by the message prompt in >>>> the Author requestName. But then initials will have exactly the >>>> same >>>> that name in the author class? >>> >>> It should be cleaned but nobody took the time. >>> >> >> I can do, but I need more directions >> >>>> I can unify all the message sends to Author in the core image, >>>> also I >>>> can unify the initials and name usage, but >>> >>> It would be nice :) >>> The prompt should ask for firstname.lastname and not initials :) >>> >> >> So I can replace all the prompts to initials for name in the format >> you mention. >> >> Will this format be the prefered/oficial one? >> Will other formats be allowed? Maybe asking for firstname and then >> for >> lastname and >> then inside Author concatenating in a firstname.lastname. >> >> What happens with someone with two firstnames and lastnames, like me: >> >> Miguel Enrique CobÃ¡ MartÃnez >> >> Firstname: Miguel Enrique >> Lastname: CobÃ¡ MartÃnez >> >> yes it is an bad example as I would write: >> >> Firstname: Miguel >> Lastname: CobÃ¡ >> >> What about spaces? >> >>>> I need to know the intended goal for this class. >>>> >>>> What is the goal? >>> >>> To represent metadata of the author. >>> Probably having initial and password for monticello/ squeaksource >>> makes sense. >>> >>> >> >> What is the reason to store the password, to automate login to >> squeaksource, or >> something like that? >> >> Thanks, >> Miguel CobÃ¡ >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >> > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 23, 2009

Re: [Pharo-project] Author class

by Michael Roberts

I made a start on changing this class but didn't finish it. One thing you should do is separate asking the developer for his name to encoding it. So there should be a form with multiple input fields. Then only internally do you apply the convention e.g. _ between fields. Second the initials string is stored as a string in the changes file. This is the hardest place to reify it into an object so I suggest to leave that encoded for the moment. Thirdly you need to update the versions tools that display this string directly. Thanks mike On Thursday, July 23, 2009, Damien Cassou <damien.cassou(a)gmail.com> wrote: > On Wed, Jul 22, 2009 at 9:53 PM, StÃ©phane > Ducasse<stephane.ducasse(a)inria.fr> wrote: >> The prompt should ask for firstname.lastname and not initials :) > > please choose FirstnameLastname instead to avoid problems with mcz > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Lambdas are relegated to relative obscurity until Java makes them > popular by not having them." James Iry > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

July 23, 2009