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

[Pharo-project] [update 1.2] #12028

by StÃ©phane Ducasse

12028 ----- - Issue 2615: Use overflow rows for ToolBuilder button panels. Thanks Gary! - Issue 2616: Use overflow rows for Debugger custom buttons. Thanks Gary! - Issue 2624: Much faster Dictionary>>unreferencedKeys. Thanks Eliot

July 2, 2010

[Pharo-project] Problem with number parsing in Shout...help needed!

by Mariano Martinez Peck

If you load Shout-lr.84 and ShoutTests-tween.9 from http://www.squeaksource.com/shout and run the testNumbers it will in: s := 'x 16r-d'. types := self tokenTypesIn: s. tokens := self tokensIn: s. self assert: types = #(patternUnary number unary). self assert: tokens = #('x' '16r-' 'd'). because types is #(#patternUnary #number) and in addition, tokens is #('x' '16r-d') I have no idea about this. Does someone know how to fix it? Thanks mariano

July 2, 2010

Re: [Pharo-project] [Esug-list] [vwnc] ESUG 2010 registration dead-line is approaching!

by Serge Stinckwich

Hi Joaquim, There is no information on the FB event that is not on the ESUG website. This is just a convenient way to do some some buzz. Thank you. Le 2 juil. 2010 Ã 17:49, "jtuchel(a)objektfabrik.de" <jtuchel(a)objektfabrik.de> a Ã©crit : > Just a side note: > >> http://www.esug.org/Conferences/2010 > > If I visit the conference page, there is a link to Conference news on Facebook > This is only accessible for registered Facebook users. > I think it's not a good idea to be a closed circle. > > Joachim > > > > Noury Bouraqadi <bouraqadi(a)gmail.com> hat am 2. Juli 2010 um 00:32 geschrieben > >> Dear Smalltalkers, >> >> The dead-line for registration at early bird fees is approaching (one month to >> go). >> So, hurry up and register on our new seaside-based server. >> http://registration.esug.org/ >> This server comes with new features. >> You can now do a group registration and make a single payment. >> Also, we have reduction tickets (typically for Golden and Platinum sponsors). >> >> The ESUG 2010 conference program is about to be ready, and it is as promising >> as was for the previous editions of the conference. >> Checkout the preliminary schedule is already on the web, >> http://www.esug.org/Conferences/2010 >> >> See you in Barcelona, >> Noury >> ESUG treasurer >> >> >> _______________________________________________ >> vwnc mailing list >> vwnc(a)cs.uiuc.edu >> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc > > -- > ------------------------------------------------------------------- > Objektfabrik Joachim Tuchel mailto:jtuchel@objektfabrik.de > Fliederweg 1 http://www.objektfabrik.de > D-71640 Ludwigsburg > Telefon: +49 7141 56 10 86 0 Fax: +49 7141 56 10 86 1 > > _______________________________________________ > Esug-list mailing list > Esug-list(a)lists.esug.org > http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org

July 2, 2010

[Pharo-project] BogusSnapshotResource >> restoreMethod: ref using deprecated and: and:

by Mariano Martinez Peck

Hi Lukas. BogusSnapshotResource >> restoreMethod: ref is using the and: and: that was just deprecated in Pharo 1.1. Just replacing it by this I think should work: restoreMethod: ref | definition | definition := snapshot definitions detect: [ :ea | ea isMethodDefinition and: [ (ea className = ref classSymbol ) and: [ ea selector = ref methodSymbol ] ]] ifNone: [ ^ self removeMethod: ref ]. definition load cheers mariano

July 2, 2010

[Pharo-project] [ANN 1.1] pre-built 1.1 Core RC4

by Marcus Denker

https://gforge.inria.fr/frs/download.php/27242/PharoCore-1.1-11409-rc4.zip

July 2, 2010

[Pharo-project] [update 1.1] #11409

by Marcus Denker

(it is getting *far* too hot here...) 11409 ----- RC4

July 2, 2010

Re: [Pharo-project] [BetaTesting] [ANN] Pharo-1.1-11406-rc3dev10.07.1

by Mariano Martinez Peck

