January 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Date fromString: '6-Jan-10'

by Peter Hugosson-Miller

This whole subject is my number one pet hate: ambiguous date representation. Seriously, after y2k and all the associated messing about fixing broken dates, one would think people would want to prevent anything like that ever happening again! IMNSHO, *all* dates should either be expressed as YYYY-MM-DD, or in a form using the three elements: month name; two-digit day number; four- digit year, in arbitrary order. Otherwise there will always be ambiguity, which will lessen slightly in 2013, and slightly more in 2032, but will never go away as long as people insist on using "10/6/11" and calling it a date. As for the problem in hand, I think the best solution would be to reject out of hand Strings that are ambiguous, and develop a tool for processing *collections* of "date" strings. This tool could infer which elements represented what by looking at the whole collection, and noticing patterns that give the clues needed to make the best guess, in much the same way as a human reader does. -- Cheers, Peter. On 16 jan 2010, at 13.39, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > no problem > we were not criticizing your fix more the problem in general > Would be nice to have a guessFrom: > > Stef > > On Jan 16, 2010, at 12:07 PM, David Hotham wrote: > >> Hello, >> >> The motivation behind this fix is that I am parsing historical >> stock data >> obtained from Google, in which dates are provided like this: "15- >> Jan-10". >> Of course I want this to read as 2010, not 1910. >> >> I agree that the existing solution (with or without my tweak) looks >> ugly. >> >> I gave brief consideration to a bigger fix which first checked what >> the >> current year was and then calculated what century to add to a low >> date. >> But, frankly, I couldn't be bothered. I figure that a one- >> character fix >> that is good for ten years isn't too bad. >> >> I am quite content to defer to others as to what the right solution >> is here. >> So long as there ends up being a convenient way to read two-digit >> years >> correctly, I'll be happy. >> >> David >> >> >> >> "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> wrote in >> message news:78E0F3D1-D169-43D9-B12E-6C9D4E2860C5@inria.fr... >>> hi guys >>> >>> can one of you give a look at the this fix because I'm confused. >>> Kernel-DavidHotham.538 >>> >>> year < 20 ifTrue: [year := 2000 + year] >>> was >>> year < 10 ifTrue: [year := 2000 + year] >>> >>> both solutions look strange to me. >>> >>> http://code.google.com/p/pharo/issues/detail?id=1749 >>> >>> >>> readFrom: aStream >>> "Read a Date from the stream in any of the forms: >>> <day> <monthName> <year> (5 April 1982; 5-APR-82) >>> <monthName> <day> <year> (April 5, 1982) >>> <monthNumber> <day> <year> (4/5/82) >>> <day><monthName><year> (5APR82)" >>> | day month year | >>> aStream peek isDigit >>> ifTrue: [day := Integer readFrom: aStream]. >>> [aStream peek isAlphaNumeric] >>> whileFalse: [aStream skip: 1]. >>> aStream peek isLetter >>> ifTrue: ["number/name... or name..." >>> month := (String new: 10) writeStream. >>> [aStream peek isLetter] >>> whileTrue: [month nextPut: aStream next]. >>> month := month contents. >>> day isNil >>> ifTrue: ["name/number..." >>> [aStream peek isAlphaNumeric] >>> whileFalse: [aStream skip: 1]. >>> day := Integer readFrom: aStream]] >>> ifFalse: ["number/number..." >>> month := Month nameOfMonth: day. >>> day := Integer readFrom: aStream]. >>> [aStream peek isAlphaNumeric] >>> whileFalse: [aStream skip: 1]. >>> year := Integer readFrom: aStream. >>>>> year < 20 ifTrue: [year := 2000 + year] >>> ifFalse: [ year < 1900 ifTrue: [ year := 1900 + year]]. >>> >>> ^ self >>> year: year >>> month: month >>> day: day >> >> >> >> _______________________________________________ >> 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

Jan. 16, 2010

Re: [Pharo-project] us the vm -memory in an image ?

by Mariano Martinez Peck

