February 2014 - Pharo-dev - lists.pharo.org

[pharo-project/pharo-core] bbf231: 30738

by GitHub

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: bbf2310921f674f2b94772095b47310ea9888091 https://github.com/pharo-project/pharo-core/commit/bbf2310921f674f2b9477209… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-02-03 (Mon, 03 Feb 2014) Changed paths: M Nautilus.package/AbstractNautilusUI.class/class/menu/classesFixMenu_.st A Nautilus.package/AbstractNautilusUI.class/instance/menus behavior/addFullClass.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script391.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30738.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A Tools.package/AbstractTool.class/class/private/defineFullClassTemplate.st A Tools.package/AbstractTool.class/instance/class/addFullClassIn_.st M ToolsTest.package/OpenToolTest.class/instance/test browse/testOpenBrowseOnInstalledTraitMethod.st Log Message: ----------- 30738 12771 KeyNotFound: key #localSelectors not found in MethodDictionary https://pharo.fogbugz.com/f/cases/12771 12769 Add a full class definition menu in nautilus https://pharo.fogbugz.com/f/cases/12769 http://files.pharo.org/image/30/30738.zip

Feb. 3, 2014

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/30738 Home: https://github.com/pharo-project/pharo-core

Feb. 3, 2014

[pharo-project/pharo-core] 8215ef: 30737

by GitHub

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: 8215efddb24de39f84bf15551fdccad678b9699f https://github.com/pharo-project/pharo-core/commit/8215efddb24de39f84bf1555… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-02-03 (Mon, 03 Feb 2014) Changed paths: M RPackage-Core.package/RPackage.class/instance/accessing/removeClass_.st M RPackage-Core.package/RPackage.class/instance/private/basicImportClass_.st A RPackage-Tests.package/RPackageExtensionMethodsSynchronisationTest.class/instance/tests - operations on methods/testMoveClassInPackageWithExtensionsOnClass.st A RPackage-Tests.package/RPackageExtensionMethodsSynchronisationTest.class/instance/tests - operations on methods/testMoveClassInPackageWithExtensionsOnClass2.st A RPackage-Tests.package/RPackageExtensionMethodsSynchronisationTest.class/instance/tests - operations on methods/testMoveClassInPackageWithExtensionsOnClassAndBack.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script390.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30737.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 30737 12655 RPackage bug when moving a class to another package that has extensions in that package already https://pharo.fogbugz.com/f/cases/12655 http://files.pharo.org/image/30/30737.zip

Feb. 3, 2014

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/30737 Home: https://github.com/pharo-project/pharo-core

Feb. 3, 2014

Re: [Pharo-dev] WhatsUp from: 2014-02-03 until: 2014-02-16

by Tudor Girba

### Here's what I've been up to since the last WhatsUp: Developed and documented more use cases in the GTInspector: - Browsing files: http://www.humane-assessment.com/blog/browsing-files-with-gtinspector/ - Code analysis: http://www.humane-assessment.com/blog/looking-for-undesired-key-bindings - Managing extensions: http://www.humane-assessment.com/blog/managing-gtinspector-extensions/ - Performance analysis: http://www.humane-assessment.com/blog/assessing-pharo-performance-with-gtin… Presented Moose and humane assessment at an event on "Managing Technical Debt" (http://si-se.ch/2014/) ### What's next, until 2014-02-16 (*): More GT stuff. Some directions we (Andrei and I) are thinking of: - how to make the workspace obsolete, - how to integrate examples, or - how to build a fresh code browsing in the inspector. (if you are interested in participating, please let me know) Doru -- www.tudorgirba.com "Every thing has its own flow"

Feb. 3, 2014

Re: [Pharo-dev] Seaside extensions and lowercase package names in Pharo

by Goubier Thierry

Le 02/02/2014 17:11, Pharo4Stef a Ã©crit : > Chris > > There are several points: > - we will maintain compatibility when filein/out using * > - now I was not aware that the class extensions should be lower case. They are in the current implementation of RPackage. Normally there is code to ensure case-isensivity. > - Pharo should clean the packages because some of the extensions are for > packages not existing anymore > and other edge cases. Yes! Thierry -- Thierry Goubier CEA list Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

Feb. 3, 2014

Re: [Pharo-dev] test failures in downloaded image 30733

by Marcus Denker

On 02 Feb 2014, at 16:27, btc(a)openinworld.com wrote: > Thanks for your feedback Marcus. A couple of thought inline... > > Marcus Denker wrote: >> >> On 02 Feb 2014, at 14:31, btc(a)openinworld.com wrote: >> >> >>> For diligence and curiosity leading up to the Pharo3 release, I downloaded build image 30733 (with PharoLauncher) >>> >> Another wonderful thing is that tests are fine when run individually, but fail when running all tests. >> > > It seems that when clicking on the failed test, the test is re-run and that result is debugged - but sometimes the error doesn't occur. It would be great the context of the error in the original execution was stored so that actual error could be inspected. Indeed, (to dream) presuming you're working off fresh CI build, it would be cool if using Fuel in one step you send the context of the original error (with CI build meta-info attached) to someone else's PharoLauncher, which automatically downloads the required CI build, and launches with the Fuel file loaded and ready to debug. > On the ci server this is already done: failing tests are serialise with Fuel for debugging. In addition, the image is save and can be downloaded (in the state after the test run). >> We need to think about automatic UI testingâ¦ >> >> Loading an external package changes *everything*. We do not have a a release criterium that all tests are green after loading external packages. >> > > No external packages loaded here. Launcher? Itâs external in the sense that this is not code that is in the image when we run all tests on the build server. > btw, What was your OS environment? > Mac >>> 3. Assuming Pharo3 will go through a Release Candidate phase, >>> >> >> Normally the idea is that we will just release. In the past we used an elaborate process, but the reality is that nobody looks at release candidates. >> You can tell 5 times that the release candidate will be released unchanged and people should check: they will not. They will download >> the release, though, and then complain that the âobviousâ thing X is not fixed that that the people who managed the release process did >> everything wrong. Because âreleaseâ means bug free. By magic. >> >> >> > I've seen that happening previously. In trying to understand the reality of this, perhaps... > * "check if this is okay" is an open ended question that doesn't have a deliverable to drive people to action. How do you know when its time to report success/failure? > * people do download and try it but its only shallow testing > * people only report by exception. > > Perhaps a more defined task such as "Run All Tests" is easier for people to do (single button press) and to report success/failure. PharoLaucher also makes it easier and quicker to do this. You don't need to call it a Release Candidate. Just have a specified version that multiple people run in multiple environments. Of course, that could also open up a can of worms of being hard from your end to dealing every test failure due to other people's environments. There would need a pragmatic approach about which ones to deal with to stay on schedule with the release date. > yesâ¦ its important that we don burn ourselves while doing the release, that is why the idea was to move as much things upfront as possible (âthe build is the release unchangedâ) Marcus