Thanks Andrian. I have just fixed all Nile tests (see the other thread), and there were some new PharoCore for 1.1 with more green tests...so we are getting near. Soon I will create we will create an rc4. Cheers Mariano On Fri, Jul 2, 2010 at 12:09 PM, Adrian Lienhard <adi(a)netstyle.ch> wrote: > Thanks, Mariano! > > Here is the result of running all the tests: 15 failures, 76 errors > Failures: > NSFileStreamTest>>#testFlush21 > ObjectAsOneTimeMethodWrapperTest>>#testInstallOnClassCategory > NSFileStreamTest>>#testPeek01 > ReleaseTest>>#testUndeclared > SHParserST80Test>>#testNumbers > NSMultiByteBinaryOrTextStreamTest>>#testFileIn > NSFileStreamTest>>#testReadWriteText > NSMultiByteBinaryOrTextStreamTest>>#testFileOut > WeakRegistryTest>>#testFinalization > NSFileStreamTest>>#testNext01 > NSFileStreamTest>>#testReadWriteBinary > NSFileStreamTest>>#testDo01 > NSFileStreamTest>>#testSkip01 > ObjectFinalizerTests>>#testFinalizationOfMultipleResources > MCInitializationTest>>#testWorkingCopy > > Errors: > NSRWBinaryOrTextStreamTest>>#testFileIn > NSRWBinaryOrTextStreamTest>>#testFileInExpresion > NSRWBinaryOrTextStreamTest>>#testFileOut > NSRWBinaryOrTextStreamTest>>#testFileOutFileIn > NSCompressedSourceStreamTest>>#testAtEnd01 > NSCompressedSourceStreamTest>>#testAtEnd11 > NSCompressedSourceStreamTest>>#testAtStart11 > NSCompressedSourceStreamTest>>#testBack11 > NSCompressedSourceStreamTest>>#testBack61 > NSCompressedSourceStreamTest>>#testDo01 > NSCompressedSourceStreamTest>>#testFlush21 > NSCompressedSourceStreamTest>>#testGlobal > NSCompressedSourceStreamTest>>#testIsEmpty11 > NSCompressedSourceStreamTest>>#testNext01 > NSCompressedSourceStreamTest>>#testNextInto01 > NSCompressedSourceStreamTest>>#testNextMatchFor01 > NSCompressedSourceStreamTest>>#testNextPutAllAppending21 > NSCompressedSourceStreamTest>>#testNextPutAllAppendingASet21 > NSCompressedSourceStreamTest>>#testNextPutAllReplacing21 > NSCompressedSourceStreamTest>>#testNextPutAllReplacingASet21 > NSCompressedSourceStreamTest>>#testNextPutAppending21 > NSCompressedSourceStreamTest>>#testNextPutReplacing21 > NSCompressedSourceStreamTest>>#testNexts01 > NSCompressedSourceStreamTest>>#testPeek01 > NSCompressedSourceStreamTest>>#testPeekFor01 > NSCompressedSourceStreamTest>>#testPosition11 > NSCompressedSourceStreamTest>>#testReset11 > NSCompressedSourceStreamTest>>#testSetPosition11 > NSCompressedSourceStreamTest>>#testSetToEnd11 > NSCompressedSourceStreamTest>>#testSize11 > NSCompressedSourceStreamTest>>#testSkip01 > NSCompressedSourceStreamTest>>#testSkip61 > NSCompressedSourceStreamTest>>#testUpToElementSatisfying01 > NSCompressedSourceStreamTest>>#testWriteBack71 > WeakSetInspectorTest>>#testSymbolTableM6812 > NSMCPseudoFileStreamTest>>#testFileIn > NSMCPseudoFileStreamTest>>#testFileInExpresion > NSMCPseudoFileStreamTest>>#testFileOut > NSMCPseudoFileStreamTest>>#testFileOutFileIn > NSSmartRefStreamTest>>#testGlobal > NSMailAddressTokenizerTest>>#testNextElements > NSMultiByteBinaryOrTextStreamTest>>#testFileInExpresion > NSPipeTest>>#testScenario1 > NSFileStreamTest>>#testAtEnd01 > NSFileStreamTest>>#testAtEnd11 > NSFileStreamTest>>#testAtStart11 > NSFileStreamTest>>#testBack11 > NSFileStreamTest>>#testBack61 > NSFileStreamTest>>#testIsBinaryOnBinaryStream > NSFileStreamTest>>#testIsBinaryOnNonBinaryStream > NSFileStreamTest>>#testIsClosedTest > NSFileStreamTest>>#testIsEmpty11 > NSFileStreamTest>>#testNextInto01 > NSFileStreamTest>>#testNextMatchFor01 > NSFileStreamTest>>#testNextPutAllAppending21 > NSFileStreamTest>>#testNextPutAllAppendingASet21 > NSFileStreamTest>>#testNextPutAllReplacing21 > NSFileStreamTest>>#testNextPutAllReplacingASet21 > NSFileStreamTest>>#testNextPutAppending21 > NSFileStreamTest>>#testNextPutReplacing21 > NSFileStreamTest>>#testNexts01 > NSFileStreamTest>>#testPeekFor01 > NSFileStreamTest>>#testPosition11 > NSFileStreamTest>>#testReadWriteBinary2 > NSFileStreamTest>>#testReadWriteText2 > NSFileStreamTest>>#testReset11 > NSFileStreamTest>>#testSetPosition11 > NSFileStreamTest>>#testSetToEnd11 > NSFileStreamTest>>#testSimpleWriteData > NSFileStreamTest>>#testSize11 > NSFileStreamTest>>#testSkip61 > NSFileStreamTest>>#testTruncateBinary > NSFileStreamTest>>#testTruncateText > NSFileStreamTest>>#testUpToElementSatisfying01 > NSFileStreamTest>>#testWriteBack71 > NSCollectionAdditionsTest>>#testMakeRoomForSmallCollections > > > Nile is broken because it sends #isFinalizationSupported, which does not > exist anymore. > > Adrian > > On Jul 2, 2010, at 00:29 , Mariano Martinez Peck wrote: > > > Hi folks. I am glad to announce the Pharo 1.1 RC3. It has not too much > > changes in compare to RC2. The main change is the menu structure. I also > > updated to newest version of external packages. > > > > Here is the image: > > > > > https://gforge.inria.fr/frs/download.php/27241/Pharo-1.1-11406-rc3dev10.07.… > > > > We would really appreaciate feedback and help to fix the failing tests. > > > > Cheers > > > > Mariano > > _______________________________________________ > > 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 2, 2010

