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

[pharo-project/pharo-core] 9687d2: 40227
by GitHub Sept. 16, 2014

Sept. 16, 2014

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 9687d2baa4530b849cb16a540616f4c1b00eba35 https://github.com/pharo-project/pharo-core/commit/9687d2baa4530b849cb16a54… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-09-16 (Tue, 16 Sep 2014) Changed paths: M EmbeddedFreeTypeTests.package/EmbeddedFreeTypeFontInstallerTest.class/instance/tests/testinstallAllFontsIn.st A FontInfrastructureTests.package/LogicalFontManagerTest.class/README.md A FontInfrastructureTests.package/LogicalFontManagerTest.class/definition.st A FontInfrastructureTests.package/LogicalFontManagerTest.class/instance/tests/testHasCurrentFreeTypeFontProvider.st A FontInfrastructureTests.package/extension/LogicalFontManager/instance/identityIncludesFontProvider_.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script227.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40227.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 40227 14020 Add test cases which check font installation process and registration on singletons https://pharo.fogbugz.com/f/cases/14020 14006 3 tests fail for AsmJit in the Pharo4 https://pharo.fogbugz.com/f/cases/14006 http://files.pharo.org/image/40/40227.zip

1 0

Pragmas/Annotations for classes
by Torsten Bergmann Sept. 16, 2014

Sept. 16, 2014

Currently only methods support pragmas in Pharo. Therefore we already had a discussion about "Pragmas/Annotations for classes". See http://forum.world.st/Pragmas-Annotations-for-classes-td2282310.html To summarize: it would be helpfull to have them (and with them also get rid of workarounds like specific conventions, abusing class comments, etc.). At that time it was not possible to add an iVar to Class, but this issue was solved already: https://pharo.fogbugz.com/f/cases/11596/Adding-an-iVar-to-class-Class-gives… Must admit I havent tested in latest Pharo 4 if this is still working. After we now have slots and other nice extensions in Pharo again my basic question: what about having "annotations" for a class in Pharo. I think we will find enough use cases on annotating a class with someting useful. Even a category or a comment could just be an annotation. Is there interest to have such a change for Pharo4 or are there reasons to abandon such an idea. I guess such a change could not be provided with a simple slice. Any thoughts/decisions? Thanks T.

3 2

Pharo Success Stories on homepage
by Torsten Bergmann Sept. 16, 2014

Sept. 16, 2014

The new homepage shows only 2 (!) success story. But we have so many as one can see here: http://rmod.lille.inria.fr/archives/events/2012PharoConf/SuccessStories http://files.pharo.org/successStories This gives a false impression on the homepage to newcomers. If it is a time issue then at least the links should be added.

6 6

How often should a uninitializedvariable warning be shown?
by Stephan Eggermont Sept. 15, 2014

Sept. 15, 2014