Feb. 3, 2014

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/30736 Home: https://github.com/pharo-project/pharo-core

Feb. 3, 2014

[pharo-project/pharo-core] 857012: 30736

by GitHub

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: 85701269c487dc49fa2fd4f7c6b1f35593baf903 https://github.com/pharo-project/pharo-core/commit/85701269c487dc49fa2fd4f7… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-02-02 (Sun, 02 Feb 2014) Changed paths: A Nautilus.package/PackageTreeNautilusUI.class/instance/package/alertCategoryName_exitstsAlreadyIn_.st A Nautilus.package/PackageTreeNautilusUI.class/instance/package/category_existsIn_.st M Nautilus.package/PackageTreeNautilusUI.class/instance/private dispatch/renameClassCategory_.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script389.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30736.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A Slot.package/BitsLayout.class/instance/testing/isBytes.st A Slot.package/BitsLayout.class/instance/testing/isWords.st A Slot.package/ByteLayout.class/instance/testing/isBytes.st A Slot.package/WordLayout.class/instance/testing/isBytes.st A SlotTests.package/SlotAnnouncementsTest.class/instance/tests-integration/testFixedClassWhenTraitCompositionChangedShouldAnnounceClassModified.st A SlotTests.package/SlotAnnouncementsTest.class/instance/tests-integration/testFixedClassWithTraitCreatedShouldntAnnounceClassModified.st A SlotTests.package/SlotAnnouncementsTest.class/instance/tests-integration/testVariableByteClassWhenTraitCompositionChangedShouldAnnounceClassModified.st A SlotTests.package/SlotAnnouncementsTest.class/instance/tests-integration/testVariableByteClassWithTraitCreatedShouldntAnnounceClassModified.st A SlotTests.package/SlotAnnouncementsTest.class/instance/tests-integration/testVariableClassWhenTraitCompositionChangedShouldAnnounceClassModified.st A SlotTests.package/SlotAnnouncementsTest.class/instance/tests-integration/testVariableClassWithTraitCreatedShouldntAnnounceClassModified.st A SlotTests.package/SlotAnnouncementsTest.class/instance/tests-integration/testVariableWordClassWhenTraitCompositionChangedShouldAnnounceClassModified.st A SlotTests.package/SlotAnnouncementsTest.class/instance/tests-integration/testVariableWordClassWithTraitCreatedShouldntAnnounceClassModified.st A SlotTests.package/SlotAnnouncementsTest.class/instance/tests-integration/testWeakClassWhenTraitCompositionChangedShouldAnnounceClassModified.st A SlotTests.package/SlotAnnouncementsTest.class/instance/tests-integration/testWeakClassWithTraitCreatedShouldntAnnounceClassModified.st M SlotTests.package/TOne.class/README.md M SlotTests.package/TTwo.class/README.md M SlotTests.package/TestSharedPool.class/README.md M System-Announcements.package/ClassModifiedClassDefinition.class/README.md A Traits.package/TClass.class/instance/subclass creation - private/subclass_uses_with_.st M Traits.package/TClass.class/instance/subclass creation/subclass_uses_instanceVariableNames_classVariableNames_poolDictionaries_category_.st M Traits.package/TClass.class/instance/subclass creation/variableByteSubclass_uses_instanceVariableNames_classVariableNames_poolDictionaries_category_.st M Traits.package/TClass.class/instance/subclass creation/variableSubclass_uses_instanceVariableNames_classVariableNames_poolDictionaries_category_.st M Traits.package/TClass.class/instance/subclass creation/variableWordSubclass_uses_instanceVariableNames_classVariableNames_poolDictionaries_category_.st M Traits.package/TClass.class/instance/subclass creation/weakSubclass_uses_instanceVariableNames_classVariableNames_poolDictionaries_category_.st Log Message: ----------- 30736 12727 Duplicated categories in Nautilus https://pharo.fogbugz.com/f/cases/12727 12157 Wrong announcement of ClassModifiedClassDefinition https://pharo.fogbugz.com/f/cases/12157 11670 strange MC package Generated-code-non-existing-package https://pharo.fogbugz.com/f/cases/11670 http://files.pharo.org/image/30/30736.zip

Feb. 3, 2014

Re: [Pharo-dev] Comparing dates

by Damien Cassou

Please use #assert:equals (that won't change the result though :-)) On Feb 1, 2014 12:04 AM, "Sebastian Sastre" <sebastian(a)flowingconcept.com> wrote: > self assert: Date today = Date today. > > today := Date today translateTo: 2 hours. > self assert: today = Date today > > Is this right? > > > > >

Feb. 3, 2014