November 2015 - Pharo-dev - lists.pharo.org

[pharo-project/pharo-core]
by GitHub Nov. 11, 2015

Nov. 11, 2015

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

1 0

autocategorizing
by Peter UhnÃ¡k Nov. 11, 2015

Nov. 11, 2015

How does autocategorizing decides what to put where? For example I have (on class-side) three methods #example #example2 #exampleClusters after autocategorizing they end up being #example in 'example' protocol #example2 in 'examples' protocol #exampleClusters in 'as yet unclassified' protocol That seems really odd, shouldn't all of them be in the same protocol? Also is 'example' or 'examples' the normative protocol? Thanks, Peter

2 1

Removing Object >> #name
by Guillermo Polito Nov. 10, 2015

Nov. 10, 2015

Hey, I was following the discussion about Class>>#name and Object>>#name so I checked what happened if I removed #name from Object. 1) The system did not blew up. I could open a browser and a test runner. 2) I could use spotter, look for a class, dive in, look for methodsâ¦ Same for the inspector. 3) I ran all the tests in the image. - I saw some failures in GT* and Glamour. I ran them in a new image and they are not failing so maybe they are broken because of the change or some side effect of the tests? - Then I saw some failures of OpenToolTest and MBGroupInfoTest that *do look related* 4) I created a Package and it worked 5) I tried to create a class and it exploded with RBBrowserEnvironment DNU #includesKey:. This however explodes also in a clean image so I do not think it is related. 6) I could however create new methods... Of course integrating such a little change is still scary :). But I can propose a sliceâ¦ Votes in favor? :) Guille

3 5

[pharo-project/pharo-core]
by GitHub Nov. 10, 2015

Nov. 10, 2015

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

1 0

[pharo-project/pharo-core] 268e30: 50431
by GitHub Nov. 10, 2015

Nov. 10, 2015

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 268e3014abc774b59d1e385ca3fc5ef1adbe5ed5 https://github.com/pharo-project/pharo-core/commit/268e3014abc774b59d1e385c… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-11-10 (Tue, 10 Nov 2015) Changed paths: A Graphics-Shapes.package/PathShape.class/instance/adding/addVertex_.st R Graphics-Shapes.package/PathShape.class/instance/as yet unclassified/addVertex_.st R Graphics-Shapes.package/PathShape.class/instance/as yet unclassified/calculatedBounds.st R Graphics-Shapes.package/PathShape.class/instance/as yet unclassified/containsPoint_.st R Graphics-Shapes.package/PathShape.class/instance/as yet unclassified/segmentsDo_.st A Graphics-Shapes.package/PathShape.class/instance/compute/calculatedBounds.st A Graphics-Shapes.package/PathShape.class/instance/enumerating/segmentsDo_.st A Graphics-Shapes.package/PathShape.class/instance/testing/containsPoint_.st R Graphics-Shapes.package/Polygon.class/instance/as yet unclassified/containsPoint_.st R Graphics-Shapes.package/Polygon.class/instance/as yet unclassified/segmentsDo_.st A Graphics-Shapes.package/Polygon.class/instance/enumerating/segmentsDo_.st A Graphics-Shapes.package/Polygon.class/instance/testing/containsPoint_.st A Graphics-Shapes.package/Shape.class/instance/accessing/bounds.st R Graphics-Shapes.package/Shape.class/instance/as yet unclassified/basicContainsPoint_.st R Graphics-Shapes.package/Shape.class/instance/as yet unclassified/bounds.st R Graphics-Shapes.package/Shape.class/instance/as yet unclassified/containsPoint_.st A Graphics-Shapes.package/Shape.class/instance/testing/basicContainsPoint_.st A Graphics-Shapes.package/Shape.class/instance/testing/containsPoint_.st M OpalCompiler-Core.package/IRBytecodeGenerator.class/instance/results/bytecodes.st M OpalCompiler-Core.package/extension/Object/instance/mustBeBooleanInMagic_.st A OpalCompiler-Tests.package/MustBeBooleanTests.class/instance/tests/testDNU.st M Reflectivity.package/ReflectiveMethod.class/instance/evaluation/generatePrimitiveWrapper.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50430.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50431.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50430.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50431.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A Spec-Core.package/TreeModel.class/class/examples/exampleOfAutoRefreshOnExpand.st M Spec-Core.package/TreeModel.class/definition.st A Spec-Core.package/TreeModel.class/instance/api/autoRefreshOnExpand.st A Spec-Core.package/TreeModel.class/instance/api/autoRefreshOnExpand_.st M Spec-Core.package/TreeModel.class/instance/initialization/initialize.st M Spec-MorphicAdapters.package/SpecTreeNodeModel.class/definition.st M Spec-MorphicAdapters.package/SpecTreeNodeModel.class/instance/accessing/childrenItems.st A Spec-MorphicAdapters.package/SpecTreeNodeModel.class/instance/accessing/childrenItemsBlock.st A Spec-MorphicAdapters.package/SpecTreeNodeModel.class/instance/accessing/childrenItemsBlock_.st M Spec-MorphicAdapters.package/SpecTreeNodeModel.class/instance/accessing/childrenItems_.st M Spec-MorphicAdapters.package/SpecTreeNodeModel.class/instance/accessing/contents.st M Spec-MorphicAdapters.package/SpecTreeNodeModel.class/instance/accessing/setChildren_.st Log Message: ----------- 50431 16971 fix: support primitive methods wit arguments https://pharo.fogbugz.com/f/cases/16971 16918 Cant configure a tree to auto refresh when a node is folded and then unfolded https://pharo.fogbugz.com/f/cases/16918 16908 wrong source node for pc in mustBeBooleanInMagic https://pharo.fogbugz.com/f/cases/16908 16970 Cleaning Graphics-Shapes categorisation https://pharo.fogbugz.com/f/cases/16970 http://files.pharo.org/image/50/50431.zip

