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

Text Indentation in Pharo editor
by Torsten Bergmann Dec. 11, 2017

Dec. 11, 2017

Hi, in most code editors I know one can select a (multiline) block of code/text and then hit TAB to indent and move it from the position to the right side. Using SHIFT+TAB one can move it back to the left. In Pharo the selected text unfortunately is always deleted instead of moved/indented when hitting TAB. Is such an editor mode or special key combination available? If not could this easily be brought into the current text/code editor(s) in Pharo 7? Or will a possible upcoming Bloc text/code editor support such behavior? This would be really nice to have and move Pharo editor away from being like Notepad. Because editors in Eclipse, NetBeans, VS, Brackets, Atom, Notepad++ all support this TAB Indentation out of the box. ;) Thanks T.

8 10

About margin and rectangle
by Stephane Ducasse Dec. 10, 2017

Dec. 10, 2017

Hi While harvesting the old change of Henrik on margins and the idea that Rectangle should not be used to express margins. I looked at expandBy: comment In fact I would like to make sure that that no rectangle is passed as argument and that we can deprecate asMargin from the Rectangle class (we can keep it but I would like to identify the callers). expandBy: delta "Answer a Rectangle that is outset from the receiver by delta. delta is a Rectangle, Point, or scalar." ^ delta asMargin expandRectangle: self So looked at all the senders of expandBy: and they look ok. I imagine that I should do the same for extendBy: Stef

1 0

[ann] gtmondrian
by Tudor Girba Dec. 10, 2017

Dec. 10, 2017

Hi, We are happy to announce GT Mondrian, a graph visualization engine built on top of Bloc. It is similar to the original Mondrian and the Mondrian from Roassal, but it is different in that it is built directly out of Bloc elements. This is interesting because it allows us to combine typical widgets with visualizations. The other interesting thing about it is that it validates the design of Bloc: right now, the implementation has 509 lines of code (excluding graph-specific layouts). The goal is to make visualization a first class citizen and an integral part of the IDE. The key ingredient that made this happen is that Bloc can now treat graph layouts, such as tree or force based, behave under the same rules as typical widget layouts, such as grid or flow. The challenge comes from the fact that a graph layout depends on the notion of edges between elements, and we did not want to have elements know about edges in the core of Bloc. The solution was to split the typical edge implementation in graph visualization libraries into two distinct concepts: â¢ Line is an element that draws the connections. â¢ Edge defines constraints imposed by connections between elements. Thus, edges form constraints, and constraints are what layouts deal with. That is one reason why elements in bloc have the ability of defining layout-specific constraints. Using this, we can nicely define edges between elements as a plugin to Bloc, but still be able to connect arbitrary elements. What's more, it turns out that we need constraints for other layouts as well. For example, an element in a grid layout might specify the span. The API of GT Mondrian is similar to the one from Roassal, but there are a few differences as well. These are described in the Pillar documentation available in the GitHub repo. The best way to experience GT Mondrian and its documentation is to load the GToolkit as described here: https://github.com/feenkcom/gtoolkit If you download the GT code through Iceberg, the documentation can be experienced live by inspecting: './pharo-local/iceberg/feenkcom/gtoolkit-visualizer/doc/mondrian/index.pillar' asFileReference Cheers, The feenk team -- www.tudorgirba.com www.feenk.com "Quality cannot be an afterthought."

3 3

Re: [Pharo-dev] Two tables that share the same data source!?
by Aliaksei Syrel Dec. 9, 2017

Dec. 9, 2017

Hello Elhamer, Do you have an idea when it might be useful to have two lists representing the same datasource? We have this feature in bloc (see video in attachment) but I didn't encounter a real-life use-case yet... Cheers, Alex â Bloc-TwoListsOneDataSource.mov <https://drive.google.com/file/d/0B-bMBVDOi3oTVWpYdzF5dmlIT2Ftbm9yUVBpazNMVE…> â On 8 August 2017 at 02:16, Aliaksei Syrel <alex.syrel(a)gmail.com> wrote: > Hello Elhamer, > > Do you have an idea when it might be useful to have two lists representing > the same datasource? > We have this feature in bloc (see video in attachment) but I didn't > encounter a real-life use-case yet... > > Cheers, > Alex > > On 8 August 2017 at 01:36, Elhamer <abdelkhalekdev(a)gmail.com> wrote: > >> Hello everybody, >> >> How common is it for multiple tables (FastTables) to have the same >> datasource ? >> >> The FTDataSource has a instance variable to refer a table: >> >> ```` >> Object subclass: #FTDataSource >> instanceVariableNames: 'table' >> classVariableNames: '' >> package: 'Morphic-Widgets-FastTable-DataSource' >> ``` >> >> >> which makes it impossible for several tables to have the same data source. >> the code of the data source is also coupled to the ft code which also >> makes >> it harder to extend. >> >> I've tried to go down the rabbit hole and decouple the data source from >> the >> table but things went messy. So i would like to know how common it is for >> several tables to share the same ds, and does that worth going the extra >> mile ? >> >> Thanks, >> Elhamer. >> >> >> >> -- >> View this message in context: http://forum.world.st/Two-tabl >> es-that-share-the-same-data-source-tp4959153.html >> Sent from the Pharo Smalltalk Developers mailing list archive at >> Nabble.com. >> >> >

3 2

metalink injection into closures ?
by Ben Coman Dec. 9, 2017

Dec. 9, 2017

When we execute this... counter "Greeter new counter" | count | count := 0. [100 timesRepeat: [count := count + 1. self inform: count + 1 printString. 2 seconds wait]] forkNamed: 'Count de Money' and in the dubgger correct and save the code we normally get the message... "Method for block not found on stack, can't edit and continue." and I wonder if anything with Metalinks would facilitate inject the corrected bytecode into the Process so that it oculd continue. cheers -ben

1 0

About margin and 16969
by Stephane Ducasse Dec. 9, 2017

Dec. 9, 2017

Hi henrik I started to rescue your fix on wrong use of rectangle. Then I noticed that you change the height of a margin. We defined it as height ^ self bottom + self top Since we were considering that the height of a margin is the total amount of space around. and you as height ^ self bottom - self top Do you have a strong reason for that? Stef

1 0

Release: Conveniently browse, deactivate and reactivate halts and breakpoints with the HaltManager
by Thomas Dupriez Dec. 9, 2017

Dec. 9, 2017

Hello, I have developed a package to assist developers managing their halts and breakpoints: HaltManager. HaltManager provides a window showing all the breakpoints and halt messages of the system, and allows one to toggle them on/off with a simple click. Halt messages can also be toggled via source code rewriting. The deactivation/reactivation feature is available in all code browsers, not only in the HaltManager window. It is available here, with installation instructions and pictures: https://github.com/dupriezt/HaltManager Feedback welcome. Cheers, Thomas Dupriez

4 7

[Pharo 7.0-dev] Build #373: 20713 Cleanup RBRefactoringChangeTests
by ci-pharo-ci-jenkins2＠inria.fr Dec. 8, 2017

Dec. 8, 2017

There is a new Pharo build available! The status of the build #373 was: SUCCESS. The Pull Request #594 was integrated: "20713 Cleanup RBRefactoringChangeTests" Pull request url: https://github.com/pharo-project/pharo/pull/594 Issue Url: https://pharo.fogbugz.com/f/cases/20713 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #372: 20842-create-clear-image-entry-point-
by ci-pharo-ci-jenkins2＠inria.fr Dec. 8, 2017

Dec. 8, 2017

There is a new Pharo build available! The status of the build #372 was: SUCCESS. The Pull Request #592 was integrated: "20842-create-clear-image-entry-point-" Pull request url: https://github.com/pharo-project/pharo/pull/592 Issue Url: https://pharo.fogbugz.com/f/cases/20842 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #371: 20734-Nested-Structures-using-Platform-longs-fails
by ci-pharo-ci-jenkins2＠inria.fr Dec. 8, 2017

Dec. 8, 2017

There is a new Pharo build available! The status of the build #371 was: SUCCESS. The Pull Request #519 was integrated: "20734-Nested-Structures-using-Platform-longs-fails" Pull request url: https://github.com/pharo-project/pharo/pull/519 Issue Url: https://pharo.fogbugz.com/f/cases/20734 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Report period: 24 November 2017 to 8 December 2017
by Stephane Ducasse Dec. 8, 2017

Dec. 8, 2017

