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

[pharo-project/pharo-core]
by GitHub Feb. 15, 2017

Feb. 15, 2017

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

1 0

[pharo-project/pharo-core] 46dac9: 60394
by GitHub Feb. 15, 2017

Feb. 15, 2017

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 46dac952ad08686ed4675917623323a4e77426e2 https://github.com/pharo-project/pharo-core/commit/46dac952ad08686ed4675917… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2017-02-15 (Wed, 15 Feb 2017) Changed paths: A Kernel-Tests.package/ClassHierarchyTest.class/instance/tests/testObjectFormatInstSize.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60393.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60394.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60393.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60394.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60394 19010 ImmediateLayout and EphemeronLayout have wrong object format https://pharo.fogbugz.com/f/cases/19010 http://files.pharo.org/image/60/60394.zip

1 0

[pharo-project/pharo-core]
by GitHub Feb. 15, 2017

Feb. 15, 2017

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

1 0

[pharo-project/pharo-core] ad9d86: 60393
by GitHub Feb. 15, 2017

Feb. 15, 2017

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: ad9d866b884f6010e9e07de78d9ab03da81ba729 https://github.com/pharo-project/pharo-core/commit/ad9d866b884f6010e9e07de7… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2017-02-15 (Wed, 15 Feb 2017) Changed paths: M Monticello.package/MCClassDefinition.class/instance/installing/createClass.st M RPackage-Core.package/RPackageOrganizer.class/class/singleton/resetDefault.st M RPackage-Core.package/RPackageOrganizer.class/instance/private registration/basicRegisterPackage_.st M RPackage-Core.package/RPackageOrganizer.class/instance/private registration/basicUnregisterPackage_.st M RPackage-Core.package/RPackageOrganizer.class/instance/private/stopNotification.st M RPackage-Core.package/RPackageOrganizer.class/instance/system integration/registerInterestToAnnouncer_.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60392.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60393.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60392.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60393.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A Slot.package/ComputedSlot.class/README.md A Slot.package/ComputedSlot.class/definition.st A Slot.package/ComputedSlot.class/instance/accessing/block.st A Slot.package/ComputedSlot.class/instance/comparing/=.st A Slot.package/ComputedSlot.class/instance/comparing/hash.st A Slot.package/ComputedSlot.class/instance/instance creation/with_.st A Slot.package/ComputedSlot.class/instance/meta-object-protocol/read_.st A Slot.package/ComputedSlot.class/instance/meta-object-protocol/write_to_.st A Slot.package/ComputedSlot.class/instance/printing/printOn_.st Log Message: ----------- 60393 19710 Monticello should ignore the class definition of Context https://pharo.fogbugz.com/f/cases/19710 19711 RPackage should not strongly depend on Monticello https://pharo.fogbugz.com/f/cases/19711 19709 add example ComputedSlot https://pharo.fogbugz.com/f/cases/19709 http://files.pharo.org/image/60/60393.zip

1 0

[pharo-project/pharo-core]
by GitHub Feb. 15, 2017

Feb. 15, 2017

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

1 0

[pharo-project/pharo-core] c79b3f: 60392
by GitHub Feb. 15, 2017

Feb. 15, 2017

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: c79b3f4d5d0e0a00864b8f59cd2860cfb6b3a1f5 https://github.com/pharo-project/pharo-core/commit/c79b3f4d5d0e0a00864b8f59… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2017-02-15 (Wed, 15 Feb 2017) Changed paths: M BaselineOfIDE.package/BaselineOfIDE.class/instance/actions/preload_package_.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60391.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60392.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60391.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60392.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M System-Clipboard.package/Clipboard.class/instance/accessing/clipboardText_.st M System-Clipboard.package/ExternalClipboard.class/instance/accessing/clipboardText_.st M System-Clipboard.package/UnixClipboard.class/instance/accessing/clipboardText_.st A Text-Core.package/Text.class/instance/converting/copyWithoutExternalReferences.st A Text-Core.package/TextAttribute.class/instance/testing/mayHaveExternalReferences.st A Text-Core.package/TextLink.class/instance/testing/mayHaveExternalReferences.st R Versionner-Tests-Core-Model.package/MBConfigurationInfoTest.class/instance/tests/testInitialization.st Log Message: ----------- 60392 19707 remove Object>>#name hack in the BaselineOfIDE https://pharo.fogbugz.com/f/cases/19707 19706 remove MBConfigurationInfoTest>>#testInitialization https://pharo.fogbugz.com/f/cases/19706 19704 [Memory leak] Clipboard can produce memory leaks https://pharo.fogbugz.com/f/cases/19704 http://files.pharo.org/image/60/60392.zip

