February 2014 - Pharo-dev - lists.pharo.org

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/30735 Home: https://github.com/pharo-project/pharo-core

Feb. 2, 2014

[pharo-project/pharo-core] 84479c: 30735

by GitHub

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: 84479c3be512ca637893e3061cf4843e85816d5b https://github.com/pharo-project/pharo-core/commit/84479c3be512ca637893e306… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-02-02 (Sun, 02 Feb 2014) Changed paths: A Polymorph-Widgets.package/ListDialogWindow.class/instance/actions/doubleClickOk.st M Polymorph-Widgets.package/ListDialogWindow.class/instance/items creation/buildListMorph.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script388.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30735.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Tools.package/AbstractTool.class/class/private/requestProtocolNameFor_initialAnswer_.st M Tools.package/AbstractTool.class/instance/class/addCategoryIn_before_.st Log Message: ----------- 30735 12469 Sometimes an empty protocol is created https://pharo.fogbugz.com/f/cases/12469 http://files.pharo.org/image/30/30735.zip

Feb. 2, 2014

Re: [Pharo-dev] ZTimestamp>>monthName spelling error

by Norbert Hartl

Am 01.02.2014 um 17:26 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: > Sabine, > > On 01 Feb 2014, at 15:15, Sabine KnÃ¶fel <sabine.knoefel(a)gmail.com> wrote: > >> Hi Sven, >> >> thank you for the quick fix. It works fine now. >> >> I do not call this directly but from >> DateAndTime date: self endDate time: self endTime >> >> Your example: >> I am no english native speaker but I assume, that 'saterday' should be spelled as 'saturday'. >> If yes, there are several occurences of saterday. > > Terrible spelling of me! > > === > Name: ZTimestamp-SvenVanCaekenberghe.33 > Author: SvenVanCaekenberghe > Time: 1 February 2014, 5:18:50.139922 pm > UUID: 40111894-d387-432a-a3e1-2245af4a269b > Ancestors: ZTimestamp-SvenVanCaekenberghe.32 > > Even worse: Saterday => Saturday (thx Sabine KnÃ¶fel) > === > > ConfigurationOfZTimestamp has been updated everywhere. > >> I saw this when trying your example: >> >> (ZTimestampFormat fromString: 'Saterday, 3 February, 2001') >> german; >> format: Date today. ==>>'Samstag, 1 Februar, 2014' >> >> (ZTimestampFormat fromString: 'Saturday, 3 February, 2001') >> german; >> format: Date today. ==>>'Samurday, 1 Februar, 2014' >> >> Also, 'Samurday' is no german word. 'Saturday' means 'Samstag' in German. > > Now that example should work: > > (ZTimestampFormat fromString: 'Saturday, 3 February, 2001') > german; > format: Date today. > > => 'Samstag, 1 Februar, 2014â Does ZTimestampFormat handle the formatting of the date? If so then for germany it would be Samstag, 1. Februar 2014 Norbert > > Thanks for the feedback. > > Sven > >> Regards >> Sabine >> >> >> On Sat, Feb 1, 2014 at 1:31 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> Sabine, >> >> On 01 Feb 2014, at 12:52, Sabine KnÃ¶fel <sabine.knoefel(a)gmail.com> wrote: >> >>> Hi Sven, >>> >>> could you change Februari into February please? >> >> Ah, terrible typo, it was all over the place. >> >> === >> Name: ZTimestamp-SvenVanCaekenberghe.32 >> Author: SvenVanCaekenberghe >> Time: 1 February 2014, 1:27:02.50151 pm >> UUID: 70fd3b88-e15e-4139-922c-9c602e3fc532 >> Ancestors: ZTimestamp-SvenVanCaekenberghe.31 >> >> The English spelling of the 2nd month name was consistently wrong: Februari instead of the correct February (thx Sabine KnÃ¶fel); >> Now use #monthIndex instead of the less consistent #month >> === >> >> Btw, did you know you can do: >> >> (ZTimestampFormat fromString: 'Saterday, 3 February, 2001') >> german; >> format: Date today. >> >> => 'Samstag, 1 Februar, 2014' >> >> Regards, >> >> Sven >> >>> (I use http://mc.stfx.eu/Neo, this is the right place?) >>> >>> Regards >>> Sabine >>> >>> ZTimestamp>>monthName >>> "Return the English name of the month of the receiver, according to the >>> Gregorian calendar, a Symbol" >>> >>> ^ #(January Februari March April May June July August September October >>> November December) at: self monthIndex >>> >>> >>> >>> -- >>> View this message in context: http://forum.world.st/ZTimestamp-monthName-spelling-error-tp4740821.html >>> Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >>> >> >> >> > >