Report period: 24 November 2017 to 8 December 2017 * 20734-Nested-Structures-using-Platform-longs-fails >> Adding implementation of platform dependent longs in FFIExternalStructureReferenceHandle. >> >> Fixes https://pharo.fogbugz.com/f/cases/20734/Nested-Structures-using-Platform-lo… Issue URL: https://pharo.fogbugz.com/f/cases/20734 PR URL: https://github.com/pharo-project/pharo/pull/519 Diff URL: https://github.com/pharo-project/pharo/pull/519/files Thanks to tesonep * 20847 Super setUp need to be called in various test classes (Part 2) >> - call super setUp in HiNodesAndLinksIteratorWithOneLinkModelTest >> - call super setUp in GuideTest >> - call super setUp in SMTPClientTest >> - call super setUp in SocketStreamTest >> - call super setUp in SocketTest >> - call super setUp in ZipArchiveTest >> - call super setUp in TonelRepositoryTest >> - call super setUp in SlotMethodRecompilationTest >> - call super setUp in SmalllintManifestCheckerTest >> - call super setUp in OmSessionStoreNameStrategyTest >> - call super setUp in PharoBootstrapRuleTest >> - call super setUp in PharoIssueTest >> - call super setUp in PharoTutorialTestGoOnMockTutorial >> - call super setUp in PharoTutorialTestNavigation >> - call super setUp in UUIDGeneratorTest >> - call super setUp in TestObjectsAsMethods >> - call super setUp in TutorialPlayerTestWithMockTutorial >> - call super setUp in PNGReadWriterTest >> - call super setUp in PragmaTest >> - call super setUP in QuotedPrintableMimeConverterTest >> - call super setUP in RandomTest >> - call super setUP in RectangleTest >> - call super setUP in RecursionStopperTest >> - call super setUp in ResumableTestFailureTestCase >> - call super setUp in MTDependencyTest >> - call super setUp in MTDevelopmentWorkfowTestWithXMLParser >> - call super setUp in NautilusTest >> - call super setUp in NautilusUITest >> - call super setUp in SimpleTestResourceTestCase >> - call super setUp in SUnitTest >> - call super setUp in SimpleTestResource >> - call super setUp in GTDebuggerSmokeTest >> - call super setUp in GTPlaygroundBasicTest >> - call super setUp in GTSpotterCandidatesListTest >> - call super setUp in ZdcPluginSSLSessionTest >> - call super setUp in ZnStaticFileServerDelegateTests >> - call super setUp in ZnStaticFileServerDelegateTests >> - call super setUp in GLMAnnouncementPropagationTest >> - call super setUp in GLMAnnouncerTest >> - call super setUp in GLMExplicitBrowserCopyTest >> - call super setUp in GLMPagerModelTest >> - call super setUp in GLMUpdateMorphicTest >> - call super setUp in GLMPagerMorphTest >> >> https://pharo.fogbugz.com/f/cases/20847/Super-setUp-need-to-be-called-in-va… Issue URL: https://pharo.fogbugz.com/f/cases/20847 Super setUp need to be called in various test classes (Part 2) PR URL: https://github.com/pharo-project/pharo/pull/593 Diff URL: https://github.com/pharo-project/pharo/pull/593/files Thanks to astares * 20840 Super setUp need to be called in various test classes (Part 1) >> - call super setUp in AbstractNautilusUITest >> - call super setUp in AndreasSystemProfilerTest >> - call super setUp in ArrayTest >> - call super setUp in AssociationTest >> - call super setUp in ASTCacheResetTest >> - call super setUp in BagTest >> - call super setUp in Base64MimeConverterTest >> - call super setUp in BuilderManifestTest >> - call super setUp in CairoUTF8ConverterTest >> - call super setUp in ChangesBrowserTest >> - call super setUp in ChangeSetClassChangesTest >> - call super setUp in ClassRenameFixTest >> - call super setUp in ClassTest >> - call super setUp in TraitsResource >> - call super setUp in CollectionValueHolderTest >> - call super setUp in CommandLineArgumentsTest >> - call super setUp in CopyVisitorTest >> - call super setUp in FreeTypeCacheTest >> - call super setUp in HashAndEqualsTestCase >> - call super setUp in HeapTest >> - call super setUp in SortedCollectionTest >> - call super setUp in SortHierarchicallyTest >> - call super setUp in SetTest >> - call super setUp in StackTest >> - call super setUp in StringTest >> - call super setUp in SymbolTest >> - call super setUp in FloatArrayTest >> - call super setUp in SHStyleElementTest >> - call super setUp in HistoryIteratorTest >> - call super setUp in IntervalTest >> - call super setUp in OrderedCollectionTest >> - call super setUp in LazyTabGroupTest >> - call super setUp in MatrixTest >> - call super setUp in RPackageTestCase >> - call super setUp in ScheduleTest >> - call super setUp in SendsDeprecatedMethodToGlobalRuleTest >> - call super setUp in MorphTest >> - call super setUp in MorphicEventHandlerTest >> - call super setUp in MorphicAdapterTest >> - call super setUp in MorphicUIBugTest >> - call super setUp in CircleMorphTest Issue URL: https://pharo.fogbugz.com/f/cases/20840 Super setUp need to be called in various test classes (Part 1) PR URL: https://github.com/pharo-project/pharo/pull/590 Diff URL: https://github.com/pharo-project/pharo/pull/590/files Thanks to astares * 20838 Super setUp need to be called in System-SessionManager package tests >> - call super setUp in SessionErrorHandlingTest >> - call super setUp in SessionManagerRegistrationTest >> - call super setUp in SessionManagerUnregistrationTest >> >> https://pharo.fogbugz.com/f/cases/20838/Super-setUp-need-to-be-called-in-Sy… Issue URL: https://pharo.fogbugz.com/f/cases/20838 Super setUp need to be called in System PR URL: https://github.com/pharo-project/pharo/pull/588 Diff URL: https://github.com/pharo-project/pharo/pull/588/files Thanks to astares * 20839 Super setUp need to be called in NECompletion-Tests >> - call super setUp in NECControllerTest >> - call super setUp in NECOverrideModelTest >> - call super setUp in NECUntypedModelTest >> >> https://pharo.fogbugz.com/f/cases/20839/ Issue URL: https://pharo.fogbugz.com/f/cases/20839 Super setUp need to be called in NECompletion PR URL: https://github.com/pharo-project/pharo/pull/589 Diff URL: https://github.com/pharo-project/pharo/pull/589/files Thanks to astares * 20826 Super setup need to be called in DependencyAnalyser tests >> - call super setUp in DADependencyCheckerTest >> - call super setUp in DAMessageSendAnalyzerTest >> - call super setUp in DAPackageCycleDetectorTest (with some formatting cleanups in setUp) >> - call super setUp in DAPackageCycleTest >> - call super setUp in DAPackageDependencyTest >> - call super setUp in DAPackageDependencyWrapperTest >> - call super setUp in DAPackageRelationGraphDiffTest >> - call super setUp in DAPackageRelationGraphTest (with some formatting cleanups in setUp) >> - call super setUp in DAPackageTest (with some formatting cleanups in setUp) >> - call super setUp in DATarjanAlgorithmTest (with some formatting cleanups in setUp) >> Also add some tags to to better categorize the test classes in package "Tool-Dependency-Analyse-Test" Issue URL: https://pharo.fogbugz.com/f/cases/20826 Super setup need to be called in DependencyAnalyser tests PR URL: https://github.com/pharo-project/pharo/pull/579 Diff URL: https://github.com/pharo-project/pharo/pull/579/files Thanks to astares * 20791-World-menu-help-not-shown-in-the-menu >> Set balloonText after the spec's help. Issue URL: https://pharo.fogbugz.com/f/cases/20791 PR URL: https://github.com/pharo-project/pharo/pull/575 Diff URL: https://github.com/pharo-project/pharo/pull/575/files Thanks to luque * 20830 Super setup need to be called in Monticello tests and other cleanups (comments, tags) >> - call super setUp in MCChangeNotificationTest >> - call super setUp in MCClassDefinitionTest >> - call super setUp in MCDictionaryRepositoryTest >> - call super setUp in MCDirectoryRepositoryTest >> - call super setUp in MCFileInTest >> - call super setUp in MCMczInstallerTest >> - call super setUp in MCMethodDefinitionTest >> - call super setUp in MCPatchTest >> - call super setUp in MCSnapshotBrowserTest >> - call super setUp in MCSnapshotTest >> - call super setUp in MCStWriterTest >> - call super setUp in MCVersionTest >> - call super setUp in MCSnapshotResource (test resource) >> >> - categorize the three test methods in MCPackageManagerTest >> - Add a comment to uncommented MCTestCase >> - Add a comment to uncommented MCRepositoryTest >> - Add a comment to uncommented MCSnapshotResource >> - Add a comment to uncommented MCMockDependency >> >> - add some tags to structure the many test classes in the package better >> >> >> https://pharo.fogbugz.com/f/cases/20830/Super-setup-need-to-be-called-in-Mo… Issue URL: https://pharo.fogbugz.com/f/cases/20830 Super setup need to be called in Monticello tests and other cleanups (comments, tags) PR URL: https://github.com/pharo-project/pharo/pull/583 Diff URL: https://github.com/pharo-project/pharo/pull/583/files Thanks to astares * 20816 Typo in DateAndTimeEpochTest and DateAndTimeUnixEpochTest tearDown >> fix typo >> >> https://pharo.fogbugz.com/f/cases/20816/Typo-in-DateAndTimeEpochTest-and-Da… Issue URL: https://pharo.fogbugz.com/f/cases/20816 Typo in DateAndTimeEpochTest and DateAndTimeUnixEpochTest tearDown PR URL: https://github.com/pharo-project/pharo/pull/572 Diff URL: https://github.com/pharo-project/pharo/pull/572/files Thanks to astares * 20822 Cleanup AbstractKeymappingTest >> - override #isAbstract as it is an abstract test superclass >> - call super setUp >> - call super tearDown >> - set default to nil in tearDown to avoid further referencing Issue URL: https://pharo.fogbugz.com/f/cases/20822 Cleanup AbstractKeymappingTest PR URL: https://github.com/pharo-project/pharo/pull/577 Diff URL: https://github.com/pharo-project/pharo/pull/577/files Thanks to astares * 20820 Better formatting of TestSuite setUp >> - one blank instead of two >> - format to be more readable >> >> https://pharo.fogbugz.com/f/cases/20820/Better-formatting-of-TestSuite-setUp Issue URL: https://pharo.fogbugz.com/f/cases/20820 Better formatting of TestSuite setUp PR URL: https://github.com/pharo-project/pharo/pull/574 Diff URL: https://github.com/pharo-project/pharo/pull/574/files Thanks to astares * 20825 Super setUp need to be called in Opal Compiler tests >> - call super setUp in OCBytecodeDecompilerTest >> - call super setUp in OCClosureCompilerTest >> - call super setUp in OCCompilerExceptionTest >> - call super setUp in OCCompilerNotifyingTest >> - call super setUp in OCCompilerTest Issue URL: https://pharo.fogbugz.com/f/cases/20825 Super setUp need to be called in Opal Compiler tests PR URL: https://github.com/pharo-project/pharo/pull/578 Diff URL: https://github.com/pharo-project/pharo/pull/578/files Thanks to astares * 20819 Fix variable assignment in RBScanner>>stripComment >> https://pharo.fogbugz.com/f/cases/20819/Fix-variable-assignment-in-RBScanne… Issue URL: https://pharo.fogbugz.com/f/cases/20819 Fix variable assignment in RBScanner>>stripComment PR URL: https://github.com/pharo-project/pharo/pull/573 Diff URL: https://github.com/pharo-project/pharo/pull/573/files Thanks to astares * Fix potential dangling reference to a released FT_Face >> This is issue https://pharo.fogbugz.com/f/cases/20776/Potential-dangling-ref-to-freed-FT_… >> >> Technical details: >> >> A cairo_font_face could still be referenced from external heap and further used. >> Thus we must NOT release the FT_Face until the external reference count drops to 1. >> >> Thus the CairoFontFace is not a good place for retaining a strong reference to the FT2Face, because the reference will vanish as soon as the Smalltalk object is garbage collected, while some external cairo_font_face still point on it. >> It's better to have the strong reference in the executor, and avoid garbageCollecting the executor while there are external references to the resource data... >> >> The solution is to use a specific CairoFontFaceExecutor. >> If the resource is shared, then we have no other choice than regularly polling the ref count in a new Process. >> This process must stop whenever the session change. >> >> Please review carefully and pass some tests. Issue URL: https://pharo.fogbugz.com/f/cases/Fix potential dangling reference to a released FT_Face PR URL: https://github.com/pharo-project/pharo/pull/565 Diff URL: https://github.com/pharo-project/pharo/pull/565/files Thanks to nicolas-cellier-aka-nice * 20821 Remove unused ivar from RBKeywordToken and RBIdentifierToken >> Remove >> - unused ivar stopPosition in RBIdentifierToken and >> - unused ivar stopPosition in RBKeywordToken >> >> https://pharo.fogbugz.com/f/cases/20821/Remove-unused-ivar-from-RBKeywordTo… Issue URL: https://pharo.fogbugz.com/f/cases/20821 Remove unused ivar from RBKeywordToken and RBIdentifierToken PR URL: https://github.com/pharo-project/pharo/pull/576 Diff URL: https://github.com/pharo-project/pharo/pull/576/files Thanks to astares * 20828 Super setup need to be called in Versionner tests >> - call super setUp in MBAbstractTest >> - call super setUp in MBPackageInfoTest >> >> https://pharo.fogbugz.com/f/cases/20828/Super-setup-need-to-be-called-in-Ve… Issue URL: https://pharo.fogbugz.com/f/cases/20828 Super setup need to be called in Versionner tests PR URL: https://github.com/pharo-project/pharo/pull/581 Diff URL: https://github.com/pharo-project/pharo/pull/581/files Thanks to astares * 20829 Super setup need to be called in Spec tests >> - call super setUp in MorphicLabelAdapterTest >> - call super setUp in MorphicTreeAdapterTest >> - call super setUp in SpecInterpreterTest >> - call super setUp in SpecTestCase >> >> https://pharo.fogbugz.com/f/cases/20829/Super-setup-need-to-be-called-in-Sp… Issue URL: https://pharo.fogbugz.com/f/cases/20829 Super setup need to be called in Spec tests PR URL: https://github.com/pharo-project/pharo/pull/582 Diff URL: https://github.com/pharo-project/pharo/pull/582/files Thanks to astares * 20827 Super setUp need to be called RBParseTreeRewriterTest and RBParseTreeSearcherTest >> - call super setUp in RBParseTreeRewriterTest >> - call super setUp in RBParseTreeSearcherTest Issue URL: https://pharo.fogbugz.com/f/cases/20827 Super setUp need to be called RBParseTreeRewriterTest and RBParseTreeSearcherTest PR URL: https://github.com/pharo-project/pharo/pull/580 Diff URL: https://github.com/pharo-project/pharo/pull/580/files Thanks to astares * 20814 Add release check that we have no protocols left without methods >> Check that we have no protocols left without methods >> >> https://pharo.fogbugz.com/f/cases/20814/Add-release-check-that-we-have-no-p… Issue URL: https://pharo.fogbugz.com/f/cases/20814 Add release check that we have no protocols left without methods PR URL: https://github.com/pharo-project/pharo/pull/570 Diff URL: https://github.com/pharo-project/pharo/pull/570/files Thanks to astares * 20815 Add a release test ensuring that there are no empty packages in the i >> Add a release test ensuring that there are no empty packages in the image left >> >> https://pharo.fogbugz.com/f/cases/20815/Release-check-so-that-we-have-no-em… Issue URL: https://pharo.fogbugz.com/f/cases/20815 Add a release test ensuring that there are no empty packages in the i PR URL: https://github.com/pharo-project/pharo/pull/571 Diff URL: https://github.com/pharo-project/pharo/pull/571/files Thanks to astares * 20786-halt-messages-are-not-highlighted-in-red-as-the-other-flavours-of-halt-messages >> Added haltIfNil to the selectors to be highlighted by HaltIconStyler. >> Changed the structure of the shouldStyleNode method's code to increase clarity. Issue URL: https://pharo.fogbugz.com/f/cases/20786 PR URL: https://github.com/pharo-project/pharo/pull/569 Diff URL: https://github.com/pharo-project/pharo/pull/569/files Thanks to dupriezt * 20781-update-to-iceberg-064 >> closes issue #20781 Issue URL: https://pharo.fogbugz.com/f/cases/20781 PR URL: https://github.com/pharo-project/pharo/pull/560 Diff URL: https://github.com/pharo-project/pharo/pull/560/files Thanks to estebanlm * 20793-During-Bootstrap-if-a-baseline-installation-fails-it-should-cancel-the-process >> This PR introduces two changes to handle the errors during the bootstrap: >> >> 1. The Whole process now has a timeout of 60 minutes. >> 2. After initializing the world in BaselineOfMorphic the UIManager is restored to the correct UIManager depending the system state. If it is headless then the NonInteractiveManager is used, otherwise the MorphicUIManager. Issue URL: https://pharo.fogbugz.com/f/cases/20793 PR URL: https://github.com/pharo-project/pharo/pull/567 Diff URL: https://github.com/pharo-project/pharo/pull/567/files Thanks to tesonep * 20800-do-not-open-welcome-window-for-now >> https://pharo.fogbugz.com/f/cases/20800/do-not-open-welcome-window-for-now >> >> do not open the welcome window Issue URL: https://pharo.fogbugz.com/f/cases/20800 PR URL: https://github.com/pharo-project/pharo/pull/568 Diff URL: https://github.com/pharo-project/pharo/pull/568/files Thanks to pavel-krivanek * 20786-halt-messages-are-not-highlighted-in-red-as-the-other-flavours-of-halt-messages >> Created HaltColonIconStylerClass, to style `halt:` message nodes with red highlighting in code browsers. Issue URL: https://pharo.fogbugz.com/f/cases/20786 PR URL: https://github.com/pharo-project/pharo/pull/564 Diff URL: https://github.com/pharo-project/pharo/pull/564/files Thanks to dupriezt * 20782-CompiledCode-misses-an-abstract-sourcePointer-method >> introduced CompiledCode>>sourcePointer as an abstract method Issue URL: https://pharo.fogbugz.com/f/cases/20782 PR URL: https://github.com/pharo-project/pharo/pull/561 Diff URL: https://github.com/pharo-project/pharo/pull/561/files Thanks to LucFabresse * -20785/Fix-the-names-of-uploaded-bootstrap-zip-files >> https://pharo.fogbugz.com/f/cases/20785/Fix-the-names-of-uploaded-bootstrap… Issue URL: https://pharo.fogbugz.com/f/cases/ PR URL: https://github.com/pharo-project/pharo/pull/563 Diff URL: https://github.com/pharo-project/pharo/pull/563/files Thanks to pavel-krivanek * 20783-upload-temporary-building-files-into-a-separate-repository >> https://pharo.fogbugz.com/f/cases/20783/upload-temporary-building-files-int… Issue URL: https://pharo.fogbugz.com/f/cases/20783 PR URL: https://github.com/pharo-project/pharo/pull/562 Diff URL: https://github.com/pharo-project/pharo/pull/562/files Thanks to pavel-krivanek * 20777-Fix-instVarAt-instVarAt-put-comment >> https://pharo.fogbugz.com/f/cases/20777/Fix-instVarAt-instVarAt-put-comment >> >> http://forum.world.st/Problem-with-primitive-instVarAt-instVarAt-put-what-s… Issue URL: https://pharo.fogbugz.com/f/cases/20777 PR URL: https://github.com/pharo-project/pharo/pull/559 Diff URL: https://github.com/pharo-project/pharo/pull/559/files Thanks to clementbera * 20772 - Unused temps in MBConfigurationInfo, MethodDictionaryTest,... >> Fix unused temps in >> >> MethodDictionaryTest>>#testIdentityKeyAtNonExistantValueReturnsFailBlock >> MBConfigurationInfo>>#buildStringOrText >> MBPackageInfo>>#versions >> MCFileTreeRepository class>>#parseName:extension: >> MCWorkingCopyBrowser>>#addRepositoryToPackage >> MethodDictionaryTest>>#testGrowPreservesElements Issue URL: https://pharo.fogbugz.com/f/cases/20772 PR URL: https://github.com/pharo-project/pharo/pull/557 Diff URL: https://github.com/pharo-project/pharo/pull/557/files Thanks to astares * 20745-cleanup-unused-methods-OCOptimizedBlockScope >> cleanup unused methods OCOptimizedBlockScope >> >> https://pharo.fogbugz.com/f/cases/20745/cleanup-unused-methods-OCOptimizedB… Issue URL: https://pharo.fogbugz.com/f/cases/20745 PR URL: https://github.com/pharo-project/pharo/pull/556 Diff URL: https://github.com/pharo-project/pharo/pull/556/files Thanks to MarcusDenker * 20700-translateToUTC-does-not-work-on-Month-and-Year >> 20700 translateToUTC does not work on Month and Year >> >> Update Year>>starting:duration: and Month>>starting:duration: to keep the supplied DateAndTime's offset. >> >> Add automated tests to Year, Month and Week to confirm correct operation. Issue URL: https://pharo.fogbugz.com/f/cases/20700 PR URL: https://github.com/pharo-project/pharo/pull/545 Diff URL: https://github.com/pharo-project/pharo/pull/545/files Thanks to akgrant43 * 20770-Open-WelcomeHelp-window-at-startup >> https://pharo.fogbugz.com/f/cases/20770/Open-WelcomeHelp-window-at-startup >> >> open WelcomeHelp on startup Issue URL: https://pharo.fogbugz.com/f/cases/20770 PR URL: https://github.com/pharo-project/pharo/pull/555 Diff URL: https://github.com/pharo-project/pharo/pull/555/files Thanks to pavel-krivanek * 20769-DateAndTime-now-returns-summer-time-in-winter-France-time-zone >> https://pharo.fogbugz.com/f/cases/20769/DateAndTime-now-returns-summer-time… >> >> add missing startup list registrations Issue URL: https://pharo.fogbugz.com/f/cases/20769 PR URL: https://github.com/pharo-project/pharo/pull/553 Diff URL: https://github.com/pharo-project/pharo/pull/553/files Thanks to pavel-krivanek * 19304-anyOne-comment-should-be-improved >> https://pharo.fogbugz.com/f/cases/19304/ >> >> improve #anyOne comment Issue URL: https://pharo.fogbugz.com/f/cases/19304 PR URL: https://github.com/pharo-project/pharo/pull/552 Diff URL: https://github.com/pharo-project/pharo/pull/552/files Thanks to pavel-krivanek * 20768-remove-GLMWatcherMorphicTest >> https://pharo.fogbugz.com/f/cases/20768/remove-GLMWatcherMorphicTest >> >> remove GLMWatcherMorphicTest Issue URL: https://pharo.fogbugz.com/f/cases/20768 PR URL: https://github.com/pharo-project/pharo/pull/551 Diff URL: https://github.com/pharo-project/pharo/pull/551/files Thanks to pavel-krivanek * 20738 dictionarystore string generates incorrect source code when a negative number is in values Issue URL: https://pharo.fogbugz.com/f/cases/20738 dictionarystore string generates incorrect source code when a negative number is in values PR URL: https://github.com/pharo-project/pharo/pull/538 Diff URL: https://github.com/pharo-project/pharo/pull/538/files Thanks to juliendelplanque * 20767-Decrease-retry-times-for-failing-jobs >> https://pharo.fogbugz.com/f/cases/20767/Decrease-retry-times-for-failing-jo… Issue URL: https://pharo.fogbugz.com/f/cases/20767 PR URL: https://github.com/pharo-project/pharo/pull/550 Diff URL: https://github.com/pharo-project/pharo/pull/550/files Thanks to pavel-krivanek * 20758-Slot-should-have-explicit-property-definingClass2 >> definingClass is added to Slot. >> It is initialized in ClassDescription>>superclass:layout: >> SlotIntegrationTest>>testSlotsAreInitializedWithDefiningAnonimousClass covers that initialization is performed. >> >> https://pharo.fogbugz.com/f/cases/20758/Slot-should-have-explicit-property-… Issue URL: https://pharo.fogbugz.com/f/cases/20758 PR URL: https://github.com/pharo-project/pharo/pull/543 Diff URL: https://github.com/pharo-project/pharo/pull/543/files Thanks to dionisiydk * 20747-Date-comparisons-without-time-zone >> 20747 Date comparisons without time zone >> >> Add time zone independent comparisons to Date. Issue URL: https://pharo.fogbugz.com/f/cases/20747 PR URL: https://github.com/pharo-project/pharo/pull/544 Diff URL: https://github.com/pharo-project/pharo/pull/544/files Thanks to akgrant43 * 20766-Increase-priority-of-FreeType-initialization >> https://pharo.fogbugz.com/f/cases/20766/Increase-priority-of-FreeType-initi… >> >> increase priority of FreeType initialization Issue URL: https://pharo.fogbugz.com/f/cases/20766 PR URL: https://github.com/pharo-project/pharo/pull/548 Diff URL: https://github.com/pharo-project/pharo/pull/548/files Thanks to pavel-krivanek * 20699-Convenience-method-for-creating-typed-buffers-to-pass-by-ref-through-FFI- >> https://pharo.fogbugz.com/f/cases/20699/Convenience-method-for-creating-typ… Issue URL: https://pharo.fogbugz.com/f/cases/20699 PR URL: https://github.com/pharo-project/pharo/pull/508 Diff URL: https://github.com/pharo-project/pharo/pull/508/files Thanks to estebanlm * 20759 Unused temps in Metacello classes >> Fix unused temps >> >> MetacelloMCProjectSpec>>#determineCurrentVersionForLoad >> MetacelloToolBox class>>#defaultTopic:for: >> MetacelloToolBox>>#commitBaselineOfMethod >> MetacelloToolBox>>#commitMethod >> MetacelloToolBox>>#updateVersionMethodForVersion:projectAttributes:updateProjects:updatePackages:versionSpecsDo: >> MetacelloToolBoxConstructor>>#extractSymbolicVersionSpecsFor: >> MetacelloVersionSpec>>#configMethodOn:last:indent: >> MetacelloMCVersion>>#executeLoadFromArray: >> MetacelloMCVersionValidator>>#validateProjectVersionLoad:loads: >> MetacelloMemberListSpec>>#mergeSpec: >> MetacelloPackageSpec>>#currentPackageLoaded:notLoaded:using: >> MetacelloPackageSpec>>#mergeSpec: >> MetacelloProject>>#version: >> MetacelloScriptEngine>>#lookupProjectSpecFor: >> MetacelloSemanticVersionNumber class>>#fromString:forPattern: Issue URL: https://pharo.fogbugz.com/f/cases/20759 Unused temps in Metacello classes PR URL: https://github.com/pharo-project/pharo/pull/546 Diff URL: https://github.com/pharo-project/pharo/pull/546/files Thanks to astares * 20763 ExternalAddress>>finalize should be in finalization protocol >> Put finalize into finalization category to satisfy ProperMethodCategorizationTest >> >> https://pharo.fogbugz.com/f/cases/edit/20763/ExternalAddress-finalize-shoul… Issue URL: https://pharo.fogbugz.com/f/cases/20763 ExternalAddress>>finalize should be in finalization protocol PR URL: https://github.com/pharo-project/pharo/pull/547 Diff URL: https://github.com/pharo-project/pharo/pull/547/files Thanks to astares * 20061-Explicit-isAbstract-is-needed-instead-of-using-hasAbstractMethods-in-tools2 >> https://pharo.fogbugz.com/f/cases/20061/Explicit-isAbstract-is-needed-inste… >> >> Few things are done: >> - Behavior and friends define isAbstract method with optimized logic. >> It gives 50 milliseconds for the test: >> [50 timesRepeat: [ PluggableTextMorph isAbstract]] timeToRun. >> 50 items is much more then we able to see in browser class list. So it should not affect browser speed. >> - BehaviorTest>>testIsAbstract >> - CompiledMethod>>isAbstract is now take into account traits explicit and implicit requirement. >> - Nautilus uses #isAbstract instead of hasAbstractMethods to mark abstract classes Issue URL: https://pharo.fogbugz.com/f/cases/20061 PR URL: https://github.com/pharo-project/pharo/pull/541 Diff URL: https://github.com/pharo-project/pharo/pull/541/files Thanks to dionisiydk * 20740-Work-Needed-isAbstract-not-working-correctly-on-64bit >> Fixed markerOrNil to work on both bytecode sets for 64 bits and 32 bits. >> >> https://pharo.fogbugz.com/f/cases/20740 Issue URL: https://pharo.fogbugz.com/f/cases/20740 PR URL: https://github.com/pharo-project/pharo/pull/537 Diff URL: https://github.com/pharo-project/pharo/pull/537/files Thanks to clementbera * 20176-Error-in-ByteArraybooleanAt >> Fix ByteArray>>#booleanAt: to actually return true when the byte at the querried position in the ByteArray is a non-zero integer Issue URL: https://pharo.fogbugz.com/f/cases/20176 PR URL: https://github.com/pharo-project/pharo/pull/539 Diff URL: https://github.com/pharo-project/pharo/pull/539/files Thanks to dupriezt * 20756-Secondary-selections-are-dark-after-switch-to-the-white-theme-in-Pharo-7 >> https://pharo.fogbugz.com/f/cases/20756/Secondary-selections-are-dark-after… >> >> change default secondary selection color Issue URL: https://pharo.fogbugz.com/f/cases/20756 PR URL: https://github.com/pharo-project/pharo/pull/540 Diff URL: https://github.com/pharo-project/pharo/pull/540/files Thanks to pavel-krivanek * 20690-assertequals >> https://pharo.fogbugz.com/f/cases/20690/assert-equals >> >> - swap actual and experted sides in comparig inside assert:equals: >> - deprecate assert:descriptionBlock: Issue URL: https://pharo.fogbugz.com/f/cases/20690 PR URL: https://github.com/pharo-project/pharo/pull/533 Diff URL: https://github.com/pharo-project/pharo/pull/533/files Thanks to pavel-krivanek * 20729-Monticello-history-browser-should-enable-diffing-with-parent >> This is issue https://pharo.fogbugz.com/f/cases/20729/Monticello-history-browser-should-e… >> Such option is really handy when cherry picking changes from other branches >> Pick the implementation from Squeak (fbs, eem) and adapt to Pharo Issue URL: https://pharo.fogbugz.com/f/cases/20729 PR URL: https://github.com/pharo-project/pharo/pull/513 Diff URL: https://github.com/pharo-project/pharo/pull/513/files Thanks to nicolas-cellier-aka-nice