I agree with cesar. I would also like to discuss the default parameters. Several people said that Pharo was slow for them. Maybe changing the default values may help in some point of view. On Sat, Jan 16, 2010 at 2:55 PM, Alexandre Bergel <alexandre(a)bergel.eu>wrote: > I added http://code.google.com/p/pharo/issues/detail?id=1836 > > I haven't found your emails in the Cc field. > > Cheers, > Alexandre > > On 16 Jan 2010, at 01:17, John M McIntosh wrote: > > > Personally I think you need to add an entry. > > > > I am currently am doing a statistical study in this area for a > > client, of course not all of the data/solution will flow back to the > > community unless agreed to by the client, > > however I'll supply some numbers & thoughts to take us from the 1996 > > values into 2010. Also there will an active memory policy that will > > adjust some things to avoid > > some interesting edge cases as an example of the solution that lurks. > > > > On 2010-01-15, at 6:19 PM, csrabak(a)bol.com.br wrote: > > > >> I would only add the item if we could agree these parameters are to > >> used with such frequency to make the addition worthwhile. > >> > >> Do more users of Pharo feel in need to tweak these parameters > >> before delivering their projects to users in production? > >> > >> -- > >> Cesar Rabak > > > > -- > > = > > = > > = > > = > > = > > ====================================================================== > > John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: > > squeaker68882 > > Corporate Smalltalk Consulting Ltd. http:// > > www.smalltalkconsulting.com > > = > > = > > = > > = > > = > > ====================================================================== > > > > > > > > > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 16, 2010

Re: [Pharo-project] us the vm -memory in an image ?

by Alexandre Bergel

I added http://code.google.com/p/pharo/issues/detail?id=1836 I haven't found your emails in the Cc field. Cheers, Alexandre On 16 Jan 2010, at 01:17, John M McIntosh wrote: > Personally I think you need to add an entry. > > I am currently am doing a statistical study in this area for a > client, of course not all of the data/solution will flow back to the > community unless agreed to by the client, > however I'll supply some numbers & thoughts to take us from the 1996 > values into 2010. Also there will an active memory policy that will > adjust some things to avoid > some interesting edge cases as an example of the solution that lurks. > > On 2010-01-15, at 6:19 PM, csrabak(a)bol.com.br wrote: > >> I would only add the item if we could agree these parameters are to >> used with such frequency to make the addition worthwhile. >> >> Do more users of Pharo feel in need to tweak these parameters >> before delivering their projects to users in production? >> >> -- >> Cesar Rabak > > -- > = > = > = > = > = > ====================================================================== > John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: > squeaker68882 > Corporate Smalltalk Consulting Ltd. http:// > www.smalltalkconsulting.com > = > = > = > = > = > ====================================================================== > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Jan. 16, 2010

Re: [Pharo-project] Pharo 1.1 failing tests testAllLocalCallsOn

by Nicolas Cellier

Same for testAllCallsOn, this test is obsolete as soon as you make modifications in Pharo :) Such test should use specific classes and messages specially crafted for the test Nicolas 2010/1/16 Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com>: > testAllLocalCallsOn > Â Â Â Â " > Â Â Â Â self debug: #testAllLocalCallsOn > Â Â Â Â " > > Â Â Â Â | set | > Â Â Â Â set := Array allLocalCallsOn: #printOn:. > Â Â Â Â self assert: (set asArray = Â #('WeakActionSequence printOn:' 'Object > fullPrintString' 'Array printOn:' 'SequenceableCollection > asStringWithCr' 'Behavior printOn:' 'Class fileOutPool:onFileStream:' > 'Object printStringLimitedTo:' 'Collection printNameOn:' > 'ActionSequence printOn:' 'FixedIdentitySet printOn:')). > Â Â Â Â "This is a bit strange that allLocalCallsOn: returns a list of string!" > > This one is bad for two reasons: > 1) it relies on an arbitrary order in Set. For example, just change > default size of sets and the order will change. Eventually you could > test set = #() asSet but see 2) > 2) it relies on a particular snapshot of pharo and prevent pharo from evolving. > > Moreover, if a user adds its own sender of printOn: in an extension or > a subclass, this will make the test fail... > > Such test should create a class hierarchy dedicated to the test with a > know set of senders and test > Either correct it or remove it. > > Nicolas >

Jan. 16, 2010

[Pharo-project] Pharo 1.1 failing tests testAllLocalCallsOn

by Nicolas Cellier