Feb. 2, 2014

Re: [Pharo-dev] subscript out of bounds in protocol creation

by Jordi Delgado

Hi, I downloaded the most recent image with the most recent VM. I'm using a macbook air with Mountain Lion 10.8.5, image 30733 and System Reporter says: Virtual Machine --------------- /Users/jdelgado/Smalltalk/Pharo-latest/Pharo.app/Contents/MacOS/Pharo NBCoInterpreter NativeBoost-CogPlugin-GuillermoPolito.19 uuid: acc98e51-2fba-4841-a965-2975997bba66 Dec 26 2013 NBCogit NativeBoost-CogPlugin-GuillermoPolito.19 uuid: acc98e51-2fba-4841-a965-2975997bba66 Dec 26 2013 https://github.com/pharo-project/pharo-vm.git Commit: e698e14f38003258fa49506b14307d83863a5ac1 Date: 2013-12-16 06:32:59 -0800 By: Esteban Lorenzano <estebanlm(a)gmail.com> Jenkins build #14780 Mac Cocoa Cog 5.8b12 21-Sep-10 >1B0534FA-246C-47C5-AB29-7A76C81CCDCB< VMMaker versionString https://github.com/pharo-project/pharo-vm.git Commit: e698e14f38003258fa49506b14307d83863a5ac1 Date: 2013-12-16 06:32:59 -0800 By: Esteban Lorenzano <estebanlm(a)gmail.com> Jenkins build #14780 NBCoInterpreter NativeBoost-CogPlugin-GuillermoPolito.19 uuid: acc98e51-2fba-4841-a965-2975997bba66 Dec 26 2013 NBCogit NativeBoost-CogPlugin-GuillermoPolito.19 uuid: acc98e51-2fba-4841-a965-2975997bba66 Dec 26 2013 However: This time the error does not appear, no matter what I do. Maybe it's solved (?) Bests, Jordi > > Am 01.02.2014 um 16:41 schrieb Jordi Delgado <jdelgado(a)lsi.upc.edu>: > > > That's what I mean, I did *exactly* that, and the chosen class was > > KMKeymapBuilder (from Keymapping-Pragmas package). The private > > protocol was added with no problem. So...? No idea. > > > > Bests, > > > > Jordi > > > > PS: Also with a freshly 30733 image downloaded > > > > > OK, I tried it with KMKeymapBuilder and got the errors. > So we need to check for the operating system and VM. > On my machine (OSX 10.9.1) System Reporter says for VM General: > > Virtual Machine > --------------- > /Applications/Pharo.app/Contents/MacOS/Pharo > NBCoInterpreter NativeBoost-CogPlugin-GuillermoPolito.19 uuid: acc98e51-2fba-4841-a965-2975997bba66 Dec 12 2013 > NBCogit NativeBoost-CogPlugin-GuillermoPolito.19 uuid: acc98e51-2fba-4841-a965-2975997bba66 Dec 12 2013 > https://github.com/pharo-project/pharo-vm.git Commit: 71adca113a9aff2876288927e5c1c86bf7ac13e2 Date: 2013-12-07 05:00:47 -0800 By: Philippe Back <philippeback(a)gmail.com> Jenkins build #14777 > > Mac Cocoa Cog 5.8b12 21-Sep-10 >1B0534FA-246C-47C5-AB29-7A76C81CCDCB< > VMMaker versionString https://github.com/pharo-project/pharo-vm.git Commit: 71adca113a9aff2876288927e5c1c86bf7ac13e2 Date: 2013-12-07 05:00:47 -0800 By: Philippe Back <philippeback(a)gmail.com> Jenkins build #14777 > NBCoInterpreter NativeBoost-CogPlugin-GuillermoPolito.19 uuid: acc98e51-2fba-4841-a965-2975997bba66 Dec 12 2013 > NBCogit NativeBoost-CogPlugin-GuillermoPolito.19 uuid: acc98e51-2fba-4841-a965-2975997bba66 Dec 12 2013 > > > What are you using? > > Regards, > Andreas > > > > > > > >> Hi Jordi and all, > >> > >> here is my detailed receipt with a freshly downloaded 30733.zip from Pharo files: > >> > >> 1. Open Nautilus > >> 2. Select an arbitrary package > >> 3. Select an arbitrary class from that package > >> 4. Right-click in the methods panel and select ÂAdd protocolÂÂ from the popup menu. > >> 5. Enter ÂprivateÂ in the dialog without selecting any entry in the listbox on top. > >> 6. Hit ÂenterÂ or press ÂOKÂ with a left-click. > >> > >> -> Bummer! A cascade of 3 "SubscriptOutOfBounce: 1Â pre-debuggers. > >> > >> Regards, > >> Andreas > >> > >> > >> > >> Am 01.02.2014 um 11:46 schrieb Jordi Delgado <jdelgado(a)lsi.upc.edu>: > >> > >>> Hi, > >>> > >>> With a fresh image, I do that with a class randomly selected > >>> (obviously, with no class selected nothing happens) and the > >>> protocol gets added without problems. Then, I choose another class, > >>> again I pick a random one, and after doing exactly the same the > >>> error appears. Why? No clue. > >>> > >>> I said that the error is difficult to reproduce because sometimes > >>> it appears, and sometimes not. And I am not able to ascertain the > >>> circumstances under which it will pop up. > >>> > >>> Bests, > >>> > >>> Jordi > >>> > >>> > >>> > >>> > >>>> Hi, > >>>> > >>>> Am 31.01.2014 um 08:36 schrieb Jordi Delgado <jdelgado(a)lsi.upc.edu>: > >>>> > >>>>> Hi, > >>>>> > >>>>> I realized that sometimes, when creating new protocols, it appears an > >>>>> error "subscript out of bounds: 1". I have not been able -yet- > >>>>> to reproduce it from a clean image, but it happens often (at least > >>>>> to me). It seems to me that it has something to do with protocol > >>>>> creation before any method has been written, but I am still investigating. > >>>>> > >>>> I guess I can produce this easily :-) > >>>> Just hit ÂAdd protocolÂÂ in the popup menu of the method protocol pane. > >>>> Enter a name like ÂprivateÂ in the dialog. And then press enter without selecting anything in the listbox above. > >>>> And voilÃ Â > >>>> > >>>> Regards, > >>>> Andreas > >>>> > >>>> > >>>> > >>> > >> > >> > > > >