1 0

[Pharo 7.0-dev] Build #370: 20847 Super setUp need to be called in various test classes (Part 2)
by ci-pharo-ci-jenkins2＠inria.fr Dec. 8, 2017

Dec. 8, 2017

There is a new Pharo build available! The status of the build #370 was: SUCCESS. The Pull Request #593 was integrated: "20847 Super setUp need to be called in various test classes (Part 2)" Pull request url: https://github.com/pharo-project/pharo/pull/593 Issue Url: https://pharo.fogbugz.com/f/cases/20847 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #369: 20840 Super setUp need to be called in various test classes (Part 1)
by ci-pharo-ci-jenkins2＠inria.fr Dec. 8, 2017

Dec. 8, 2017

There is a new Pharo build available! The status of the build #369 was: SUCCESS. The Pull Request #590 was integrated: "20840 Super setUp need to be called in various test classes (Part 1)" Pull request url: https://github.com/pharo-project/pharo/pull/590 Issue Url: https://pharo.fogbugz.com/f/cases/20840 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #368: 20838 Super setUp need to be called in System-SessionManager package tests
by ci-pharo-ci-jenkins2＠inria.fr Dec. 8, 2017

Dec. 8, 2017

There is a new Pharo build available! The status of the build #368 was: SUCCESS. The Pull Request #588 was integrated: "20838 Super setUp need to be called in System-SessionManager package tests" Pull request url: https://github.com/pharo-project/pharo/pull/588 Issue Url: https://pharo.fogbugz.com/f/cases/20838 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #367: 20839 Super setUp need to be called in NECompletion-Tests
by ci-pharo-ci-jenkins2＠inria.fr Dec. 8, 2017