testAllLocalCallsOn " self debug: #testAllLocalCallsOn " | set | set := Array allLocalCallsOn: #printOn:. self assert: (set asArray = #('WeakActionSequence printOn:' 'Object fullPrintString' 'Array printOn:' 'SequenceableCollection asStringWithCr' 'Behavior printOn:' 'Class fileOutPool:onFileStream:' 'Object printStringLimitedTo:' 'Collection printNameOn:' 'ActionSequence printOn:' 'FixedIdentitySet printOn:')). "This is a bit strange that allLocalCallsOn: returns a list of string!" This one is bad for two reasons: 1) it relies on an arbitrary order in Set. For example, just change default size of sets and the order will change. Eventually you could test set = #() asSet but see 2) 2) it relies on a particular snapshot of pharo and prevent pharo from evolving. Moreover, if a user adds its own sender of printOn: in an extension or a subclass, this will make the test fail... Such test should create a class hierarchy dedicated to the test with a know set of senders and test Either correct it or remove it. Nicolas

Jan. 16, 2010

Re: [Pharo-project] Date fromString: '6-Jan-10'

by StÃ©phane Ducasse

no problem we were not criticizing your fix more the problem in general Would be nice to have a guessFrom: Stef On Jan 16, 2010, at 12:07 PM, David Hotham wrote: > Hello, > > The motivation behind this fix is that I am parsing historical stock data > obtained from Google, in which dates are provided like this: "15-Jan-10". > Of course I want this to read as 2010, not 1910. > > I agree that the existing solution (with or without my tweak) looks ugly. > > I gave brief consideration to a bigger fix which first checked what the > current year was and then calculated what century to add to a low date. > But, frankly, I couldn't be bothered. I figure that a one-character fix > that is good for ten years isn't too bad. > > I am quite content to defer to others as to what the right solution is here. > So long as there ends up being a convenient way to read two-digit years > correctly, I'll be happy. > > David > > > > "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> wrote in > message news:78E0F3D1-D169-43D9-B12E-6C9D4E2860C5@inria.fr... >> hi guys >> >> can one of you give a look at the this fix because I'm confused. >> Kernel-DavidHotham.538 >> >> year < 20 ifTrue: [year := 2000 + year] >> was >> year < 10 ifTrue: [year := 2000 + year] >> >> both solutions look strange to me. >> >> http://code.google.com/p/pharo/issues/detail?id=1749 >> >> >> readFrom: aStream >> "Read a Date from the stream in any of the forms: >> <day> <monthName> <year> (5 April 1982; 5-APR-82) >> <monthName> <day> <year> (April 5, 1982) >> <monthNumber> <day> <year> (4/5/82) >> <day><monthName><year> (5APR82)" >> | day month year | >> aStream peek isDigit >> ifTrue: [day := Integer readFrom: aStream]. >> [aStream peek isAlphaNumeric] >> whileFalse: [aStream skip: 1]. >> aStream peek isLetter >> ifTrue: ["number/name... or name..." >> month := (String new: 10) writeStream. >> [aStream peek isLetter] >> whileTrue: [month nextPut: aStream next]. >> month := month contents. >> day isNil >> ifTrue: ["name/number..." >> [aStream peek isAlphaNumeric] >> whileFalse: [aStream skip: 1]. >> day := Integer readFrom: aStream]] >> ifFalse: ["number/number..." >> month := Month nameOfMonth: day. >> day := Integer readFrom: aStream]. >> [aStream peek isAlphaNumeric] >> whileFalse: [aStream skip: 1]. >> year := Integer readFrom: aStream. >>>> year < 20 ifTrue: [year := 2000 + year] >> ifFalse: [ year < 1900 ifTrue: [ year := 1900 + year]]. >> >> ^ self >> year: year >> month: month >> day: day > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 16, 2010

[Pharo-project] ConfigurationOfAlien

by Fernando olivero

Hi, i've updated the ConfigurationOfAlien. I've added groups and load shortcuts to the class. Thanks Mariano for the tips on metacello. John, I bother you once again, please put the new info on the page. To load Alien in a Pharo Dev image: Gofer new url: 'http://www.squeaksource.com/Alien' ; addPackage: 'ConfigurationOfAlien'; load. Then evaluate the desired group/s: ConfigurationOfAlien loadCore. ConfigurationOfAlien loadTests. ConfigurationOfAlien loadLibC. ConfigurationOfAlien loadMacOSX. ConfigurationOfAlien loadVMMaker. ConfigurationOfAlien loadWin32.

Jan. 16, 2010

Re: [Pharo-project] Object>>#actionMap -> (Object>>#actionMap "a CompiledMethod(1891)")