Does it make sense to warn more than once for each variable? Stephan distibutionMapOn: a a roassal2 title: 'Distribution map'; painting: [:view2 | "Simple example of a distribution map. Green methods are short. Orange are long. Red are very long" | view classes d packages | self halt. packages := self forumPackages. classes := OrderedCollection new. packages do: [ :p | classes addAll: p classes ]. d := IdentityDictionary new. classes do: [:aClass | aClass methods do: [:m | d at: m put: m getSource lineCount ] ]. view shape rectangle withoutBorder. view nodes: classes forEach: [ :each | view shape label. view node: each. view node: each forIt: [ view interaction action: #browse. view shape rectangle size: 8; if: [:m | (d at: m) < 5 ] fillColor: Color green; if: [:m | (d at: m) >= 5 and: [ (d at: m) < 25 ] ] fillColor: Color orange; if: [:m | (d at: m) >= 25 ] fillColor: Color red. view nodes: (each methods sortedAs: [:m | (d at: m) ]). view gridLayout gapSize: 1 ]. view verticalLineLayout ]. view gridLayout]

5 5

[pharo-project/pharo-core] aa28e7: 40217
by GitHub Sept. 15, 2014

Sept. 15, 2014

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: aa28e797888dded04a4b8d67eab2e57a7ab516a5 https://github.com/pharo-project/pharo-core/commit/aa28e797888dded04a4b8d67… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-09-10 (Wed, 10 Sep 2014) Changed paths: M Collections-Sequenceable.package/OrderedCollection.class/instance/enumerating/do_.st M Collections-Sequenceable.package/OrderedCollection.class/instance/enumerating/reverseDo_.st A DebuggerModel.package/DebugSystemSettings.class/README.md A DebuggerModel.package/DebugSystemSettings.class/class/private - settings/addDebugFilterSessingsOn_.st A DebuggerModel.package/DebugSystemSettings.class/class/settings/debugSettingsOn_.st A DebuggerModel.package/DebugSystemSettings.class/definition.st A Nautilus.package/AbstractNautilusUI.class/instance/menus behavior/compareTwoMethods.st M Nautilus.package/MethodWidget.class/class/menu/elementsMenu_.st A Nautilus.package/NautilusUI.class/instance/menus behavior/compareTwoMethods.st A Nautilus.package/NautilusUI.class/instance/widget method/enableMethodDualSelection.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script217.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40217.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st R Settings-Tools.package/DebugSystemSettings.class/README.md R Settings-Tools.package/DebugSystemSettings.class/class/private - settings/addDebugFilterSessingsOn_.st R Settings-Tools.package/DebugSystemSettings.class/class/settings/debugSettingsOn_.st R Settings-Tools.package/DebugSystemSettings.class/definition.st Log Message: ----------- 40217 13985 OrderedCollection>>#do: and #reverseDo: are not consistent with the other enumerations https://pharo.fogbugz.com/f/cases/13985 13986 move DebugSystemSettings to DebuggerModel package https://pharo.fogbugz.com/f/cases/13986 13981 Nautilus should allow to compare two methods https://pharo.fogbugz.com/f/cases/13981 http://files.pharo.org/image/40/40217.zip

2 1

TWM - Shortcuts - Fixed.
by phil＠highoctane.be Sept. 15, 2014

Sept. 15, 2014

I was frustrated by being unable to have the Tiling Window Manager shortcuts not working properly in 3.0 This is now fixed by registering the category as a global one. Sean, Laurent, is this working for you? Phil

5 10

#doSemanticAnalysisIn: error
by Esteban A. Maringolo Sept. 15, 2014

Sept. 15, 2014

>From time to time when I halt the execution (or try to halt it) I get walkbacks reporting a MNU in nil #doSemanticAnalaysisIn: nil Now after hiting Alt+. for a while I was able to recover the control of the image, but when selecting the "Morphic UI process" in the process explorer I get a similar walkback (see screenshot). Why is this? Is it a know bug? Esteban A. Maringolo

3 3

GToolkit
by phil＠highoctane.be Sept. 15, 2014

Sept. 15, 2014

I've been working in a data acquisition scenario today and GToolkit proved to be of immense help. Working in the live application, looking around for data (including file contents), and inspecting it all + live debugging is really a sweet experience. With CommandShell I may not have to leave the environment... Phil

5 6

Sprint Friday 26 @ Lille
by stepharo Sept. 15, 2014

Sept. 15, 2014

Hi guys we will organize an official Pharo Sprint at Lille Friday 26 as mentioned in the calendar http://pharo.org/contribute-events Let us know if you plan to join. We will take care of the logistic :) Stef

1 0

About renaming API methods
by Marcus Denker Sept. 15, 2014

Sept. 15, 2014

Hi, In case we rename methods that are used as part of the public API, I propose to do 1) add the same API to the current stable version (today this would be Pharo3 2) add a rule (in a âPort Pharo3 to Pharo4â category that finds the needed senders (if possible even with a transformation) Then depending on the use and importance -> deprecate the old API right away or -> just tag it as âto be deprecatedâ one version later or -> keep the old as âcompatibilityâ This should make it possible to clean up API (e.g. when there are typos in the selectorâ¦), while not disturbing users to much. *And* it will be possible to have affected code running both in Stable and Development. (This should not be a strict rule, more a âbest effortâ one, and there will always be cases where we can not do this or where it is not needed). Marcus

4 4