Dec. 8, 2017

There is a new Pharo build available! The status of the build #367 was: SUCCESS. The Pull Request #589 was integrated: "20839 Super setUp need to be called in NECompletion-Tests" Pull request url: https://github.com/pharo-project/pharo/pull/589 Issue Url: https://pharo.fogbugz.com/f/cases/20839 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

2 1

Crash Dump - GT loaded into 6.1
by Sean P. DeNigris Dec. 8, 2017

Dec. 8, 2017

Let me know if you need any other infoâ¦ Image ----- Pharo6.0 Latest update: #60523 Unnamed Virtual Machine --------------- ~/Documents/Pharo/vms/61-x86/Pharo.app/Contents/MacOS/Pharo CoInterpreter VMMaker.oscog-eem.2254 uuid: 4f2c2cce-f4a2-469a-93f1-97ed941df0ad Jul 20 2017 StackToRegisterMappingCogit VMMaker.oscog-eem.2252 uuid: 2f3e9b0e-ecd3-4adf-b092-cce2e2587a5c Jul 20 2017 VM: 201707201942 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ Date: Thu Jul 20 12:42:21 2017 -0700 $ Plugins: 201707201942 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ Mac OS X built on Jul 20 2017 21:45:23 UTC Compiler: 4.2.1 Compatible Apple LLVM 6.1.0 (clang-602.0.53) VMMaker versionString VM: 201707201942 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ Date: Thu Jul 20 12:42:21 2017 -0700 $ Plugins: 201707201942 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ CoInterpreter VMMaker.oscog-eem.2254 uuid: 4f2c2cce-f4a2-469a-93f1-97ed941df0ad Jul 20 2017 StackToRegisterMappingCogit VMMaker.oscog-eem.2252 uuid: 2f3e9b0e-ecd3-4adf-b092-cce2e2587a5c Jul 20 2017 *Here's the top part of the dmp:* Bus error VM: 201707201942 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ Date: Thu Jul 20 12:42:21 2017 -0700 $ Plugins: 201707201942 https://github.com/OpenSmalltalk/opensmalltalk-vm.git $ C stack backtrace & registers: eax 0x6b50fd00 ebx 0x6dd03c90 ecx 0x88bb0000 edx 0x012f39a0 edi 0x6dd03c30 esi 0x6dd03c30 ebp 0xbff89a88 esp 0xbff89a7c eip 0x88bb0000 0 ??? 0x88bb0000 0x0 + 2293956608 1 Pharo 0x000c5460 reportStackState + 819 2 Pharo 0x000c57e6 sigsegv + 163 3 libsystem_platform.dylib 0xa778202b _sigtramp + 43 4 ??? 0xffffffff 0x0 + 4294967295 5 libMoz2D.dylib 0x1394b9d3 _ZN12PLDHashTableD1Ev + 67 6 libMoz2D.dylib 0x13b9e492 _ZN21nsLanguageAtomService7ReleaseEv + 82 7 libMoz2D.dylib 0x138dd879 _ZN19gfxPlatformFontListD2Ev + 377 8 libMoz2D.dylib 0x13902881 _ZN22gfxMacPlatformFontListD0Ev + 17 9 libMoz2D.dylib 0x13877839 _ZN11gfxPlatform8ShutdownEv + 73 10 Pharo 0x000fb3d2 primitiveCalloutWithArgs + 1748 11 Pharo 0x00055357 executeNewMethod + 144 12 Pharo 0x00056187 ceSendsupertonumArgs + 1017 13 ??? 0x061310a3 0x0 + 101912739 14 Pharo 0x000403ab interpret + 646 15 Pharo 0x000c69d9 -[sqSqueakMainApplication runSqueak] + 476 16 Foundation 0x953897ec __NSFirePerformWithOrder + 432 17 CoreFoundation 0x9392a216 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 22 18 CoreFoundation 0x9392a132 __CFRunLoopDoObservers + 498 19 CoreFoundation 0x9390d5ed __CFRunLoopRun + 1661 20 CoreFoundation 0x9390cc41 CFRunLoopRunSpecific + 641 21 CoreFoundation 0x9390c9aa CFRunLoopRunInMode + 122 22 HIToolbox 0x92f0dd3b RunCurrentEventLoopInMode + 321 23 HIToolbox 0x92f0d91f ReceiveNextEventCommon + 454 24 HIToolbox 0x92f0d73b _BlockUntilNextEventMatchingListInModeWithFilter + 71 25 AppKit 0x9136538d _DPSNextEvent + 2101 26 AppKit 0x91ad6c74 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 2859 27 AppKit 0x91ad6141 -[NSApplication(NSEvent) nextEventMatchingMask:untilDate:inMode:dequeue:] + 134 28 AppKit 0x9135a2e1 -[NSApplication run] + 763 29 AppKit 0x9132c2f2 NSApplicationMain + 1228 30 libdyld.dylib 0xa7502711 start + 1 Smalltalk stack dump: 0xbffa09e4 M MozServices class>primShutdownPlatform 0xb45b538: a(n) MozServices class 0xbffa0a10 I FFICalloutAPI>function:module: 0x642b5a0: a(n) FFICalloutAPI 0xbffa0a38 I MozServices class(Object)>ffiCall: 0xb45b538: a(n) MozServices class 0xbffa0a5c I MozServices class>primShutdownPlatform 0xb45b538: a(n) MozServices class 0xbffa0a74 M [] in MozServices class>stop 0xb45b538: a(n) MozServices class 0xbffa0a94 M BlockClosure>ensure: 0x641e930: a(n) BlockClosure 0xbffa0ab8 I MozServices class>stop 0xb45b538: a(n) MozServices class 0xbffa0ad8 I MozServices class>shutDown: 0xb45b538: a(n) MozServices class 0xbffa0af4 M ClassSessionHandler>shutdown: 0xb7c7dc8: a(n) ClassSessionHandler 0xbffa0b14 M [] in WorkingSession>runShutdown: 0x8c5c0f8: a(n) WorkingSession 0xbffa0b38 M [] in WorkingSession>runList:do: 0x8c5c0f8: a(n) WorkingSession 0xbffa0b50 M BlockClosure>on:do: 0x641e770: a(n) BlockClosure 0xbffa0b74 M [] in WorkingSession>runList:do: 0x8c5c0f8: a(n) WorkingSession 0xbffa0b98 M Array(SequenceableCollection)>do: 0x641df40: a(n) Array 0xbffa0bbc I WorkingSession>runList:do: 0x8c5c0f8: a(n) WorkingSession 0xbffa0be4 I WorkingSession>runShutdown: 0x8c5c0f8: a(n) WorkingSession 0xbffa0c08 I WorkingSession>stop: 0x8c5c0f8: a(n) WorkingSession 0xbffa0c34 I SessionManager>snapshot:andQuit: 0x8248590: a(n) SessionManager 0xbffa0c64 I [] in SmalltalkImage>snapshot:andQuit: 0x6c0bf40: a(n) SmalltalkImage ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

