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

Re: [Pharo-project] Issue 3581 in pharo: [Failing test] 1.1.1 Full: MethodWrappers.Tests.ObjectAsOneTimeMethodWrapperTest.testInstallOnClassCategory

by pharo＠googlecode.com

Updates: Labels: -Milestone-1.1.2 Milestone-1.1.2-DevImage Comment #2 on issue 3581 by marcus.d...(a)gmail.com: [Failing test] 1.1.1 Full: MethodWrappers.Tests.ObjectAsOneTimeMethodWrapperTest.testInstallOnClassCategory http://code.google.com/p/pharo/issues/detail?id=3581 (No comment was entered for this change.)

Jan. 28, 2011

[Pharo-project] Accessing external resources in a cross-platform way

by HernÃ¡n Morales Durand

Let's say you want to resolve paths in a cross platform way Binaries @ 'MyExec' Libraries @ 'MyLib' SystemLibraries @ 'SystemLib' etc. then Binaries is In Windows: #( 'C:\Program Files\' 'C:\Archivos de Programa\' ...) " and all standard locations including translations " In UNIX: #('/usr/bin/' '/usr/local/bin' ....) " and all standard locations " etc Now you may say it is necessary to scan all directories to find MyExec, yes but you may then save that location myBinaryLocation := Binaries @ 'MyExec'. so you scan for it just once. What do you think? it is already implemented anywhere? If not what package do you think is more suitable or prepared for implementing it? Cheers, -- HernÃ¡n Morales Information Technology Manager, Institute of Veterinary Genetics. National Scientific and Technical Research Council (CONICET). La Plata (1900), Buenos Aires, Argentina. Telephone: +54 (0221) 421-1799. Internal: 422 Fax: 425-7980 or 421-1799.

Jan. 28, 2011

Re: [Pharo-project] Issue 3575 in pharo: [Failing Tests] Package Monticello leaves Obsolete class after tests

by pharo＠googlecode.com

Updates: Labels: -Milestone-1.1.2 Milestone-1.1.2-DevImage Comment #4 on issue 3575 by marcus.d...(a)gmail.com: [Failing Tests] Package Monticello leaves Obsolete class after tests http://code.google.com/p/pharo/issues/detail?id=3575 (No comment was entered for this change.)

Jan. 28, 2011

Re: [Pharo-project] Issue 3469 in pharo: [Failing Test] ShoutTests.Parsing.SHParserST80Test.testCollectionHierarchy

by pharo＠googlecode.com

Updates: Labels: -Milestone-1.1.2 Milestone-1.1.2-DevImage Comment #5 on issue 3469 by marcus.d...(a)gmail.com: [Failing Test] ShoutTests.Parsing.SHParserST80Test.testCollectionHierarchy http://code.google.com/p/pharo/issues/detail?id=3469 (No comment was entered for this change.)

Jan. 28, 2011

Re: [Pharo-project] About FileSystem (probably not for 1.3)

by StÃ©phane Ducasse

I merged them also in PharoTaskForces On Jan 28, 2011, at 12:02 AM, Dale Henrichs wrote: > On 01/27/2011 03:00 PM, Lukas Renggli wrote: >>> I started to merge some of your changes to FS. >> >> I already merged most of the changes of Max into the main code. >> >>> Now I was wondering about this one: >>> ***for my work on GitFS I needed a resumable exception (alternatively an ifPresent block would have done the trick but that would have ment more meddling with Filesystem) to delete existing files when copying. The following changes are a result of introducing this exception to the copy methods. >>> *added class FSFileExistsResumbale and its superclass FSFilesystemException to support the changes to the copy methods >>> *#copy:to: signals FSFileExistsResumbale instead of FSFileExists >>> *FSCopyVisitor>>copyDirectory uses #ensureDirectory instead of #createDirectory >>> *needed to change FSFilesystemTest>>testCopyDestExists to expect FSFileExistsResumable >>> *FSReference>>basicCopyTo: signals FSFileExistsResumable instead of FSFileExists >>> >>> Could you explain us a bit more? >> >> This is not something that should go into the main code. If I remember >> correctly this was a quick hack to avoid some problems in GitFS. >> >> Lukas >> > > At the time I ported FileSystem to GemStone (4 months ago?), I started with the packages in Lukas' repository... > > Dale >

Jan. 28, 2011

Re: [Pharo-project] Issue 3469 in pharo: [Failing Test] ShoutTests.Parsing.SHParserST80Test.testCollectionHierarchy

by pharo＠googlecode.com

Updates: Cc: -renggli Labels: -Type-OB Type-Shout Comment #4 on issue 3469 by marcus.d...(a)gmail.com: [Failing Test] ShoutTests.Parsing.SHParserST80Test.testCollectionHierarchy http://code.google.com/p/pharo/issues/detail?id=3469 ups, wrong bugreport. Change to Package Shout

Jan. 28, 2011

Re: [Pharo-project] Issue 3601 in pharo: Recommended Seaside version in Pharo-1.2 outdated

by pharo＠googlecode.com

Updates: Status: Closed Comment #4 on issue 3601 by marcus.d...(a)gmail.com: Recommended Seaside version in Pharo-1.2 outdated http://code.google.com/p/pharo/issues/detail?id=3601 in build #99

Jan. 28, 2011

Re: [Pharo-project] Issue 3470 in pharo: [Failing Tests] OBKeyBindingsTest

by pharo＠googlecode.com

Updates: Labels: Type-OB Comment #4 on issue 3470 by marcus.d...(a)gmail.com: [Failing Tests] OBKeyBindingsTest http://code.google.com/p/pharo/issues/detail?id=3470 (No comment was entered for this change.)

Jan. 28, 2011

Re: [Pharo-project] Issue 3469 in pharo: [Failing Test] ShoutTests.Parsing.SHParserST80Test.testCollectionHierarchy

by pharo＠googlecode.com

Updates: Cc: renggli Labels: Type-OB Comment #3 on issue 3469 by marcus.d...(a)gmail.com: [Failing Test] ShoutTests.Parsing.SHParserST80Test.testCollectionHierarchy http://code.google.com/p/pharo/issues/detail?id=3469 So, this is a change to the package AutomaticMethodCategorizerOB Where do we need to merge this?

Jan. 28, 2011

Re: [Pharo-project] Issue 3583 in pharo: Shout should only be active in code panes

by pharo＠googlecode.com

Updates: Labels: -Type-Patch -Milestone-1.2 -Milestone-1.3 Milestone-1.2-DevImage Comment #13 on issue 3583 by marcus.d...(a)gmail.com: Shout should only be active in code panes http://code.google.com/p/pharo/issues/detail?id=3583 So I move this to 1.2Dev

Jan. 28, 2011