[Pharo-project] Fixed Nile for Pharo 1.1 [WAS] Re: Found senders of #isSystemDefined in Nile

by Mariano Martinez Peck

Ok....I finally take an hour and fix all the Nile tests in Pharo 1.1. They are now all green. While doing this, I have removed all (or all I saw) from uniClasses in Nile. It would be very cool if someone from Nile can check my latests commits in the repository. If you want to load it: Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfNile'; load. and then (ConfigurationOfNile project version: '1.1') load: 'Core Tests' Cheers Mariano On Sat, May 22, 2010 at 6:37 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > Yes we should just update Nile > This is a clear example of the fact that since we do not record refactoring > external packages can easily degrade > > > > On May 22, 2010, at 6:26 PM, Alexandre Bergel wrote: > > > I have the feeling that all these uniClasses are stone age. All traces > should be removed. > > > > Cheers, > > Alexandre > > > > > > On 22 May 2010, at 13:19, Mariano Abel Coca wrote: > > > >> Hi, > >> > >> I've found a few senders of #isSystemDefined when trying to run the > pharo dev test suite, and I don't know what is the expected behavior. > >> > >> I've read in: > http://www.mail-archive.com/pharo-project@lists.gforge.inria.fr/msg12075.ht… the idea is to remove the message and all it's senders, but I don't > know why is used here in Nile. > >> > >> The senders are in NSSmartRefStream, inside of #uniClassInstVarsRefs:, > #uniClasesDo: and #beginInstance:size: > >> > >> Any hint on this will be appreciated. > >> > >> Cheers, > >> > >> Mariano. > >> _______________________________________________ > >> 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 > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

July 2, 2010

Re: [Pharo-project] fix for blocks restart in debugger

by Henrik Johansen

I fixed privRefresh some time ago so block restart works, asContext was not part of that though. Should also take a second look at privRefresh to see if Eliot's made additional changes. Cheers, Henry On Jul 2, 2010, at 2:06 39PM, StÃ©phane Ducasse wrote: > hi eliot > > do you know if such changes should be pushed into pharo? > > http://code.google.com/p/pharo/issues/detail?id=2617 > > Stef > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 2, 2010

[Pharo-project] fix for blocks restart in debugger

by StÃ©phane Ducasse

hi eliot do you know if such changes should be pushed into pharo? http://code.google.com/p/pharo/issues/detail?id=2617 Stef

July 2, 2010