2 3

ANN: Pharo6.1 new release (I do not remember how this subject was)
by Esteban Lorenzano Dec. 7, 2017

Dec. 7, 2017

So, I made a couple of changes: 20784 update Metacello since last update failed https://pharo.fogbugz.com/f/cases/20784 <https://pharo.fogbugz.com/f/cases/20784> and from a previous integration: 20176 Error in ByteArray>>booleanAt: https://pharo.fogbugz.com/f/cases/20176 <https://pharo.fogbugz.com/f/cases/20176> 20762 Pharo 6.1 has `pharo6.0.x` platform attribute instead of `pharo6.1.x` https://pharo.fogbugz.com/f/cases/20762 <https://pharo.fogbugz.com/f/cases/20762> 20103 Minor glitch in source code diff tool https://pharo.fogbugz.com/f/cases/20103 <https://pharo.fogbugz.com/f/cases/20103> So, the recent problems should be fixed. Now I can backport iceberg 0.6.4 :) cheers! Esteban

2 1

Is Pharo spying on me?
by Bernhard Pieber Dec. 7, 2017

Dec. 7, 2017

I just found a file named org.pharo.global-identifiers.ston in my preferences folder. It contains a #secretUUID and a #computerUUID. :-( What is this information used for? More importantly, how can I turn it off? Bernhard

11 16

[Pharo 7.0-dev] Build #366: 20826 Super setup need to be called in DependencyAnalyser tests
by ci-pharo-ci-jenkins2＠inria.fr Dec. 7, 2017

Dec. 7, 2017

There is a new Pharo build available! The status of the build #366 was: SUCCESS. The Pull Request #579 was integrated: "20826 Super setup need to be called in DependencyAnalyser tests" Pull request url: https://github.com/pharo-project/pharo/pull/579 Issue Url: https://pharo.fogbugz.com/f/cases/20826 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #365: 20830 Super setup need to be called in Monticello tests and other cleanups (comments, tags)
by ci-pharo-ci-jenkins2＠inria.fr Dec. 7, 2017

Dec. 7, 2017

There is a new Pharo build available! The status of the build #365 was: SUCCESS. The Pull Request #583 was integrated: "20830 Super setup need to be called in Monticello tests and other cleanups (comments, tags)" Pull request url: https://github.com/pharo-project/pharo/pull/583 Issue Url: https://pharo.fogbugz.com/f/cases/20830 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #364: 20816 Typo in DateAndTimeEpochTest and DateAndTimeUnixEpochTest tearDown
by ci-pharo-ci-jenkins2＠inria.fr Dec. 7, 2017

Dec. 7, 2017

There is a new Pharo build available! The status of the build #364 was: FAILURE. The Pull Request #572 was integrated: "20816 Typo in DateAndTimeEpochTest and DateAndTimeUnixEpochTest tearDown" Pull request url: https://github.com/pharo-project/pharo/pull/572 Issue Url: https://pharo.fogbugz.com/f/cases/20816 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Running tests in MCMethodDefinitionTest
by Torsten Bergmann Dec. 7, 2017

Dec. 7, 2017

