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

[Pharo-project] Athens Flake Demo

by Marcus Denker

Hi, I don't remember if Igor send the link: https://vimeo.com/45137985 This demo is very basic, demonstrating a rendering speed of Athens using Cairo backend. The scene consists from very simple elements, but on its highest zoom it renders like 3^10 visible elements per frame. The output image having transparent background by default, but blitting it to morphic world ignores it (however it works when you drag it.. a bit strange ;). Perhaps i should use different blit method for transferring bitmap to display. -- Marcus Denker -- http://marcusdenker.de

July 7, 2012

Re: [Pharo-project] OSProcess test failures in Pharo 1.4

by Sean P. DeNigris

Igor Stasenko wrote > > so someone must update it :) > Yes, but how and from where?! ;-) -- View this message in context: http://forum.world.st/OSProcess-test-failures-in-Pharo-1-4-tp4638907p463895… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

July 7, 2012

Re: [Pharo-project] OSProcess test failures in Pharo 1.4

by Igor Stasenko

On 7 July 2012 05:48, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > David T. Lewis wrote >> >> There might be some plugin version issues too. >> ... >> OSProcess accessor osppModuleVersionString ==> '4.3.3 Cog' >> > > My failing image was running on the latest Jit Cocoa Cog VM from Jenkins and > had the same outdated plugin > so someone must update it :) > -- > View this message in context: http://forum.world.st/OSProcess-test-failures-in-Pharo-1-4-tp4638907p463893… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > -- Best regards, Igor Stasenko.

July 7, 2012

Re: [Pharo-project] Cairo, VM?

by Igor Stasenko

On 6 July 2012 22:20, Hilaire Fernandes <hilaire.fernandes(a)edu.ge.ch> wrote: > Hello, > > Are there VM ready for Cairo? > > If so for which system? > RIght now for macs only.. https://ci.lille.inria.fr/pharo/view/NativeBoost/job/NB-Cog-Mac-Cocoa/29/ (well, actually linux one is *ready* too , you just need to install cairo library by yourself, and even, AFAIK, it is there by default in many linux distros on linux we don't need to care about bundling. > Hilaire > > -- > Dr. Geo -- http://www.drgeo.eu > -- Best regards, Igor Stasenko.

July 7, 2012

Re: [Pharo-project] OSProcess test failures in Pharo 1.4

by Sean P. DeNigris

David T. Lewis wrote > > There might be some plugin version issues too. > ... > OSProcess accessor osppModuleVersionString ==> '4.3.3 Cog' > My failing image was running on the latest Jit Cocoa Cog VM from Jenkins and had the same outdated plugin -- View this message in context: http://forum.world.st/OSProcess-test-failures-in-Pharo-1-4-tp4638907p463893… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

July 7, 2012

Re: [Pharo-project] OSProcess test failures in Pharo 1.4

by David T. Lewis

On Fri, Jul 06, 2012 at 04:49:35PM -0400, DeNigris Sean wrote: > 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 OSProcess and CommandShell tests run successfully on Pharo 1.4 with an interpreter VM on Linux. Many of the tests rely on #forkSqueak to set up the test conditions, and these tests may not run on VMs that cannot fully support #forkSqueak (which is tricky to do when pthreads are involved in the VM). But note that the test failures do not mean that e.g. file locking is broken, they just mean that the file locking tests will not succeed if forkSqueak is not available on the platform. There might be some plugin version issues too. The testRedirectStdOutTo failure happened only when I ran the test on a Cog VM so I suspect this may reflect an out of date plugin. Sorry I cannot check now to be sure, but the failure happens with this version: OSProcess accessor osppModuleVersionString ==> '4.3.3 Cog' And no failure with this: OSProcess accessor osppModuleVersionString ==> '4.4.11' Dave > > 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

July 7, 2012

[Pharo-project] [update 2.0] #20192

by Marcus Denker

20192 ----- Issue 6296: remove some debugging leftovers http://code.google.com/p/pharo/issues/detail?id=6296 Issue 6294: Update improvement 2 http://code.google.com/p/pharo/issues/detail?id=6294 Issue 5992: testMethodsWithUnboundGlobals http://code.google.com/p/pharo/issues/detail?id=5992 -- Marcus Denker -- http://marcusdenker.de

July 6, 2012

Re: [Pharo-project] Bogus/Annoying #logCr's

by Marcus Denker

On Jul 6, 2012, at 9:10 PM, Sven Van Caekenberghe wrote: > Probably leftovers from debugging: > > AbstractNautilusUI>>mcWorkingCopyCreated: > | package rpackage mcPackage | > 'Passed there' logCr. > window ifNil: [^ self ]. > window isDisplayed ifFalse: [ ^ self ]. > > ... > > RPackageOrganizer>>systemClassRemovedActionFrom: > "A class has been removed, we should update the package adequately." > > | class className rPackage categoryName | > 'herrrrrre ' logCr. > class := ann removedClass. > > â¦ > http://code.google.com/p/pharo/issues/detail?id=6296 -- Marcus Denker -- http://marcusdenker.de

July 6, 2012

Re: [Pharo-project] Google Code labels/templates

by Marcus Denker

On Jul 6, 2012, at 7:35 PM, Sean P. DeNigris wrote: > > Marcus Denker-4 wrote >> >>> So, now that I said all that, it seems the most powerful/flexible >>> approach >>> would be to leave the "nautilus" tag, remove the leading "Type-" from >>> "Type-[Jenkins|Spec|Seed]", and then to make templates for >>> Jenkins/Spec/Seed >>> like the one for Nautilus. >>> >>> What do you think? >> >> honestly I don't care... there is so much to do that I can't even think >> about details like >> this. >> > > If you give me access, I will take care of it. These clarifications will > avoid more, possibly invalid, issues from cluttering up our minds. That is a great idea! I will add you as and admin. Marcus -- Marcus Denker -- http://marcusdenker.de

July 6, 2012

[Pharo-project] OSProcess test failures in Pharo 1.4

by DeNigris Sean

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

July 6, 2012