1 0

GLMAction and PharoShortcut
by Hilaire Feb. 15, 2017

Feb. 15, 2017

Hi, While writing these tooltips for the debugger, it seems to me some refactoring is needed in the use of Pharo shortcut: https://pharo.fogbugz.com/f/cases/19684/GLMAction-and-PharoShortcut-need-re… because the current situation to have Glamour tk rendering short cut as 'Ctrl-A' then Spec as 'Meta-A' Any opinion on the topic. Hilaire -- Dr. Geo http://drgeo.eu

5 8

Slack, fragmentation and design information
by Stephan Eggermont Feb. 15, 2017

Feb. 15, 2017

The past year we have started using Slack to communicate in real-time about Pharo. It has nice (mobile) clients and makes it easy to share pictures and snippets. As a result a large part of the communication about design and how to do things has moved from the mailing lists to Slack. As we're using the free version, and cannot afford to use the commercial version, we have no long-time storage of the design discussions. This contrasts with our mailing lists, that have a long-term archive. There was some discussion about this, and I'm not aware of that resulting in an accessible, easy to access archive. Also, we have not succeeded in summarizing design discussions from slack to the mailing lists. The resulting gap in design information forms an enormous long-term risk for our community. Without the design discussions it is much more difficult to later understand why decisions were taken. We cannot afford to let this short-term ease-of-use destroy Pharo's community history, and thereby Pharo. Let us fix this. Stephan

15 28

[QA] Scoped
by Hilaire Feb. 14, 2017

Feb. 14, 2017

Hi, What about the Nautilus Scoped button tooltip to be more explicit for newbie? What about: 'Browse the selected packaged in a scoped context: analysis tools as 'Senders of...', 'Implementors of...', 'Class refs...', etc. are limited to the package. Thanks Hilaire -- Dr. Geo http://drgeo.eu

2 2

Points, Free type fonts cache and memory leaks
by Pavel Krivanek Feb. 14, 2017

Feb. 14, 2017

Hi, It is very common to see in actively used images that the number of instances of Point is very high. Sometimes in order of hundreds of thousands. There is several reasons for that: Pharo every few milliseconds checks for the new display size. That check generates two instances of Point that are not garbage collected in reasonably short time. So if you periodically check the result of "Point allInstances size", you will see that it is quickly growing. On the other hand. That Point instances are not referenced by anyone so as soon as you do Smalltalk garbageCollect, the amount of Points in reduced. And they are correctly garbage collected by the VM after some time which is often longer than one minute. So no action needed. Then a lot of Points is stored in FreeTypeCache. That cache is a huge beast and it tries to store a small form for every new rendered character glyph. That means for every font, every pixel size etc. It sounds reasonable but the main reason why the cache can be very huge is in the fact that it stores a new glyph for every sub-pixel variant too! Every FreeTypeChacheEntry also contains several Point instances so it is a important source of them. Fortunately, this cache has mechanisms to limit its size. This limit now set to expected size of 5MB, see FreeTypeChache>>#defaultMaximumSize. So in the end, probably no immediate fix is needed although this cache deserves revision. And then we have a Text related memory leak that I will try to investigate. This memory leak does not let to garbage collect any tool window as soon as clipboard or history (undo) was used in it. Cheers, -- Pavel

3 3