Hi, a little story: while working on cleaning up MCMethodDefinitionTest (see https://pharo.fogbugz.com/f/cases/20830) I noticed that from time to time you have trouble when running the test methods in this class one after the other several times. So sometimes it worked and sometimes not. I wondered since the latest Pharo 7 build #70360 is definitely green on CI, so the tests seem to work. After investigating I've noticed that in MCMethodDefinitionTest>>tearDown a package "FooBarBaz" which is used during the tests is unregistered and (when you run another test from this suite right afterwards) is not found anymore. Because in the test initialization it is not. This is easily fixed with setting the package up in the #setUp method which is unregistered in #tearDown and one can easily run the tests several times independently. So if one had trouble in Pharo 6 and Pharo 7 with sporadic fails in Monticello tests this might have been the cause. The fix is part of PR https://github.com/pharo-project/pharo/pull/583 Bye T.

3 2

[Pharo 7.0-dev] Build #363: 20825 Super setUp need to be called in Opal Compiler tests
by ci-pharo-ci-jenkins2＠inria.fr Dec. 7, 2017

Dec. 7, 2017

There is a new Pharo build available! The status of the build #363 was: SUCCESS. The Pull Request #578 was integrated: "20825 Super setUp need to be called in Opal Compiler tests" Pull request url: https://github.com/pharo-project/pharo/pull/578 Issue Url: https://pharo.fogbugz.com/f/cases/20825 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #362: 20819 Fix variable assignment in RBScanner>>stripComment
by ci-pharo-ci-jenkins2＠inria.fr Dec. 7, 2017

Dec. 7, 2017

There is a new Pharo build available! The status of the build #362 was: SUCCESS. The Pull Request #573 was integrated: "20819 Fix variable assignment in RBScanner>>stripComment" Pull request url: https://github.com/pharo-project/pharo/pull/573 Issue Url: https://pharo.fogbugz.com/f/cases/20819 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Next OpenSmalltalkVM Release Planned For February 1
by Torsten Bergmann Dec. 7, 2017

Dec. 7, 2017

see http://forum.world.st/ANN-Next-OpenSmalltalkVM-Release-Planned-For-February… What does it mean for Pharo-VM and release planning? Thx T.

1 0

[Pharo 7.0-dev] Build #361: 20827 Super setUp need to be called RBParseTreeRewriterTest and RBParseTreeSearcherTest
by ci-pharo-ci-jenkins2＠inria.fr Dec. 7, 2017

Dec. 7, 2017

There is a new Pharo build available! The status of the build #361 was: SUCCESS. The Pull Request #580 was integrated: "20827 Super setUp need to be called RBParseTreeRewriterTest and RBParseTreeSearcherTest" Pull request url: https://github.com/pharo-project/pharo/pull/580 Issue Url: https://pharo.fogbugz.com/f/cases/20827 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Corrupt method source in Pharo 6.1 (stable)
by Bernhard Pieber Dec. 6, 2017

Dec. 6, 2017

I did the following in Pharo Launcher: 1. Select Official distributions > Pharo 6.1 (stable) 2. Click Create Image 3. Launch created image 4. Browse GLMAccumulator 5. Click on any method, e.g. activeEntity => method source is corrupt, e.g. mp: âtg 2/2/2010 22:03' I tried it twice, also with the Pharo 6.0 > latest image. Can anyone else confirm that? Bernhard

3 4

[Pharo 7.0-dev] Build #360: 20814 Add release check that we have no protocols left without methods
by ci-pharo-ci-jenkins2＠inria.fr Dec. 6, 2017

Dec. 6, 2017

There is a new Pharo build available! The status of the build #360 was: SUCCESS. The Pull Request #570 was integrated: "20814 Add release check that we have no protocols left without methods" Pull request url: https://github.com/pharo-project/pharo/pull/570 Issue Url: https://pharo.fogbugz.com/f/cases/20814 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #359: 20815 Add a release test ensuring that there are no empty packages in the i
by ci-pharo-ci-jenkins2＠inria.fr Dec. 6, 2017

Dec. 6, 2017

There is a new Pharo build available! The status of the build #359 was: SUCCESS. The Pull Request #571 was integrated: "20815 Add a release test ensuring that there are no empty packages in the i" Pull request url: https://github.com/pharo-project/pharo/pull/571 Issue Url: https://pharo.fogbugz.com/f/cases/20815 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Re: [Pharo-dev] Is Pharo spying on me?
by Tudor Girba Dec. 6, 2017

Dec. 6, 2017

Hi, An interesting point. However, just because other people behave less nicely does not mean we should be the same. Principles should always remain principles regardless of how inconvenient or apparently insignificant the situation is. Cheers, Doru > On Dec 6, 2017, at 12:00 PM, Benoit St-Jean via Pharo-dev <pharo-dev(a)lists.pharo.org> wrote: > > > From: Benoit St-Jean <bstjean(a)yahoo.com> > Subject: Re: [Pharo-dev] Is Pharo spying on me? > Date: December 6, 2017 at 12:00:31 PM GMT+1 > To: Pharo Development List <pharo-dev(a)lists.pharo.org> > Reply-To: Benoit St-Jean <bstjean(a)yahoo.com> > > > Let's not panic here! > > Funny to see people worry so much about privacy from a tool that collects technical data anonymously when a gazillion agencies (especially NSA) keep track of every email and phone call we do!!! > > ----------------- > BenoÃ®t St-Jean > Yahoo! Messenger: bstjean > Twitter: @BenLeChialeux > Pinterest: benoitstjean > Instagram: Chef_Benito > IRC: lamneth > Blogue: endormitoire.wordpress.com > "A standpoint is an intellectual horizon of radius zero". (A. Einstein) > > > From: Tudor Girba <tudor(a)tudorgirba.com> > To: Pharo Development List <pharo-dev(a)lists.pharo.org> > Sent: Wednesday, December 6, 2017 1:13 AM > Subject: Re: [Pharo-dev] Is Pharo spying on me? > > Hi, > > What exactly are we removing? > > Cheers, > Doru > > > > On Dec 5, 2017, at 9:41 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > > > but you are asked to share it, this is not collected automatically without asking before. > > > > anyway, we are removing that (if not removed yet) > > > >> On 5 Dec 2017, at 21:34, Sean Glazier <sglazier456(a)gmail.com> wrote: > >> > >> Personally, I know of work places where this is not going to be allowed. I understand they need the data, but you need to be able to turn it off. A secure facility would not allow the transmission out in any case. > >> > >> > >> Kind Regards, > >> > >> Sean Glazier > >> > >> > >> On Tue, Dec 5, 2017 at 2:45 PM, Juraj Kubelka <juraj.kubelka(a)icloud.com> wrote: > >> Check Privacy section in Settings Browser. > >> If you ever send anything, data are anonymized. > >> Developers use it to be able to evaluate their research (PhD) work. It is a requirement in the research field. > >> By sending the anonymized data, you help developers to understand how their tools are used. > >> In particular, I am aware of Spotter, Quality Assistant, GT tools, and Roassal. > >> > >> Cheers, > >> Juraj > >> > >> > On Dec 5, 2017, at 16:30, Bernhard Pieber <bernhard(a)pieber.com> wrote: > >> > > >> > I just found a file named org.pharo.global-identifiers.ston in my preferences folder. It contains a #secretUUID and a #computerUUID. :-( What is this information used for? More importantly, how can I turn it off? > >> > > >> > Bernhard > >> > >> > >> > > > > -- > www.tudorgirba.com > www.feenk.com > > "Next time you see your life passing by, say 'hi' and get to know her." > > > > > > > > Virus-free. www.avg.com > > -- www.tudorgirba.com www.feenk.com "What we can governs what we wish."

1 0

Re: [Pharo-dev] How to get a Moose Model
by Tudor Girba Dec. 6, 2017

Dec. 6, 2017

Hi, Thanks for the question. Please address this to the moose-dev mailing list (in CC): https://www.list.inf.unibe.ch/listinfo/moose-dev I just answered it there. Cheers, Doru > On Dec 5, 2017, at 4:44 PM, Moussa Saker via Pharo-dev <pharo-dev(a)lists.pharo.org> wrote: > > > From: Moussa Saker <sak_moussa(a)yahoo.fr> > Subject: How to get a Moose Model > Date: December 5, 2017 at 4:44:31 PM GMT+1 > To: "pharo-dev(a)lists.pharo.org" <pharo-dev(a)lists.pharo.org> > Reply-To: Moussa Saker <sak_moussa(a)yahoo.fr> > > > Hello everyone > > we are working on a Moose project and we need a script to import the Moose Model, right now we use: > > MooseModel root first , > > but it's not really practical, Any suggestions ? > > Moussa Saker > LISCO Laboratory > Badji Mokhtar-Annaba University, > P.O. Box 12, Annaba 23000, Algeriai n > > -- www.tudorgirba.com www.feenk.com "To lead is not to demand things, it is to make them happen."

1 0

How to get a Moose Model
by Moussa Saker Dec. 5, 2017

Dec. 5, 2017

Hello everyoneÂ we are working on a Moose project andÂ we need a script to importÂ the Moose Model, right now we use:Â MooseModel root first , Â but it's not really practical, Any suggestions ? Moussa Saker LISCO Laboratory Badji Mokhtar-Annaba University, P.O. Box 12, Annaba 23000, Algeriai n

1 0

using Pharo 7 from Pharo Launcher gives warning about changes file
by Nicolai Hess Dec. 5, 2017

Dec. 5, 2017

Just reinstalled pharo launcher new. Select the Pharo 7 (development version) entry, create an image and start it. It always shows a warning about the changes : " Pharo cannot write to the changes file named C:\Users\nicolai\Documents\Pharo\images\Pharo 7.0 (development version)\Pharo 7.0 (development version).changes. Please check that you have write permission for this file. You won't be able to save this image correctly until you fix this." But I can save the image, and reopening gives the same message. I don't know if this is an Pharo 7 or a Pharo Launcher issue, but starting a pharo 6.1 image does not give this message. nicolai

2 1

feenk log
by Tudor Girba Dec. 5, 2017

Dec. 5, 2017

Hi, Here is an update of the work on Bloc and GT: Bloc: - Bezier curves (cubic and quadratic). https://twitter.com/feenkcom/status/934765444464021504 https://twitter.com/feenkcom/status/934856909001252865 - Dragging is now possible through a BlDragHandler that can be attached to any element. - Pixel accurate line heads and tails https://twitter.com/feenkcom/status/936704646290305025 - More flexible scalable element. https://twitter.com/feenkcom/status/934003681539907585 - Improved scalability of the rendering. For example, on Mac, we are on par with the speed of Firefox. https://twitter.com/feenkcom/status/931462535861108736 - Sparta is now able to load custom fonts. https://twitter.com/feenkcom/status/930919637214285824 - Text insertion works now much better. Deletion and Selection still require more work. - The rope data structure can now be better inspected. https://twitter.com/feenkcom/status/937298739584172032 - Sparta/Moz2D has a visual loader that also provides more specific details in case of errors. https://twitter.com/feenkcom/status/936501909581688832 - Moz2D is now installed by default on Linux 64b. GT: - The GT Visualizer sub-project now contains two tools: -- GT Mondrian is a graph visualization engine that is both performant and shows how Bloc works well for visualizations. More details in a follow up post. https://twitter.com/feenkcom/status/937682660704563202 -- GT Connector is a new tool for browsing connected examples. More details about it in a follow up post. https://twitter.com/feenkcom/status/936109463462965248 Enjoy, The feenk team -- www.tudorgirba.com www.feenk.com "If you can't say why something is relevant, it probably isn't."

2 1

Pharo newsletter archive
by Torsten Bergmann Dec. 5, 2017

Dec. 5, 2017

Hi, the newsletter archive is now available on "newsletter.pharo.org" which is more easy to remember. Thanks Marcus for setting up the redirect! Bye T.

3 2

[ANN] Pharo TechTalk 21 Nov: Discord Demo
by Marcus Denker Dec. 5, 2017

Dec. 5, 2017

Pharo TechTalk: Discord Demo When? 21 Nov 2017 5:00 PM - 7:00 PM (UTC+01:00) Topic: "Discord communication Demoâ, how to script discord from Pharo. https://association.pharo.org/event-2642665

6 13

Garbage Collection (was Re: Discussing the roadmap)
by Ben Coman Dec. 5, 2017

Dec. 5, 2017

Hi Eliot, Clement, On 7 July 2017 at 00:41, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > > - Better support for large heaps (GC tuning API, incremental GC). > > Pharo 64 bit is now able to manage large heap. However better > > performance can be proposed by offering better settings for the > > different GC zone. > > The most important thing here is the incremental GC. Spur has a generation > scavenger that collects garbage in newly created objects (new space), > and a mark-compact collector that collects and compacts garbage in old space. > > Right now on my 2.3GHz MacMini doing normal development, the generation > scavenger causes pauses of 1ms or less, and the mark-compact collector > than causes pauses of around 200ms. Both account for about 0.75% of > entire execution time (1.5% total), so the scavenger is invoked frequently > and the pauses that it creates are not noticeable. But the occasional > pauses created by the mark-compact collector /are/ noticeable, > especially in games and music. > > The idea for the incremental collector is to implement a mark-sweep or > mark-sweep-compact collector for old space that works incrementally, > doing a little bit of work on each invocation, probably immediately after a scavenge. > It is intended to avoid the long pauses caused by the non-incremental > mark-compact collector and make the system more suitable for games, music, etc. Reading http://www.mirandabanda.org/cogblog/2013/09/13/lazy-become-and-a-partial-re… "An alternative implementation, oft-used in Lisp systems, is to add a read barrier to all object access, and mark objects as forwarders. This can be used to implement a >>>lazy copying garbage collection<<<< where objects are copied from one semi-space to another in parallel to the main program (the âmutatorâ). To become, or move an object one replaces the objectâs header or first field with a forwarding pointer to the desired target or copy in a new location, marking the âcorpseâ as forwarded. The program checks the forwarded flag on each access. If there is hardware support, as in a Lisp machine, this can work well. But without hardware support, and like the object table representation, it has costs, slowing down program execution due to the scattering of forwarding checks and forwarding pointer follows throughout program execution." I'm curious... Given we now have forwarders with Spur, are we already sufficiently paying the cost of forwarding checks that a lazy copying garbage collector might be a feasible form of incremental garbage collection? I presume "parallel to the main program" means garbage collection occuring in a separate thread to the main vm thread, potentially resulting in very low main program pause times for garbage collection. I found this a useful summary of the terminology... * https://www.dynatrace.com/resources/ebooks/javabook/reduce-garbage-collecti… and I'm curious how our planned Incremental CG fits those categories. That article got me contemplating our performance constraint of the VM only operating in only in a single native thread. Even though GC is a only a few percent of performance, I wondered what a concurrent GC might look like for us. I found this video describing concurrent GC in Go (ignore first 11:20 and the second half was not so interesting) * https://pusher.com/sessions/meetup/the-realtime-guild/golangs-realtime-garb… where they present some interesting charts of their concern with latency pauses. (btw they reference a multi-language GC latency benchmark https://github.com/WillSewell/gc-latency-experiment) And for balance of that I found... https://blog.plan99.net/modern-garbage-collection-911ef4f8bd8e And then my mind wandered around implementation details of concurrent garbage collection. To organise and quiet my thoughts I needed to put pen to paper, so I thought sharing that might stir thoughts for others. Probably naive and please excuse the brain dump format... Considering two threads... * Main program thread "MP" * Garbage collection thread "GC" with object-space shared between them, consisting of objects split in object-header & object-body... 1. Only "MP" mutates the object-body, updating slots creating new edges in the object-graph, and relocating objects in memory using forwarders. This rule avoids potential race conditions without needing to add synchronisation code affecting performance of "MP". 2. Concurrently "GC" performs a Marking Phase by following the object-graph tricolour tagging objects gray & black. it needs to mutate the object-header, in a synchronised way something like... a. Load object-header from shared object-space into local variable H <== object-header b. Modify header into another local variable H' <== H + updated GC color bits c. Atomic compare-and-swap H' back into object-space object-header <== if H then H' "MP" gets priority. Conflicts presumed rare. Then considering object mutation by "MP" concurrent/overlapped with "GC" marking... 3. TLDR; see 4. In old-space if 'mutated' object is linked to a 'target' object a. if 'mutated' isBlack, "MP" marks 'target' gray (to be later processed by "GC"). b. if 'mutated' isGray, overlapped 'mutated' gray->black by "GC" while 'target' remains white would break tricolor invariant (is it a credible case?), options... i. mark 'target' gray, the state anyway in case 'mutated' gray -> black ii. re-mark 'mutated' gray, i.e. normally gray->gray, and rarely black->gray iii. optimisticly just check after mutation if color changed (cached reads cheaper than writes and conflicts presumed rare) then set color to gray. c. if 'mutated' isWhite, options... i. do nothing and let "GC" reach 'target' normally, as long as overlapped white->black cannot occur ii. if white->black possible, do same as (3.b) "MP" marks 'target' gray, to be later processed by "GC". 4. Overall simplification of (3.) might be... "MP" checks for any color change during mutation, and only then marks 'mutated' object gray. How expensive would such a check be? Presumed marking is infrequent and can be done safely like (2.) 5. Eden/survivor space is ignored by "GC" thread. No point in adding work to the gray set until survivors filtered. Stop the world scavenging done as normal by "MP", only marking objects gray when they are moved to old-space. Post scavenging options... a. Resume the world and leave it for "GC" to process these recently grayed objects. b. Keep world stopped for "MP" to complete marking, emptying gray set to transition to Sweep Phase, at which point "MP" resumes the world. It doesn't matter if subsequently objects are added to the gray set, since existing white objects can never again be referenced by "MP". 6. Sweeping can be safely done by "GC" since white-objects are unreachable from "MP". "GC" can also take time to determine an optimum page P to compact and then (per 1.) passes to "MP" via a relocation-queue the objects to be relocated using forwarding pointers. "GC" could even spend extra time to determine the optimum relocation-destination without impacting the performance of "MP". When "MP" empties the relocation-queue, "GC" starts on the next Marking Phase. 7. Now a question remains about multi-threaded flattening of forwarding pointers. If two threads simultaneously perform an identical transform from... someObject-slot --> forwarder-b --> finalObject-c to... someObject-slot --> finalObject-c does it matter that these operation may be done twice overlapping? Options... a. One mitigation could be for "GC" to identify forwarders to be flattened and queue them for "MP" to process (reuse the compaction-queue). This is work that "MP" would need to do anyway, but brings it forward to be dealt with at a convenient time. b. I guess "MP" and "GC" could play nice together if when encountering a slot containing with a forwarding pointer they both do something similar to (2.) like... i. Load object-slot from shared object-space into local variable S <== slot ii. Set local variable S' <== flattened/followed pointer iii. Atomic compare-and-swap S' back into object-space, (object-slot <== if S then S') - "MP" gets priority but presume conflicts rare anyway. - While this violates rule (1.) the presumed frequency of encountering forwarding pointers is low for "MP", so performance should not be affected. Indeed by "GC" pre-emptively flattening forwarders the frequency "MP" sees reduces. 8. The release of the compacted page back to the OS is held up by forwarding pointers. Forwarders are part of the graph followed in the Marking Phase they get marked gray/black just like objects if they are referenced. After forwarders are fully flattened they are skipped by Marking and end up marked white and released just like any other object. Once all forwarders are released, the page is released to the OS. If "GC" can effectively flatten pointers concurrently with "MP" during its normal Marking Phase, then pages would be released back to the OS in a timely manner. Now one thing I am curious about how the GC tri-color marking is implemented. At https://clementbera.wordpress.com/2014/01/16/spurs-new-object-format it describes how Spur's object header has three bits for GC. * isGray * isRemembered * isMarked (I presume this means marked "black") Do the bits imply the gray set is not stored in a separate data structure on the heap, but rather distributed in-place, which I guess would require multiple passes through memory to grow the gray set? So this is not an area I'm set up to seriously work on, but I remain curious and hopefully its a useful seed discussion for others. cheers -ben P.S. At https://clementbera.wordpress.com/2017/09/19/vm-learning-memory-management/ nice to hear that you have Sophie (I presume) continuing with the VM.

4 5

Bloc Feedback
by Sean P. DeNigris Dec. 4, 2017

Dec. 4, 2017

Highlights: - BlCornerRadii - 1st class corners - yay to the death of cryptic arrays for this kind of thing :) Questions: - How would one do e.g. a ticking clock in Bloc? The only possibly relevant example I see is BlAnimatedCursor. Is that a typical usage? One thing that I'm not sure how to translate to a BlElement is that the cursor seems to be responsible for starting and stopping the animation via #activateOn:, which doesn't exist for an element. How would one prevent an element's animation from continuing to run after a space was closed? - BlElement has 278 instance-side methods. A frequent battle cry against Morphic was the bloated Morph class with 899. Definitely an improvement, but are we "there yet"? - Does Bloc implement its own keybinding outside of "Keymapping" e.g. BlShortcut? If so, why? Will it ultimately be a replacement? - In BlTextEditElement class>>#exampleText, text construction seems awfully complex (`text := BrRopedText rope: (BrCollectionRope collection: (String loremIpsum: 30)). text attributes: { BrFontWeightAttribute bold }.`. How does that way contrast to e.g. `'X' asRopedText`? Problems: BlBasicExamples - #exampleShapes, select the yellow shape with red border -> inspector -> Transformations Tab -> Click on Composition -> "ShouldNotImplement: #multiplyOn: should not have been implemented in BlCompositeTransformation" - #exampleImageBackground -> "ShouldBeImplemented: #fillPath:withForm: should have been implemented in SpartaCairoFillPainter" BlTextEditElement class>>#exampleText - insert some characters and then press [delete] -> "Error: Illegal sub-sequence end index: 44" - There is aBlSelectionHandler, but I can't seem to select any of the text BrAttributeRopeExamples#>>simpleRope -> inspect return value -> In inspector, click on "Children" tab -> "Error: Improper store into indexable object" - In BlLinearLayoutExamples class>>#exampleVerticalLeftCenterRightRTL, - the red sub-element does `c linear horizontal alignLeft`, which is then overridden by its parent's `BlLinearLayout vertical "rightToLeft"`. Was it intentional to show the precedence because I found it confusing when an element that sent #alignLeft showed up on the right! - the yellow sub-element does not appear at all. Maybe it should do a `c vertical exact: 100.` like its siblings? - All BlAnimationExamples lead to deprecation warnings and DNU's, but *do not even attempt* #exampleBallsAnim or face endlessly multplying debugger windows! ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

