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

[Pharo-project] [update 2.0] #20195
by Marcus Denker July 8, 2012

July 8, 2012

20195 ----- Issue 6259: DataStream is still there http://code.google.com/p/pharo/issues/detail?id=6259 Issue 4095: Suggestion: rename some methods for consistency (just example methods, no API changes) http://code.google.com/p/pharo/issues/detail?id=4095 -- Marcus Denker -- http://marcusdenker.de

1 0

[Pharo-project] StartupPreferences
by Sean P. DeNigris July 8, 2012

July 8, 2012

Mariano, Can any of the script lookup logic from 2.0 be ported to 1.4? StartupPreferences doesn't seem very useful if only the image folder is checked, given that the initial use case was for working in many fresh images. - S -- View this message in context: http://forum.world.st/StartupPreferences-tp4639058.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

2 2

[Pharo-project] On the frontpage of news.ycombinator.com
by Marcus Denker July 8, 2012

July 8, 2012

http://news.ycombinator.com/ Sunday morning... but nevertheless :-) Marcus -- Marcus Denker -- http://marcusdenker.de

3 2

[Pharo-project] [update 2.0] #20194
by Marcus Denker July 8, 2012

July 8, 2012

20194 ----- Issue 6304: [BUG]: Completion DNU in Inspector/Object Explorer for 2.0 http://code.google.com/p/pharo/issues/detail?id=6304 Issue 6301: Halts in image http://code.google.com/p/pharo/issues/detail?id=6301 Issue 6274: another step to remove StringHolder hierarchy element http://code.google.com/p/pharo/issues/detail?id=6274 -- Marcus Denker -- http://marcusdenker.de

1 0

[Pharo-project] ConfigurationOfPharoVM
by Sean P. DeNigris July 8, 2012

July 8, 2012

I noticed the versions vary between x.x.x and x.x-x and that some of the versions import baselines and others import other versions. I've never seen it done like that... what's the intention? e.g. "Baseline with dot imported by version with dash" version145: spec <version: '1.4-5' imports: #('1.4.1-baseline')> "version importing another version" version143: spec <version: '1.4-3' imports: #('1.4-2')> Cheers, Sean -- View this message in context: http://forum.world.st/ConfigurationOfPharoVM-tp4639007.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

4 7

[Pharo-project] Bug fix to review for Summer Release
by Sean P. DeNigris July 8, 2012

July 8, 2012

Please someone take <<5 min to review this fix so we can avoid ugly DNUs in our release... Issue 6303: [BUG]: Completion DNU in Inspector/Object Explorer for 1.4 http://code.google.com/p/pharo/issues/detail?id=6303 Status: FixReviewNeeded To reproduce: 1. DoIt: "Morph new explore" 2. In the bottom pane of the explorer, type "bounds s" You will get a DNU #guessTypeForName: Fix in inbox: Name: SLICE-Issue-6303-BUG-Completion-DNU-in-InspectorObject-Explorer-for-14-SeanDeNigris.1 Implement very basic #guessTypeForName: in ObjectExplorer and Inspector to avoid DNUs during code completion -- View this message in context: http://forum.world.st/Bug-fix-to-review-for-Summer-Release-tp4639053.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

1 1

[Pharo-project] OSProcess test failures in Pharo 1.4
by DeNigris Sean July 8, 2012

July 8, 2012