Feb. 2, 2014

Re: [Pharo-dev] poolDictionaries removal breaks my projects

by Sven Van Caekenberghe

Why state 'responded' - would it not be better if the monkey checked the slice, even though no unit tests will hit the change, it shows at least that nothing obvious broke. On 02 Feb 2014, at 09:12, Pharo4Stef <pharo4Stef(a)free.fr> wrote: > I added https://pharo.fogbugz.com/default.asp?12769 > Fix included. > took me less than 10 min including downloading the latest version of Pharo and scanning complete sources. > > Stef

Feb. 2, 2014

Re: [Pharo-dev] poolDictionaries removal breaks my projects

by Hilaire Fernandes

Le 31/01/2014 13:21, Esteban Lorenzano a Ã©crit : > Said soâ¦ I still does not understand why this particular change couldnât wait for pharo 4. But wellâ¦ now is there, so it needs to work fine. As long as you don't learn to reject, you will face this situation over and over. Believe me. Hilaire -- Dr. Geo http://drgeo.eu

Feb. 2, 2014

Re: [Pharo-dev] [Review]: Case 12737 Morph sends mouseUp twice to handlers

by Pharo4Stef

Well did we lived perfectly with it over last year? yes -> 40 no -> 30 > > > > Because changing Morphic now sounds a bit shaky to me :) > That's why I'm asking for a lot of input. But it is a bug. And I think this slice version is very unlikely to break anything - 2 lines changed. I'd at least appreciate someone taking a look. If you agree that it's a straight-forward change, I will take responsibility for getting it right or reverting. > > Cheers, > Sean > > View this message in context: Re: [Review]: Case 12737 Morph sends mouseUp twice to handlers > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Feb. 2, 2014