6 35

Polymorphism between Strings and FileReference
by Cyril Ferlicot Dec. 4, 2017

Dec. 4, 2017

Hi, I am often in the case where I have a method taking a file or a string as parameter and I often want to use #readStreamDo:/#writeStreamDo: in the method because with I do not have to care if I need to close the file stream or not with those. But since String do not understand #readStreamDo:/#writeStreamDo: I cannot do that. Maybe it's worth to implement them on String? https://pharo.fogbugz.com/f/cases/20796/String-should-understand-readStream… Since it add methods to String I prefer talk about it on the mailing list to have everyone's advice. -- Cyril Ferlicot https://ferlicot.fr http://www.synectique.eu 2 rue Jacques PrÃ©vert 01, 59650 Villeneuve d'ascq France

3 5

Bloc and Gestures
by Sean P. DeNigris Dec. 4, 2017

Dec. 4, 2017

I see a tantalizing hierarchy of BlGestureEvent and subclasses like BlGestureZoomEvent, but I can't seem to trap any. Are these working? If not, any ETA? ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

3 2

Pharo Launcher endless loop opening debuggers in Pharo 6.1
by Bernhard Pieber Dec. 4, 2017

Dec. 4, 2017

I ran into an annoying problem using the latest Pharo 6.1 (stable) from Pharo Launcher. I am on macOS Sierra Version 10.12.6. Steps to reproduce: 1. Open Pharo Launcher 2. Create new Pharo 6.1 (stable) image from the official distributions, named Test 3. Launch the Test image 4. Open a File Browser 5. Right click on the selected Test directory in the left file tree pane. 6. Debuggers start opening on KeyNotFound: key #arg4 not found in Dictionary 7. Image hangs Interestingly the problem does not happen if I create the image using âcurl get.pharo.org | bashâ and start it with â./pharo-ui Pharo.imageâ although About Pharo shows the same information: Pharo 6.0 Latest update: #60523 Can someone please confirm the bug? Bernhard