by Marcus Denker

On Jan 16, 2010, at 10:16 AM, StÃ©phane Ducasse wrote: > I was wondering if this is of > any interest to have the () and the compiled method with number because it breaks self evaluation for nothing. > > (Object>>#actionMap "a CompiledMethod(1891)") > when working with compiled methods, it makes it easy to see if you are looking (likely) at the same one. In turn, it makes it easy to see if a method is changed. With my tiny "in image" AST-to-BC JIT in Reflectivity, this was very useful to have. It's even useful when doing it "see, I invalidate the class, and all active methods are on the fly regenerated befor execution". Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Jan. 16, 2010

Re: [Pharo-project] Styles for Morphic

by Stan Shepherd

Igor Stasenko wrote: > > Hello guys, > > thinking, how to easily define styles, based on simple selection rules, > i sketched the class, MorphStyle. > > The principle how it works is simple: > > - you creating a style, add adding actions to it > - you then applying style to morph or group of morphs. > > Example: > > | style | > style := MorphStyle new > submorphs > model: #Browser; > color: Color red. > style applyTo: World. > > Let me describe in detail, what it does, when you applying it: > > style applyTo: World. > > Style initializing its current selection to be a collection with > single element - { World }. > Next thing, which it does is applying any actions , which we specified > during building the style, > namely: > > 'submorphs' - replacing the current selection by gathering all > submorphs of it, i.e. > > selection before: > #( World ) > selection after: > #( World's submorphs ) > > 'model: #Browser' - filter the current selection and leave only those > entries, which respond to #model and model class name is #Browser > > selection before: > #( world's submorphs ) > selection after: > { Browser SystemWindow#1. Browser SystemWindow#2. Browser > SystemWindow#3.Browser SystemWindow#4. } > > > 'color: Color red'. - since there's no such method in MorphStyle, it > is trapped by DNU handler and > converted to a #sendMessage: action. > A #sendMessage: action sends a specified message to current selection, > i.e.: > > { Browser SystemWindow#1. .... Browser SystemWindow#N. } > do: [:morph | message sendTo: morph ]. > > So, as result, if you doIt : > | style | > style := MorphStyle new > submorphs > model: #Browser; > color: Color red. > style applyTo: World. > > all browser windows color will be changed to red color. > > Some words about potential uses of this stuff. > > - theming, (through defining own style sheets). In contrast to > existing implementation, we're free to define anything, which morph > understands , > not just colors, border or fillstyle, but also, layout, fonts, > position etc etc. > > - defining styles in various ways: > following snippet sets the 'browse' button color to red for all > browser windows and illustrating how one style could reuse another > one. > > | browseButton buttonStyle browsers | > > buttonStyle := MorphStyle new color: Color blue. > browseButton := MorphStyle new allSubmorphs; has: #label equalTo: > 'browse'. > browsers := MorphStyle new model: #Browser. > > browseButton style: buttonStyle. "browseButton reusing buttonStyle" > browsers style: browseButton. "browser style reusing browseButton style" > > browsers applyTo: World submorphs. > > > It can be easily integrated with Morphic when using some global theme, > all we need is: > - add Morph>>applyThemeStyles > ^ World currentTheme applyStylesTo: self > > - send #applyStyles to morph, when its added to World. > > Also, we could integrate it with toolbuilder which will allow us to define > morph layouts, fonts, colors & initial properties more flexibly than > currently are . Non-morphic builders could just ignore the #setStyles: > message. > > Comments, suggestions , as always welcome. > > -- > Best regards, > Igor Stasenko AKA sig. > > +1 The builders and themes don't play nicely at present. There are 35 senders like: window := (SystemWindow labelled: labelString) model: self. So #labelled: creates a SystemWindow and asks the current UITheme to theme it, before it has any information to do so (model is still nil). So having more dynamic styles like this sounds a good way to sort this; I suspect it would also allow some theme related nasties to be removed. ...Stan -- View this message in context: http://n2.nabble.com/Styles-for-Morphic-tp4402731p4404007.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Jan. 16, 2010

[Pharo-project] [update 1.1] #11163

by StÃ©phane Ducasse

11163 ----- - Issue 1834: File fixes from trunk prior readbuffer - Fixing Base64MimeConverterTest - Issue 1829: testIndenting: remove? rely on the current font Stef

Jan. 16, 2010