1 0

Is RBRefactoryChange alive, and what do I use for recategorization
by Yuriy Tymchuk Nov. 10, 2015

Nov. 10, 2015

Hi everyone. in my critic projects I need a concept of a âchangeâ the can be previewed, executed or combined with other changes. I.e. if a critic can propose an automated solution, it has to be _something_. At the moment Iâve started to use RBRefactoryChange, but I want to know whether it is the thing to use, or maybe someone is preparing a replacement. Because classes have no comments. no real diff support and so onâ¦ If it is the thing to use, which change should I use for a recategorization (change protocol) of a method? Thanks. Uko

2 1

[ANN] No-Metadata mode for GitFileTree
by Thierry Goubier Nov. 9, 2015

Nov. 9, 2015

Oh yes, I can announce that from now on, the development version of GitFileTree for Pharo 5 handles FileTree repositories without most of the metadata (precisely version and methodProperties). This makes the format a lot more DVCS friendly (Git, Fossil, Hg, SVN, all...) by cutting the noise on diffs and conflicts on merge and cherry picking. Note: it only apply to brand new repositories; nothing is changed for pre-existing ones. Note2: reading those Metadata-less repositories with FileTree does give you packages without metadata: no version history, no author, no author nor timestamp on methods. Note3: it is possible to hack a repo from metadata to non-metadata mode, but I won't explain it. Enjoy and tell me how it works for you. I'm especially interested by heavy branchers/mergers reports :) Thierry

2 6

[pharo-project/pharo-core]
by GitHub Nov. 9, 2015

Nov. 9, 2015

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

1 0

[pharo-project/pharo-core] 006851: 50430
by GitHub Nov. 9, 2015

Nov. 9, 2015

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 006851356e13cd0d0e4741193ff611e868d38305 https://github.com/pharo-project/pharo-core/commit/006851356e13cd0d0e474119… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-11-09 (Mon, 09 Nov 2015) Changed paths: M Kernel.package/Point.class/README.md M Kernel.package/Point.class/instance/arithmetic/abs.st M Kernel.package/Point.class/instance/arithmetic/max.st M Kernel.package/Point.class/instance/arithmetic/min.st M Kernel.package/Point.class/instance/arithmetic/reciprocal.st A Kernel.package/Point.class/instance/testing/isIntegerPoint.st A Kernel.package/Point.class/instance/truncation and round off/ceiling.st A Kernel.package/Point.class/instance/truncation and round off/floor.st A Kernel.package/Point.class/instance/truncation and round off/roundDownTo_.st A Kernel.package/Point.class/instance/truncation and round off/roundUpTo_.st R Kernel.package/Point.class/instance/truncation and roundoff/ceiling.st R Kernel.package/Point.class/instance/truncation and roundoff/floor.st R Kernel.package/Point.class/instance/truncation and roundoff/isIntegerPoint.st R Kernel.package/Point.class/instance/truncation and roundoff/roundDownTo_.st R Kernel.package/Point.class/instance/truncation and roundoff/roundUpTo_.st M OpalTools.package/GTOpalScopeBrowser.class/instance/building/treeIn_.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50429.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50430.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50429.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50430.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M SmartSuggestions.package/extension/OCLiteralVariable/instance/specialCommands.st Log Message: ----------- 50430 16967 Inspecting the Scopes presentation of some ProgramNodes results in an exception https://pharo.fogbugz.com/f/cases/16967 16963 Smalltalk globals not needed for smart suggestions of OCLiteralValiable https://pharo.fogbugz.com/f/cases/16963 16953 Clean Point Reciprocal comment and improving class comment! https://pharo.fogbugz.com/f/cases/16953 http://files.pharo.org/image/50/50430.zip

1 0

[Reflectivity] Object invalidate now works
by Marcus Denker Nov. 9, 2015

Nov. 9, 2015

Hi, The mechanism that is behind the MetaLinks is now working for Object 50378: Object methods do: #createTwin. Object methods do: #invalidate. This means we are very close on having that working on the whole image. Next steps: -> invalidate the whole kernel. -> then: check/fix putting links on all methods (#before/#after). (there seems a bug in the code dealing with primitives, to check) -> then: meta-recursion stopping links: take care of the code executed until the recursion check is reached. Test. -> First use case: Breakpoints, with IDE integration. Marcus

1 2