2 2

[Pharo 7.0-dev] Build #358: 20786-halt-messages-are-not-highlighted-in-red-as-the-other-flavours-of-halt-messages
by ci-pharo-ci-jenkins2＠inria.fr Dec. 4, 2017

Dec. 4, 2017

There is a new Pharo build available! The status of the build #358 was: SUCCESS. The Pull Request #569 was integrated: "20786-halt-messages-are-not-highlighted-in-red-as-the-other-flavours-of-halt-messages" Pull request url: https://github.com/pharo-project/pharo/pull/569 Issue Url: https://pharo.fogbugz.com/f/cases/20786 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Alternative bytecode sets demo request
by Ben Coman Dec. 4, 2017

Dec. 4, 2017

I'm shooting in the dark here since its a bit hard to grasp... a. The implications of support alternative bytecode sets * Do the alternative bytecode sets run in parallel to normal Pharo bytecodes? * Can the bytecode sets be loaded adhoc/dynamically into an Image? or only compiled into the VM? b. How to implement/work with alternative bytecodes For (a.) I guess an exciting opportunity is facilitating an Ethereum virtual machine running as a Process inside a Pharo image, managed by tools written in Pharo. Other languages are already getting in a party which would be good for Pharo to join. In such a revolutionary domain I expect people are more willing to experiment with alternative systems like Pharo, and I bet Pharo could excel in that domain. * https://github.com/ethereum/go-ethereum/blob/master/core/vm/opcodes.go * https://medium.com/@jeff.ethereum/optimising-the-ethereum-virtual-machine-5… * https://github.com/pirapira/awesome-ethereum-virtual-machine#evm-implementa… To help (b.), would it be feasible to blog a mini-demo showing how to install/use alternative bytecodes? maybe for something like this simple RPN calculator substitute for "arith.c"... * https://github.com/philipaconrad/mini-vm/tree/master/examples/arith * https://github.com/philipaconrad/mini-vm/blob/master/examples/arith/arith.c (a calculator demo could be an interesting adjunct to Sven's calculator tutorial...) https://medium.com/concerning-pharo/rediscovering-the-ux-of-the-legendary-h… cheers -ben

3 4

[Pharo 7.0-dev] Build #357: 20781-update-to-iceberg-064
by ci-pharo-ci-jenkins2＠inria.fr Dec. 4, 2017

Dec. 4, 2017

There is a new Pharo build available! The status of the build #357 was: SUCCESS. The Pull Request #560 was integrated: "20781-update-to-iceberg-064" Pull request url: https://github.com/pharo-project/pharo/pull/560 Issue Url: https://pharo.fogbugz.com/f/cases/20781 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #356: 20793-During-Bootstrap-if-a-baseline-installation-fails-it-should-cancel-the-process
by ci-pharo-ci-jenkins2＠inria.fr Dec. 4, 2017

Dec. 4, 2017

There is a new Pharo build available! The status of the build #356 was: FAILURE. The Pull Request #567 was integrated: "20793-During-Bootstrap-if-a-baseline-installation-fails-it-should-cancel-the-process" Pull request url: https://github.com/pharo-project/pharo/pull/567 Issue Url: https://pharo.fogbugz.com/f/cases/20793 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Design pattern for wrapper/proxy objects?
by Luke Gorrie Dec. 4, 2017

Dec. 4, 2017

Howdy, I have some Smalltalk objects that represent external data and I am looking for a neat way to access them. The data that I am dealing with is C binary objects described by DWARF schemas. So I will load a type declaration like this: struct outer { struct inner { int a, b; }; }; and then I will want to be able to write convenient expressions like: aStruct outer inner a + aStruct outer inner b I have implemented this already but I am not sure that I took the right approach. I have implemented these accessors like #outer #inner #a #b via a messageNotUnderstood: method that looks into the object, so that 'aStruct outer' is equivalent to 'aStruct field: #outer'. My concern is that the names of the C struct fields can collide with existing Smalltalk methods and then I will get totally unexpected results. Is there a canonical solution to this problem? The first idea I have is to add a bit of syntatic sugar, like to write 'aStruct _outer _inner _a' where the leading underscore avoids method name collisions and is then stripped off in messageNotUnderstood. That doesn't seem especially elegant though. I can't quite bring myself to write verbose things like ((aStruct child: #outer) child: #inner) child: #a

4 4

Esteban's ChangeLog week of 27 November 2017
by estebanlm＠gmail.com Dec. 4, 2017

Dec. 4, 2017

Hello! This is my weekly ChangeLog, from 27 November 2017 to 3 December 2017. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=27/11/2017&to=3/12/2017 ChangeLog ========= 28 November 2017: ----------------- * I just released [Iceberg 0.6.4](https://github.com/pharo-vcs/iceberg/releases/tag/v0.6.4). This is a bugfix release :) cheers! Esteban

1 0

Where is the latest linux vm?
by stephan Dec. 3, 2017

Dec. 3, 2017

Is the latest really from august? Stephan

5 10

MCRepositoryError on System > Software update
by Bernhard Pieber Dec. 2, 2017

Dec. 2, 2017

I assume that System > Software update can be used to update an Image from Pharo 6.0 to Pharo 6.1, correct? When I tried to update a Pharo 6.0 image (Latest update: #60499) using System > Software update I ran into the following error: Could not load BaselineOfFileTree-ThierryGoubier.32.mcz: ZnHttpUnsuccessful: 404 Not Found I tried it twice to make sure it was not some intermittent network error. Any help would be appreciated. Bernhard

3 2

[Pharo 7.0-dev] Build #355: 20800-do-not-open-welcome-window-for-now
by ci-pharo-ci-jenkins2＠inria.fr Dec. 1, 2017

Dec. 1, 2017

There is a new Pharo build available! The status of the build #355 was: FAILURE. The Pull Request #568 was integrated: "20800-do-not-open-welcome-window-for-now" Pull request url: https://github.com/pharo-project/pharo/pull/568 Issue Url: https://pharo.fogbugz.com/f/cases/20800 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[ANN] New Academic Partner: USI Software Institute
by Marcus Denker Dec. 1, 2017

Dec. 1, 2017

The Pharo Consortium is very happy to announce that the Software Institute of the UniversitÃ della Svizzera italiana has joined as a Academic Partner. About - USI Software Institute: https://www.si.usi.ch <https://www.si.usi.ch/> - Pharo Consortium: http://consortium.pharo.org <http://consortium.pharo.org/> The goal of the Pharo Consortium is to allow companies and institutions to support the ongoing development and future of Pharo. Individuals can support Pharo via the Pharo Association: http://association.pharo.org <http://association.pharo.org/>

1 0

[Pharo 7.0-dev] Build #354: 20786-halt-messages-are-not-highlighted-in-red-as-the-other-flavours-of-halt-messages
by ci-pharo-ci-jenkins2＠inria.fr Dec. 1, 2017

Dec. 1, 2017

There is a new Pharo build available! The status of the build #354 was: SUCCESS. The Pull Request #564 was integrated: "20786-halt-messages-are-not-highlighted-in-red-as-the-other-flavours-of-halt-messages" Pull request url: https://github.com/pharo-project/pharo/pull/564 Issue Url: https://pharo.fogbugz.com/f/cases/20786 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[ANN] files.pharo.org server move tomorrow, Nov 30
by Marcus Denker Dec. 1, 2017

Dec. 1, 2017

Hi, We will do the switch to the new server tomorrow, Nov 30. -> for people downloading, there should be no service intererruption -> For *uploaders* (mostly CI jobs), you need new SSH credentials. This means some upload jobs might break, but they will be easy to fix -> Uploading humans (people that scp to files.pharo.org <http://files.pharo.org/>): Talk to Christoph or me. Marcus

2 9

iceberg metacello integration not working?
by Tudor Girba Dec. 1, 2017

Dec. 1, 2017

Hi, In - a 60523 image, - with the latest stable VM (Mac OS X built on Jul 20 2017 21:45:23 UTC Compiler: 4.2.1 Compatible Apple LLVM 6.1.0 (clang-602.0.53)) I am doing: Iceberg enableMetacelloIntegration: true. Metacello new baseline: 'GToolkit'; repository: 'github://feenkcom/gtoolkit/src'; load. The Iceberg window is empty (no repositories), and on the file system I have the github-cache folder filled with the downloaded code. Am I doing something wrong, or is this a regression? Cheers, Doru -- www.tudorgirba.com www.feenk.com "If you interrupt the barber while he is cutting your hair, you will end up with a messy haircut."

2 2

Newsletter content / editors wanted
by Marcus Denker Dec. 1, 2017

Dec. 1, 2017

Hi, You might know that we are sending out a monthly pharo newsletter, it contains larger âmini articlesâ (e.g. announcements) and small one-line notes for blog posts, new libraries, things like that. Here is the archive: https://us11.campaign-archive.com/home/?u=6f667565c2569234585a7be77&id=0486… <https://us11.campaign-archive.com/home/?u=6f667565c2569234585a7be77&id=0486…> Target audience are especially those who no follow the mailing list, but I think it is interesting even for us as it is easy to not see all the interesting news. If you have content: please send it to me, I collect things over a month and then we put the newletter together from that. This can be: - small (half page) articles abut *your* project! - an interesting library you found - a blog post you have written (or read) People can even take over for a complete month and do e.g. a themed newsletter focusing on one aspect or project. Marcus

2 1