The few that I checked had to do with stdout being closed... OSProcess-dtl.70 Mac Lion Also tried running with vm from command line cc/ David Lewis UnixProcessAccessorTestCase>>#testRedirectStdOutTo UnixProcessTestCase>>#testCatAFile UnixProcessTestCase>>#testClassForkHeadlessSqueakAndDo UnixProcessTestCase>>#testClassForkHeadlessSqueakAndDoThenQuit UnixProcessTestCase>>#testClassForkSqueak UnixProcessTestCase>>#testClassForkSqueakAndDo UnixProcessTestCase>>#testClassForkSqueakAndDoThenQuit UnixProcessTestCase>>#testForkHeadlessSqueakAndDo UnixProcessTestCase>>#testForkHeadlessSqueakAndDoThenQuit UnixProcessTestCase>>#testForkSqueak UnixProcessTestCase>>#testForkSqueakAndDo UnixProcessTestCase>>#testForkSqueakAndDoThenQuit UnixProcessTestCase>>#testHeadlessChild UnixProcessTestCase>>#testRunCommand UnixProcessTestCase>>#testSpawnTenHeadlessChildren UnixProcessUnixFileLockingTestCase>>#testCooperatingProcesses01 UnixProcessUnixFileLockingTestCase>>#testCooperatingProcesses02 UnixProcessUnixFileLockingTestCase>>#testCooperatingProcesses03 UnixProcessUnixFileLockingTestCase>>#testCooperatingProcesses04 UnixProcessUnixFileLockingTestCase>>#testCooperatingProcesses05 UnixProcessUnixFileLockingTestCase>>#testFailFileLockOnLockedFile UnixProcessUnixFileLockingTestCase>>#testFailLockOnLockedOverlappedRegion UnixProcessUnixFileLockingTestCase>>#testFailLockOnLockedRegion UnixProcessUnixFileLockingTestCase>>#testFailLockOnLockedSupersetRegion UnixProcessUnixFileLockingTestCase>>#testFailRegionLockOnLockedFile UnixProcessUnixFileLockingTestCase>>#testLockEntireFileForWrite01 UnixProcessUnixFileLockingTestCase>>#testLockEntireFileForWrite02 UnixProcessUnixFileLockingTestCase>>#testLockEntireFileForWrite03 UnixProcessUnixFileLockingTestCase>>#testLockEntireFileForWrite04 UnixProcessUnixFileLockingTestCase>>#testLockEntireFileForWrite05 UnixProcessUnixFileLockingTestCase>>#testLockEntireFileForWrite06 UnixProcessUnixFileLockingTestCase>>#testLockRegionForRead01 UnixProcessUnixFileLockingTestCase>>#testLockRegionForRead02 UnixProcessUnixFileLockingTestCase>>#testLockRegionForWrite01 UnixProcessUnixFileLockingTestCase>>#testLockRegionForWrite02 UnixProcessUnixFileLockingTestCase>>#testLockRegionForWrite03 UnixProcessUnixFileLockingTestCase>>#testLockRegionForWrite04 UnixProcessUnixFileLockingTestCase>>#testLockRegionForWrite05 UnixProcessUnixFileLockingTestCase>>#testLockRegionForWrite06 UnixProcessUnixFileLockingTestCase>>#testLockRegionForWrite07 UnixProcessUnixFileLockingTestCase>>#testLockRegionForWrite08 UnixProcessUnixFileLockingTestCase>>#testNoFailLockOnAdjacentLockedRegions UnixProcessUnixFileLockingTestCase>>#testNoFailLockOnDifferentLockedRegion UnixProcessWin32FileLockingTestCase>>#testCooperatingProcesses01 UnixProcessWin32FileLockingTestCase>>#testCooperatingProcesses02 UnixProcessWin32FileLockingTestCase>>#testCooperatingProcesses03 UnixProcessWin32FileLockingTestCase>>#testCooperatingProcesses04 UnixProcessWin32FileLockingTestCase>>#testCooperatingProcesses05 UnixProcessWin32FileLockingTestCase>>#testFailFileLockOnLockedFile UnixProcessWin32FileLockingTestCase>>#testFailLockOnLockedOverlappedRegion UnixProcessWin32FileLockingTestCase>>#testFailLockOnLockedRegion UnixProcessWin32FileLockingTestCase>>#testFailLockOnLockedSupersetRegion UnixProcessWin32FileLockingTestCase>>#testFailRegionLockOnLockedFile UnixProcessWin32FileLockingTestCase>>#testLockEntireFileForWrite01 UnixProcessWin32FileLockingTestCase>>#testLockEntireFileForWrite02 UnixProcessWin32FileLockingTestCase>>#testLockEntireFileForWrite03 UnixProcessWin32FileLockingTestCase>>#testLockEntireFileForWrite04 UnixProcessWin32FileLockingTestCase>>#testLockEntireFileForWrite05 UnixProcessWin32FileLockingTestCase>>#testLockEntireFileForWrite06 UnixProcessWin32FileLockingTestCase>>#testLockRegionForRead01 UnixProcessWin32FileLockingTestCase>>#testLockRegionForRead02 UnixProcessWin32FileLockingTestCase>>#testLockRegionForWrite01 UnixProcessWin32FileLockingTestCase>>#testLockRegionForWrite02 UnixProcessWin32FileLockingTestCase>>#testLockRegionForWrite03 UnixProcessWin32FileLockingTestCase>>#testLockRegionForWrite04 UnixProcessWin32FileLockingTestCase>>#testLockRegionForWrite05 UnixProcessWin32FileLockingTestCase>>#testLockRegionForWrite06 UnixProcessWin32FileLockingTestCase>>#testLockRegionForWrite07 UnixProcessWin32FileLockingTestCase>>#testLockRegionForWrite08 UnixProcessWin32FileLockingTestCase>>#testNoFailLockOnAdjacentLockedRegions UnixProcessWin32FileLockingTestCase>>#testNoFailLockOnDifferentLockedRegion

