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

Re: [Pharo-project] Fwd: ChangeSorter vs. ChangeOrganizer as entry point

by Mariano Martinez Peck

http://code.google.com/p/pharo/issues/detail?id=1838 On Sun, Jan 3, 2010 at 2:13 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>wrote: > > > > > > hahahahhahah if you remove for example the ChangeSorter you break that > haha. > > I am totally agree stef. > > > > I searched references for ChangeSorter and it is everywhere :( > > We should check because I remember Pavel did a migration once. > _______________________________________________ > 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] [ANN] Pharo News Blog

by Alexandre Bergel

Excellent Alexandre On 16 Jan 2010, at 13:48, Adrian Lienhard wrote: > Hi all, > > We've started a blog on the Pharo website: > > http://www.pharo-project.org/news > > The goal of this blog is to regularly publish interesting news about > Pharo (maybe once or twice a month). This allows people who do not > have the time to closely follow the mailing list to stay up to date. > > Hope you like it! > > Cheers, > Adrian > ___________________ > http://www.adrian-lienhard.ch/ > > > _______________________________________________ > 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] us the vm -memory in an image ?

by csrabak＠bol.com.br

I agree with the intent but cannot figure out a means for evaluating (testing) the tweaking of the parameters in 'scientific' way!! -- Cesar Rabak Em 16/01/2010 12:15, Mariano Martinez Peck < marianopeck(a)gmail.com > escreveu: 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] Date fromString: '6-Jan-10'

by csrabak＠bol.com.br

