September 2013 - Pharo-dev - lists.pharo.org

[update 3.0] #30409

by Esteban Lorenzano

30409 ----- 11544 Memory leak when using weak announcements with blocks https://pharo.fogbugz.com/f/cases/11544 (step 2/3... yes, inflation!) Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/Collections-Weak-EstebanLoren…

Sept. 19, 2013

Re: [Pharo-dev] [OT] Pharo lighthouse wallpaper

by btc＠openinworld.com

Torsten Bergmann wrote: > http://wallpapers5.com/images/wallpapers/71156968/Photography/Cape-Hatteras… > > According to site Image is for personal, non commercial use > > > Here are some available for commercial use... https://www.google.com/search?as_st=y&tbm=isch&as_q=Cape+Hatteras+Lighthous… <https://www.google.com/search?as_st=y&tbm=isch&as_q=Cape+Hatteras+Lighthous…> or... http://www.google.com/advanced_image_search + all these words: Cape Hatteras Lighthouse + usage rights: free to sue or share, even commercially

Sept. 19, 2013

[update 3.0] #30408

by Esteban Lorenzano

Sept. 19, 2013

[regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2.1-Validation/label=ma… 169 regressions found. Gofer.Tests.GoferOperationTest.testLocalChanges Gofer.Tests.GoferOperationTest.testReinitialize Gofer.Tests.GoferOperationTest.testRemoteChanges RPackage.SystemIntegration.RPackageCategorySynchronisationTest.testAddCategoryCreatesPackage RPackage.SystemIntegration.RPackageCategorySynchronisationTest.testRenameCategoryAlsoRenameAllExtensionProtocols RPackage.SystemIntegration.RPackageCategorySynchronisationTest.testAddCategoryIsAlreadyAPackageDoesNotCreatePackage RPackage.SystemIntegration.RPackageCategorySynchronisationTest.testRenameCategoryChangeTheNameOfThePackage RPackage.SystemIntegration.RPackageCategorySynchronisationTest.testRenameUnknownCategoryCreatesNewRPackage RPackage.SystemIntegration.RPackageCategorySynchronisationTest.testRenameCategoryUpdateTheOrganizer RPackage.SystemIntegration.RPackageClassesSynchronisationTest.testRecategorizeClassWithMetaClassMethodsRegisterAllClassMethodsInTheNewPackage RPackage.SystemIntegration.RPackageClassesSynchronisationTest.testReorganizeClassByRenamingExtensionCategoryToClassicCategoryMoveMethodsFromExtendingPackageToParentPackage RPackage.SystemIntegration.RPackageClassesSynchronisationTest.testRecategorizeClassRaisesClassRepackagedEvent RPackage.SystemIntegration.RPackageClassesSynchronisationTest.testRecategorizeClassWithUnexistingPackageNameRegisterTheClassInANewPackage RPackage.SystemIntegration.RPackageClassesSynchronisationTest.testRenameClassUpdateClassDefinedSelectorsInTheParentPackage RPackage.SystemIntegration.RPackageClassesSynchronisationTest.testRenameClassUpdateOrganizerClassExtendingPackagesMapping RPackage.SystemIntegration.RPackageClassesSynchronisationTest.testReorganizeClassByAddingNewProtocolDoesNothing RPackage.SystemIntegration.RPackageClassesSynchronisationTest.testRemoveClassUpdateTheOrganizerMappings RPackage.SystemIntegration.RPackageClassesSynchronisationTest.testRenameClassUpdateOrganizerClassPackageMapping RPackage.SystemIntegration.RPackageClassesSynchronisationTest.testRecategorizeClassRegisterTheClassInTheExactMatchPackage RPackage.SystemIntegration.RPackageClassesSynchronisationTest.testRemoveClassUnregisterTheClassExtensionMethodsFromTheCorrespondingPackage ...

Sept. 19, 2013

[regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2.1-Validation/label=wi… 170 regressions found. Gofer.Tests.GoferOperationTest.testLocalChanges Gofer.Tests.GoferOperationTest.testReinitialize Gofer.Tests.GoferOperationTest.testRemoteChanges RPackage.SystemIntegration.RPackageCategorySynchronisationTest.testAddCategoryCreatesPackage RPackage.SystemIntegration.RPackageCategorySynchronisationTest.testRenameCategoryAlsoRenameAllExtensionProtocols RPackage.SystemIntegration.RPackageCategorySynchronisationTest.testAddCategoryIsAlreadyAPackageDoesNotCreatePackage RPackage.SystemIntegration.RPackageCategorySynchronisationTest.testRenameCategoryChangeTheNameOfThePackage RPackage.SystemIntegration.RPackageCategorySynchronisationTest.testRenameUnknownCategoryCreatesNewRPackage RPackage.SystemIntegration.RPackageCategorySynchronisationTest.testRenameCategoryUpdateTheOrganizer RPackage.SystemIntegration.RPackageClassesSynchronisationTest.testRecategorizeClassWithMetaClassMethodsRegisterAllClassMethodsInTheNewPackage RPackage.SystemIntegration.RPackageClassesSynchronisationTest.testReorganizeClassByRenamingExtensionCategoryToClassicCategoryMoveMethodsFromExtendingPackageToParentPackage RPackage.SystemIntegration.RPackageClassesSynchronisationTest.testRecategorizeClassRaisesClassRepackagedEvent RPackage.SystemIntegration.RPackageClassesSynchronisationTest.testRecategorizeClassWithUnexistingPackageNameRegisterTheClassInANewPackage RPackage.SystemIntegration.RPackageClassesSynchronisationTest.testRenameClassUpdateClassDefinedSelectorsInTheParentPackage RPackage.SystemIntegration.RPackageClassesSynchronisationTest.testRenameClassUpdateOrganizerClassExtendingPackagesMapping RPackage.SystemIntegration.RPackageClassesSynchronisationTest.testReorganizeClassByAddingNewProtocolDoesNothing RPackage.SystemIntegration.RPackageClassesSynchronisationTest.testRemoveClassUpdateTheOrganizerMappings RPackage.SystemIntegration.RPackageClassesSynchronisationTest.testRenameClassUpdateOrganizerClassPackageMapping RPackage.SystemIntegration.RPackageClassesSynchronisationTest.testRecategorizeClassRegisterTheClassInTheExactMatchPackage RPackage.SystemIntegration.RPackageClassesSynchronisationTest.testRemoveClassUnregisterTheClassExtensionMethodsFromTheCorrespondingPackage ...

Sept. 19, 2013

[regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2.1-Validation/label=li… 169 regressions found. Gofer.Tests.GoferOperationTest.testLocalChanges Gofer.Tests.GoferOperationTest.testReinitialize Gofer.Tests.GoferOperationTest.testRemoteChanges RPackage.SystemIntegration.RPackageCategorySynchronisationTest.testAddCategoryCreatesPackage RPackage.SystemIntegration.RPackageCategorySynchronisationTest.testRenameCategoryAlsoRenameAllExtensionProtocols RPackage.SystemIntegration.RPackageCategorySynchronisationTest.testAddCategoryIsAlreadyAPackageDoesNotCreatePackage RPackage.SystemIntegration.RPackageCategorySynchronisationTest.testRenameCategoryChangeTheNameOfThePackage RPackage.SystemIntegration.RPackageCategorySynchronisationTest.testRenameUnknownCategoryCreatesNewRPackage RPackage.SystemIntegration.RPackageCategorySynchronisationTest.testRenameCategoryUpdateTheOrganizer RPackage.SystemIntegration.RPackageClassesSynchronisationTest.testRecategorizeClassWithMetaClassMethodsRegisterAllClassMethodsInTheNewPackage RPackage.SystemIntegration.RPackageClassesSynchronisationTest.testReorganizeClassByRenamingExtensionCategoryToClassicCategoryMoveMethodsFromExtendingPackageToParentPackage RPackage.SystemIntegration.RPackageClassesSynchronisationTest.testRecategorizeClassRaisesClassRepackagedEvent RPackage.SystemIntegration.RPackageClassesSynchronisationTest.testRecategorizeClassWithUnexistingPackageNameRegisterTheClassInANewPackage RPackage.SystemIntegration.RPackageClassesSynchronisationTest.testRenameClassUpdateClassDefinedSelectorsInTheParentPackage RPackage.SystemIntegration.RPackageClassesSynchronisationTest.testRenameClassUpdateOrganizerClassExtendingPackagesMapping RPackage.SystemIntegration.RPackageClassesSynchronisationTest.testReorganizeClassByAddingNewProtocolDoesNothing RPackage.SystemIntegration.RPackageClassesSynchronisationTest.testRemoveClassUpdateTheOrganizerMappings RPackage.SystemIntegration.RPackageClassesSynchronisationTest.testRenameClassUpdateOrganizerClassPackageMapping RPackage.SystemIntegration.RPackageClassesSynchronisationTest.testRecategorizeClassRegisterTheClassInTheExactMatchPackage RPackage.SystemIntegration.RPackageClassesSynchronisationTest.testRemoveClassUnregisterTheClassExtensionMethodsFromTheCorrespondingPackage ...

Sept. 19, 2013

Re: [Pharo-dev] About Morphic Documentation

by Igor Stasenko

On 19 September 2013 14:36, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: > 2013/9/19 kilon <thekilon(a)yahoo.co.uk> > >> This is why I insist on collecting things on one place, inside pharo. Web >> is >> all over the place, its great for finding information and for getting >> people >> work together , but not great learning things you are not familiar with. >> >> Why not having the documentation the same way as in Eclipse ? > > I mean the documentation would be on the web, available to anyone, > and each class / each package inside Pharo has a link towards its online > documentation. > This way the image size does not grow because of massive documentation. > It could be that showing the documentation of a class / package in Pharo > would directly > show inside Pharo a view of the web page corresponding to its actual > documentation. > > even more, not only view, but also edit it in place. then we need just a simple server setup with REST protocol, which can be easily used by image via Zinc.. > Actually GUI wise Mophics is one the best examples. Think about it, if you >> try to use any GUI in python for example, you are out of luck it has none. >> Even Tkinter which is the gui it comes with cpython is not coded in >> python , >> its coded in tk a scripiting language. Python GUI APIs widely used include >> PyGTK , PyQT , WxPython , all of them wrappers for C/C++ libraries. Other >> dynamic languages follow the same recipe. >> >> Of course these frameworks are much more documented than morphic , but >> unlike morphic they follow a monolithic widget architecture, and modifying >> the source in any way requires a mandatory knowledge of C/C++. And we >> should exclude their myriad of problem , GTKs notorious buginess on macos >> and windows , QT massive complexity for big GUIs up to the point it offer >> a >> dedicated programming language QML just for designing GUIs. >> >> On the other hand morphic is to a very large extend smalltalk. So you get >> a >> lot of power but also a lot more simplicity. Some areas however are in >> need >> for some more love and of course documentation is lacking and the speed of >> the gui is far from breathtaking. >> >> Morphic is a very big reason why I am with pharo, to be exact I find its >> ability to do visual coding and transform a smalltalk object to a visual >> element very appealing and I would love to work on that. Morphic halos is >> another very nice feature. The other reason is live coding of course. >> >> I will try to add to the documentation of morphic, I agree 100% we need >> more >> of it. >> >> FDominicus wrote >> > kilon < >> >> > thekilon@.co >> >> > > writes: >> > >> >> How does "extending Pharo help tool " sounds ? :) >> >> >> >> I am struggling to learn how morphic really works, especially >> >> TreeMorph. >> > Well that is a thing I tried more than once, but somehow I never >> > understood on how to make good use for Morphic for me. I checked a lot >> > of tutorial but then even simple things like menues seem to be doable >> > but not for me.. >> > >> > It is strange and not "nice". >> > >> > Regards >> > Friedrich >> >> >> >> >> >> -- >> View this message in context: >> http://forum.world.st/if-Pharo-is-key-for-you-tp4708875p4709143.html >> Sent from the Pharo Smalltalk Developers mailing list archive at >> Nabble.com. >> >> > -- Best regards, Igor Stasenko.

Sept. 19, 2013

Re: [Pharo-dev] About Morphic Documentation

by Esteban Lorenzano

On Sep 19, 2013, at 2:36 PM, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: > 2013/9/19 kilon <thekilon(a)yahoo.co.uk> > This is why I insist on collecting things on one place, inside pharo. Web is > all over the place, its great for finding information and for getting people > work together , but not great learning things you are not familiar with. > > Why not having the documentation the same way as in Eclipse ? > > I mean the documentation would be on the web, available to anyone, > and each class / each package inside Pharo has a link towards its online documentation. > This way the image size does not grow because of massive documentation. > It could be that showing the documentation of a class / package in Pharo would directly > show inside Pharo a view of the web page corresponding to its actual documentation. +1 > > Actually GUI wise Mophics is one the best examples. Think about it, if you > try to use any GUI in python for example, you are out of luck it has none. > Even Tkinter which is the gui it comes with cpython is not coded in python , > its coded in tk a scripiting language. Python GUI APIs widely used include > PyGTK , PyQT , WxPython , all of them wrappers for C/C++ libraries. Other > dynamic languages follow the same recipe. > > Of course these frameworks are much more documented than morphic , but > unlike morphic they follow a monolithic widget architecture, and modifying > the source in any way requires a mandatory knowledge of C/C++. And we > should exclude their myriad of problem , GTKs notorious buginess on macos > and windows , QT massive complexity for big GUIs up to the point it offer a > dedicated programming language QML just for designing GUIs. > > On the other hand morphic is to a very large extend smalltalk. So you get a > lot of power but also a lot more simplicity. Some areas however are in need > for some more love and of course documentation is lacking and the speed of > the gui is far from breathtaking. > > Morphic is a very big reason why I am with pharo, to be exact I find its > ability to do visual coding and transform a smalltalk object to a visual > element very appealing and I would love to work on that. Morphic halos is > another very nice feature. The other reason is live coding of course. > > I will try to add to the documentation of morphic, I agree 100% we need more > of it. > > FDominicus wrote > > kilon < > > > thekilon@.co > > > > writes: > > > >> How does "extending Pharo help tool " sounds ? :) > >> > >> I am struggling to learn how morphic really works, especially > >> TreeMorph. > > Well that is a thing I tried more than once, but somehow I never > > understood on how to make good use for Morphic for me. I checked a lot > > of tutorial but then even simple things like menues seem to be doable > > but not for me.. > > > > It is strange and not "nice". > > > > Regards > > Friedrich > > > > > > -- > View this message in context: http://forum.world.st/if-Pharo-is-key-for-you-tp4708875p4709143.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > >

Sept. 19, 2013

Re: [Pharo-dev] [OT] Pharo lighthouse wallpaper

by Esteban A. Maringolo

I uploaded a few a took to http://www.flickr.com/photos/emaringolo/sets/72157635649023613/. We have a lighthouse in a beach two kilometers from where I live, I love to see its light beam in the sky at night. Esteban A. Maringolo 2013/9/19 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > I have some pictures of lighthouse that I could give. I love lighthouse. > There are so positive. > > Stef > On Sep 19, 2013, at 1:33 AM, Torsten Bergmann <astares(a)gmx.de> wrote: > >> http://wallpapers5.com/images/wallpapers/71156968/Photography/Cape-Hatteras… >> >> According to site Image is for personal, non commercial use >> > >

Sept. 19, 2013

bytecode table

by ClÃ©ment Bera

Hey, Yesterday I printed the bytecode set of Pharo / Squeak (named SqueakV3PlusClosure) in a nice way to have a better overview. Perhaps some people will be interested in it. You can print it on a A3. Best, PS: Thanks Guille for the page layout, margins and stuff.

Sept. 19, 2013