5 9

[Pharo-project] Issue with certificate on ci.lille.inria.fr preventing newImage.sh to work for iOSVM build
by phil＠highoctane.be July 7, 2012

July 7, 2012

I was recording a screencast to show how to create the iOS VM but there was an issue. I did a git clone git://gitorious.org/~estebanlm/cogvm/cog-osx.git Then, inside cog-osx/image, I did a ./newImage.sh and got PhilMac:image philippeback$ ./newImage.sh LOADING PREBUILT IMAGE https://ci.lille.inria.fr/pharo/job/Cog%20Git%20Tracker/lastSuccessfulBuild… --2012-07-07 21:41:12-- https://ci.lille.inria.fr/pharo/job/Cog%20Git%20Tracker/lastSuccessfulBuild… RÃ©solution de ci.lille.inria.fr (ci.lille.inria.fr)... 193.49.213.180 Connexion vers ci.lille.inria.fr (ci.lille.inria.fr )|193.49.213.180|:443...connectÃ©. ERREUR : le certificat de Â«ci.lille.inria.frÂ» n'est pas digne de confiance. ERREUR : le certificat Â«ci.lille.inria.frÂ» n'est pas d'un Ã©metteur connu. FETCHING FRESH IMAGE https://ci.lille.inria.fr/pharo/job/Pharo%201.4/lastSuccessfulBuild/artifac… --2012-07-07 21:41:12-- https://ci.lille.inria.fr/pharo/job/Pharo%201.4/lastSuccessfulBuild/artifac… RÃ©solution de ci.lille.inria.fr (ci.lille.inria.fr)... 193.49.213.180 Connexion vers ci.lille.inria.fr (ci.lille.inria.fr )|193.49.213.180|:443...connectÃ©. ERREUR : le certificat de Â«ci.lille.inria.frÂ» n'est pas digne de confiance. ERREUR : le certificat Â«ci.lille.inria.frÂ» n'est pas d'un Ã©metteur connu. UNZIPPING /Users/philippeback/Documents/Smalltalk/2-MyWorkspaces/workspaceVMiOS/cog-osx/image/image.zip Archive: image.zip End-of-central-directory signature not found. Either this file is not a zipfile, or it constitutes one disk of a multi-part archive. In the latter case the central directory and zipfile comment will be found on the last disk(s) of this archive. unzip: cannot find zipfile directory in one of image.zip or image.zip.zip, and cannot find image.zip.ZIP, period. PhilMac:image philippeback$ There is something wrong with the certificate over there. Could this be fixed? TIA -- Philippe Back

1 0

[Pharo-project] Trello board for 1.4 - dead?
by phil＠highoctane.be July 7, 2012

July 7, 2012

I was looking at the Trello board for 1.4 and it appears dead. Is it the case? (to remove it from the symbaloo desktop) Phil

2 1

[Pharo-project] getting ready to summer release of 1.4
by Esteban Lorenzano July 7, 2012

July 7, 2012

Hi, Today I finish the changes needed to release next update version of 1.4. Yes, there are still bugs around. Yes, there are still things that can be better. But the purpose of this release is to provide some important fixes (integrated since three months to now) and add enhancements due to community feedback since 1.4 was released. Most important changes are the incorporation of OB, Spotlight and backport of 2.0 Configurations Browser. Can you download and test, so I can prepare an official release next week? Best, Esteban

7 18