Re: [Pharo-dev] poolDictionaries removal breaks my projects

by Pharo4Stef

I added https://pharo.fogbugz.com/default.asp?12769 Fix included. took me less than 10 min including downloading the latest version of Pharo and scanning complete sources. Stef

Feb. 2, 2014

Fwd: poolDictionaries removal breaks my projects

by Pharo4Stef

Begin forwarded message: > From: StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > Subject: Re: [Pharo-dev] poolDictionaries removal breaks my projects > Date: 2 Feb 2014 00:56:28 GMT+1 > To: Pharo Development List <pharo-dev(a)lists.pharo.org> > > >>>> +1 on this >>> >>> There are some kinds of students who are going to find Smalltalk difficult, yes. I do not see how removing pooldictionaries from the class creation template will affect them. If they ask about them, you can say that they are there and point them to the new class creation message. And take advantage of that to say that class creation is just a message send while you are at it :-) >> >> If your students have problems to grasp the concept of pool dictionaries then how do they deal with mathematics and computer science? > > This is the proof that you never taught. I never got the time to arrive to pool. Why would I teach them something that I used two times over the last 15 years of programming (ok I just wrote moose and some parts of Pharo :). > > Why should I spend time on a detail when I can teach them real OO design? > Do you think that I attract people to Smalltalk teaching them about Pool? or because I ask them why the way boolean is implemented is so mind-blowing? I let you guess. Now during my last lectures (4.5 h in total this year). > One guy leo came after the lecture and told that he loves the way boolean are implemented and that he wants to an internship with us. > > Is it enough or I should continue? > > > >>>>> âoldtimersâ need freedom. This is one of the reasons I really enjoy dynamic typing and Smalltalk. I donât like to obey to artificial rules that only >>>>> put permanent burden to me in order to protect me from something I might do wrong sometimes. >>> >>> You still have the freedom to use pool dictionaries. They are still there. >> They are hidden for the sake of simplicity for some students. >> I want my pool dictionaries back :-D > > Donât use them you do not need them. > Why you cannot express the same with a class and a classvar + messages? > >>>>> >>>> >>>> If you donât see features you donât know what the machine can do for you. >>>> >>>> Obscuring things is sometimes a good design strategy, but here there is a well known artefact breaking tradition here, that isnât something light. And the proposed alternative design is far to be better (read: have been proven itself worth of its added burden of breaking that tradition) >>> >>> So if we cannot break tradition then Traits should never have been introduced? >> Traits are a different kind of thing. They didnât cripple existing elements in Pharo. > > really? > did you see the real class template with traits? It should be like that if we follow your reasoning > > Object subclass: #NameOfSubclass > uses: T1 (#bar -> #zork) + T2 - {#foo} > instanceVariableNames: '' > classVariableNames: '' > poolDictionaries: '' > category: 'CollectionsTests-Strings' > > > > > CollectionRootTest subclass: #StringTest > uses: TIncludesTest + TCloneTest + TCopyTest + TSetArithmetic + TIterateSequencedReadableTest + TPrintOnSequencedTest + TAsStringCommaAndDelimiterSequenceableTest + TIndexAccess + TSequencedElementAccessTest + TSubCollectionAccess + TPutBasicTest + TCopySequenceableSameContents + TCopyPartOfSequenceable + TCopyPartOfSequenceableForMultipliness + TCopySequenceableWithOrWithoutSpecificElements + TCopySequenceableWithReplacement + TReplacementSequencedTest + (TConvertTest - {#testAsByteArray}) + TConvertAsSortedTest + TBeginsEndsWith + (TIndexAccessForMultipliness - {#testIdentityIndexOfIAbsentDuplicate. #testIdentityIndexOfDuplicate. #collectionWithNonIdentitySameAtEndAndBegining}) + TSequencedConcatenationTest + TPutTest + TConvertAsSetForMultiplinessTest + TSortTest + TSequencedStructuralEqualityTest + TOccurrencesForMultiplinessTest + TCreationWithTest > instanceVariableNames: 'string emptyString elementInNonEmpty notIn nonEmpty1element withoutEqualElements collectionNotIncluded indexInNonEmptyArray sameAtEndAndBegining nonEmpty5ElementsSorted unsortedCollection subcollection3ElementsSorted arrayWithCharacters' > classVariableNames: '' > poolDictionaries: '' > category: 'CollectionsTests-Strings' > > > >> The only problem was the lack of tool support when they were introduced. You are comparing apples and oranges. >> >>> >> For generations of Smalltalk newbies it was possible to either grasp the concept or ignore it. > > How do you measure that we did not fail? > >> Why do you need to change this without a real solution for those who want to use them? >> In my eyes itâs an absolute minority of Pharo users who arenât able to understand the concept. > > Again let me repeat. This is not a question of not being able to understand or not. > This is an accessibility point. Why do we overhelm people with unnecessary information. > Now think about it for real (read what I wrote) because I will stop reading this thread. > > >>>> Itâs a half-ass non-solution >>>> >>>> Do you really love cleaning that up? >>> >>> >>> This half-assed non-solution is the same solution as for Traits, essentially. Do you have the same issue with Traits? >>> >> Again you are comparing apples and oranges. Traits didnât take away anything but brought something new. > > No :) > This is why I do not like traits. > >> You took away something. >> BTW how do your students cope with Traits? They must be completely overwhelmed. > > They do not see them. because empty traits are not in the class template nor in the definition of classes that do not use them. > Can you reread this sentence please? > >> And how do you teach the class hierarchy and meta classes? > > much simpler. > >> >> >> >>>> The second part of your homework on this design decision was completely ignored so expecting it to be loved (popular) is unrealistic >>>> >>>> And by not doing that you just added a problem where there was none >>>> >>>> Not willing to do that second part? >>>> >>>> Then donât fix what isnât broken. >>> >>> Please see previous mail. >> >> I am a close lurker of the mailing lists and I completely missed it. >> >> Regards, >> Andreas >