I'm afraid the 'fix' is trying to repair something is not broken! Date fromString: '6-Jan-10'. giving "6 January 1910" has not anything wrong. Within five year we'll have users/programmers complaining that: Date fromString: '6-Jan-16'. gave "6 January 1916" and *obviously* it should have given "6 January 2015"!! Rather document that years given with two figures get counted from 1900 (as it used to be in last century) and have people to use four digits for years in the 2000s. Otherwise: 1) We need to get used to the concept of an epoch time for Pharo; or 2) the number to be tested has to be the current year! My 0.019999. . . -- Cesar Rabak Em 16/01/2010 07:57, StÃ©phane Ducasse < stephane.ducasse(a)inria.fr > escreveu: 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: (5 April 1982; 5-APR-82) (April 5, 1982) (4/5/82) (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

Re: [Pharo-project] Toyota like process for 1.1

by Mariano Martinez Peck

My only comment is that I see continuous integration for 1.1 but this has absolutely no sense if we don't fix the tests as soon as they happen. So, or we do that, or we remove Continuous Integration for the milestone :) cheers Mariano On Sat, Jan 16, 2010 at 11:38 AM, StÃ©phane Ducasse < stephane.ducasse(a)inria.fr> wrote: > > On Jan 16, 2010, at 11:33 AM, Levente Uzonyi wrote: > > > On Sat, 16 Jan 2010, StÃ©phane Ducasse wrote: > > > >> issue 1827 soon in 11162 > >> > >> Fixed > >> - testComplIsSelfEvaluating removed the compiledMethod from the > array since the store on probably changed and > >> compiled methods are not self evaluating > >> > >> SimpleSwicthMorph>>testName removed (no external name anymore) > >> > >> AuthorTest>>testDeprecation removed (since the methods are not > there anymore) > >> > >> > >> Changed last line since a test should not rely on something on the > harddisc > >> > >> testIsFontAvailable > >> "self debug: #testIsFontAvailable" > >> (Locale isoLanguage: 'ja') languageEnvironment removeFonts. > >> self assert: (Locale isoLanguage: 'en') languageEnvironment > isFontAvailable. > >> "Next test should fail after installing Japanese font" > >> self assert: (Locale isoLanguage: 'ja') languageEnvironment > isFontAvailable not. > >> (Locale isoLanguage: 'ja') languageEnvironment installFont. > >> self assert: (Locale isoLanguage: 'ja') languageEnvironment > isFontAvailable not > >> > >> > >> TextDiffBuilderTest>>expectedFailures > >> "these tests are for the new TextDiffBuilder that should be > integrated from Squeak-trunk" > > > > To be exact, these are broken with the current implementation. > Integrating the new TextDiffBuilder should be easy. > > yeap! > > Stef > _______________________________________________ > 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] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1

by Mariano Martinez Peck

Thanks GermÃ¡n, you asked a very good question. I already asked Dale as soon as I read your email. I suggest you subscribe to metacello group as Dale is maintaining all Seaside related configurations. For the moment, would you mind trying this in this dev (clean): That will load Seaside 2.8 + Magritte (ConfigurationOfMagritte project version: '1.2.1') load: #('Magritte-Model' 'Magritte-Tests' 'Magritte-Seaside' ) I didn't found anything for 3.0 And for Pier + Magritte + Seaside 2.8 (ConfigurationOfPier project version: '1.2.1') load That's all I know for the moment. However, remember that you can install Seaside in other ways for the moment. For example you can look at the script used in the dev image before (I attach it if you want to look). However, all these configurations will be fixed soon. Thanks Mariano On Sat, Jan 16, 2010 at 5:52 PM, GermÃ¡n Arduino <garduino(a)gmail.com> wrote: > After this mail I tried to install Magritte using > "ConfigurationOfMagritte" from MetacelloRepository, but fails. > > This version of Magritte don't install with Seaside 3.0 ? > > Cheers. > GermÃ¡n. > > > 2010/1/16 GermÃ¡n Arduino <garduino(a)gmail.com>: > > Hi: > > > >> 2010/1/10 Mariano Martinez Peck <marianopeck(a)gmail.com>: > >>> Hi Folks/Beta-Testers! > >>> > >>> 6) There is no Web image this time. If you want to install Seaside > 2.8.4 > >>> evaluate: > >>> > >>> Gofer new > >>> squeaksource: 'MetacelloRepository'; > >>> package: 'ConfigurationOfSeaside28'; > >>> load. > >>> > >>> (Smalltalk at: #ConfigurationOfSeaside28) load > >>> > >>> And if you want Seaside 3.0 evaluate: > >>> > >>> Gofer new > >>> squeaksource: 'MetacelloRepository'; > >>> package: 'ConfigurationOfSeaside30'; > >>> load. > >>> > >>> (Smalltalk at: #ConfigurationOfSeaside30) loadLatestVersion > >>> > >>> However, I am not sure if this is perfectly working in Pharo. > > > > I started today, with the intention of port a new system I'm > > developing directly to Seaside 3.0. > > > > All the installation seems to works ok, I must try more yet, but a > > thing I noticed is not included > > and should by (imho) is Magritte. > > > > Just my 0.02 > > > > Cheers. > > GermÃ¡n. > > > > _______________________________________________ > 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] [ANN] Pharo News Blog

by GermÃ¡n Arduino

+1 2010/1/16 Adrian Lienhard <adi(a)netstyle.ch>: > Hi all, > > We've started a blog on the Pharo website: > > Â Â Â http://www.pharo-project.org/news > > The goal of this blog is to regularly publish interesting news about Pharo (maybe once or twice a month). This allows people who do not have the time to closely follow the mailing list to stay up to date. > > Hope you like it! > > Cheers, > Adrian > ___________________ > http://www.adrian-lienhard.ch/ > > > _______________________________________________ > 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] [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1

by GermÃ¡n Arduino

After this mail I tried to install Magritte using "ConfigurationOfMagritte" from MetacelloRepository, but fails. This version of Magritte don't install with Seaside 3.0 ? Cheers. GermÃ¡n. 2010/1/16 GermÃ¡n Arduino <garduino(a)gmail.com>: > Hi: > >> 2010/1/10 Mariano Martinez Peck <marianopeck(a)gmail.com>: >>> Hi Folks/Beta-Testers! >>> >>> 6) There is no Web image this time. If you want to install Seaside 2.8.4 >>> evaluate: >>> >>> Gofer new >>> Â Â Â squeaksource: 'MetacelloRepository'; >>> Â Â Â package: 'ConfigurationOfSeaside28'; >>> Â Â Â load. >>> >>> (Smalltalk at: #ConfigurationOfSeaside28) load >>> >>> And if you want Seaside 3.0 evaluate: >>> >>> Gofer new >>> Â Â Â squeaksource: 'MetacelloRepository'; >>> Â Â Â package: 'ConfigurationOfSeaside30'; >>> Â Â Â load. >>> >>> (Smalltalk at: #ConfigurationOfSeaside30) loadLatestVersion >>> >>> However, I am not sure if this is perfectly working in Pharo. > > I started today, with the intention of port a new system I'm > developing directly to Seaside 3.0. > > All the installation seems to works ok, I must try more yet, but a > thing I noticed is not included > and should by (imho) is Magritte. > > Just my 0.02 > > Cheers. > GermÃ¡n. >

Jan. 16, 2010

[Pharo-project] [ANN] Pharo News Blog

by Adrian Lienhard

Hi all, We've started a blog on the Pharo website: http://www.pharo-project.org/news The goal of this blog is to regularly publish interesting news about Pharo (maybe once or twice a month). This allows people who do not have the time to closely follow the mailing list to stay up to date. Hope you like it! Cheers, Adrian ___________________ http://www.adrian-lienhard.ch/

Jan. 16, 2010

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

by Nicolas Cellier

Then blockExtentsToTempsMap values are Arrays of pairs, not exactly what expected by the test... Nicolas 2010/1/16 Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com>: > Correct message is blockExtentsToTempsMap rather than blockExtentsToTempRefs > > But then, method still fails because keys does not answer a Set > anymore. Use keys asSet. > > Nicolas > > 2010/1/16 Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com>: >> The test is incompatible with new CompiledMethod trailer >> Use generate rather than generate: #(0 0 0 0) >> >> Then the method still fails because sending unimplemented >> #blockExtentsToTempRefs >> >> same for testBlockNumberingForInjectInto testTempNameAccessForInjectInto >> >> Nicolas >> >

Jan. 16, 2010