Feb. 2, 2014

Fwd: poolDictionaries removal breaks my projects

by Pharo4Stef

Begin forwarded message: > From: StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > Subject: Re: [Pharo-dev] poolDictionaries removal breaks my projects > Date: 2 Feb 2014 00:30:04 GMT+1 > To: Pharo Development List <pharo-dev(a)lists.pharo.org> > > Johan > > YOU ARE RIGHT, RIGHT, RIGHT, RIGHT. I spent a significant amount of time teaching Smalltalk to know that you are right. > And this change will be in the system :) > > Just people that know something totally ignore what is it to learn something. > Imagine people are scared and close the debuggers. Oscar wrote patterns and I always say the debugger is your best friend so do not close it. > > Stef > >> >>>> I donât see how this change make Smalltalk (the language) simpler. For me this change looks more like an obfuscation than a simplification. >>> >>> How many lectures did you give? It is annoying to have to explain something that usually people do not need to know. >> >> To complement this: in my own experience as a full-time prof, whenever you are teaching and at a given point you need to say: 'I cannot explain this yet' or resort to handwaving there is something wrong. Do I need to explain pooldictionaries to be able to talk about class creation? No, I should not need to do that. >> >> I get this feeling with Java all the time. First hello world example in Java is always a mess. public static void main(String[] args) OMG. Start to explain all that just to do a println? Were is the simplicity there? I don't want to have this kind of feeling when I explain Smalltalk. >> >>>> How should newcomers know how to enter pool dictionaries? I rarely use pool dictionaries and if I will need it I surely have forgotten about >>>> this change and expect irritation and frustration. >>> >>> Newcomers do not use pooldictionaries. In 10 years smalltalking I used them twice. >> >> I agree with Stef that pooldictionaries are advanced features. I have been Smalltalking since 1998 and I have never used them. >> >> >> ---> Save our in-boxes! http://emailcharter.org <--- >> >> Johan Fabry - http://pleiad.cl/~jfabry >> PLEIAD lab - Computer Science Department (DCC) - University of Chile >> >> >

Feb. 2, 2014