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

Re: [Pharo-dev] Bloc Naming Suggestion

by Stephane Ducasse

In Opal I would keep it because this is about error and warning and you are not all the time manipulating them while for Bloc as soon as you use text you will have to. On Wed, Nov 22, 2017 at 9:37 PM, Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> wrote: > I see same kind of names in Opal exceptions > Maybe the intention was to clearly distinguish Error from Warning > (proceedable), but the hierarchy tells already. > > OCSemanticError > OCStoreIntoReadOnlyVariableError could be just OCStoreIntoReadOnlyVariable > OCStoreIntoSpecialVariableError -> OCStoreIntoSpecialVariable > > OCSemanticWarning > OCShadowVariableWarning > OCUndeclaredVariableWarning > > Note that removing the Warning suffix might lead to ambiguous names... > OCUndeclaredVariable might be confused as being a Variable. > So maybe OCVariableUndeclared or OCVariableIsUndeclared > > 2017-11-22 21:25 GMT+01:00 Stephane Ducasse <stepharo.self(a)gmail.com>: >> >> +1 >> >> >> On Sun, Nov 19, 2017 at 4:34 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> > I think itâs not a bad idea. >> > >> > Doru >> > >> >> On Nov 19, 2017, at 4:31 PM, Sean P. DeNigris <sean(a)clipperadams.com> >> >> wrote: >> >> >> >> What do you think about removing the #Attribute suffix from all the >> >> BrTextAttribute subclasses? The names seem pretty long (e.g. >> >> BrFontGenericFamilyAttribute, the longest) and IMHO `BrTextAttribute >> >> subclass: #BrFontWeight` is adequately intention revealing. Thoughts? >> >> >> >> >> >> >> >> ----- >> >> Cheers, >> >> Sean >> >> -- >> >> Sent from: >> >> http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html >> >> >> > >> > -- >> > www.tudorgirba.com >> > www.feenk.com >> > >> > "Problem solving efficiency grows with the abstractness level of problem >> > understanding." >> > >> > >> > >> > >> > >> >

Nov. 23, 2017

Re: [Pharo-dev] Deploying using the latest minimal image of Pharo (6.1)

by Stephane Ducasse

Yes your second scenario looks cool to me :). Keep us informed because this is really exciting. Stef On Thu, Nov 23, 2017 at 10:13 PM, despotadesdibujau <despotadesdibujau(a)gmail.com> wrote: >>Hi Gabriel > >>This is cool. >>Thanks for sharing it with us. >>I really want an object responsible for deploying an app. :) >>Your effort is nice in that directory. Keep pushing > >>Stef > Thanks!!! > > Maxi Tabacman suggests me to reify the deployment process. > I thought of something like to get up a minimal image from inside the > development image, then to start the deployment process from the development > image. > I suppose that I would need to use Espell Object Spaces (Guillermo Polito), > but in this case, I would need a special virtual machine (Oz Virtual > Machine)... Something like Tornado, but not using the "Run Fail Grow" > approach, but using a BaselineOf or ConfigurationOf approach. > Another idea (simpler than the idea above) is to communicate the two images > using Teapot or Sockets: The Development image sends orders to the minimal > image until it becomes on the deployment image. > > For the moment I need to test the process (on Pharo 6 and 7) using more > complex applications until it becomes a reliable process. > > Gabriel > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html >

Nov. 23, 2017

Re: [Pharo-dev] [PHARO 7.0A] NEXT ENHANCEMENTS

by Stephane Ducasse

+ 1 :) On Thu, Nov 23, 2017 at 8:53 PM, Torsten Bergmann <astares(a)gmx.de> wrote: > What is not visible in the list are the many enhancements happening also on > Calypso, Bloc, > Grease and many many others. > > Nonetheless the core image still needs love from more people. Remember even > the smallest change > can make a difference and shape the future. Also "a contribution per day > keeps bad systems away". > Even one contribution per week or month. > > So jump in - the water is just fine! > > Bye > T. (aka astares) > > Gesendet: Donnerstag, 23. November 2017 um 12:37 Uhr > Von: "phil(a)highoctane.be" <phil(a)highoctane.be> > An: "Pharo Development List" <pharo-dev(a)lists.pharo.org> > Betreff: Re: [Pharo-dev] [PHARO 7.0A] NEXT ENHANCEMENTS > Yes, very. > > Phil > > On Thu, Nov 23, 2017 at 12:26 PM, Alexandre Bergel <alexandre.bergel(a)me.com> > wrote: >> >> Impressive!! >> >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> On Nov 23, 2017, at 7:12 AM, Stephane Ducasse <stepharo.self(a)gmail.com> >> wrote: >> >> eport period: 5 November 2017 to 23 November 2017 >> >> * 20739-Remove-dead-stream-primitives >> >> https://pharo.fogbugz.com/f/cases/20739/Remove-dead-stream-primitives >> >> >> Issue URL: https://pharo.fogbugz.com/f/cases/20739 >> PR URL: https://github.com/pharo-project/pharo/pull/524 >> Diff URL: https://github.com/pharo-project/pharo/pull/524/files >> >> Thanks to clementbera >> >> * 20645-Windows-rebuildFieldAccessors-problem >> >> Fixing the creation of annonymous classes for FFITypeArray. >> It was affecting all the platforms. >> >> Issue: >> https://pharo.fogbugz.com/f/cases/20645/Windows-rebuildFieldAccessors-probl… >> >> >> Issue URL: https://pharo.fogbugz.com/f/cases/20645 >> PR URL: https://github.com/pharo-project/pharo/pull/521 >> Diff URL: https://github.com/pharo-project/pharo/pull/521/files >> >> Thanks to tesonep >> >> * >> 20735-ComposablePresenter-classowneron-is-missing-the-initialization-call >> >> >> https://pharo.fogbugz.com/f/cases/20735/ComposablePresenter-class-owner-on-… >> >> >> Issue URL: https://pharo.fogbugz.com/f/cases/20735 >> PR URL: https://github.com/pharo-project/pharo/pull/517 >> Diff URL: https://github.com/pharo-project/pharo/pull/517/files >> >> Thanks to pavel-krivanek >> >> * Fix the sign of FloatNegativeZero >> >> Like any other zero, the sign of Float negativeZero should be zeroâ¦ >> Introduce signBit to differentiate Float negativeZero from Float zero. >> >> This is issue >> >> https://pharo.fogbugz.com/f/cases/19629/0-0-sign-answers-1-should-be-zero >> >> >> Note that this PR does not implement isSignMinus which is not >> >> strictly necessary. >> >> If itâs for ISO 10967 compliance, then there will be other >> >> functions missing. >> >> Maybe open a new issue for this one? >> >> >> Issue URL: https://pharo.fogbugz.com/f/cases/Fix the sign of >> FloatNegativeZero >> PR URL: https://github.com/pharo-project/pharo/pull/515 >> Diff URL: https://github.com/pharo-project/pharo/pull/515/files >> >> Thanks to nicolas-cellier-aka-nice >> >> * 20717-Duplicities-of-themes-in-the-list-2 >> >> https://pharo.fogbugz.com/f/cases/20717/Duplicities-of-themes-in-the-list >> >> alternative version by Torsten >> >> >> Issue URL: https://pharo.fogbugz.com/f/cases/20717 >> PR URL: https://github.com/pharo-project/pharo/pull/499 >> Diff URL: https://github.com/pharo-project/pharo/pull/499/files >> >> Thanks to pavel-krivanek >> >> * 20730 Unused temps in FileReferenceTest, FLHeaderSerializationTest, >> FLHookedSubstitutionTest, FT2GlyphRenderer, ... >> >> Fix unused temps in >> >> FileReferenceTest>>#testRename >> FileReferenceTest>>#testDeleteAllChildren >> FileReferenceTest>>#testHasChildren >> FileReferenceTest>>#testHasDirectories >> FileReferenceTest>>#testHasFiles >> FLHeaderSerializationTest>>#testAdditionalObjects >> FLHookedSubstitutionTest>>#testAvoidRecursion >> FT2GlyphRenderer>>#loadSurfaceTransform >> FT2GlyphRenderer>>#loadUnicode: >> FileDialogWindowTest>>#testIssue6406 >> FileReferenceTest>>#testDeleteAll >> >> >> Issue URL: https://pharo.fogbugz.com/f/cases/20730 Unused temps >> in FileReferenceTest, FLHeaderSerializationTest, >> FLHookedSubstitutionTest, FT2GlyphRenderer, ... >> PR URL: https://github.com/pharo-project/pharo/pull/510 >> Diff URL: https://github.com/pharo-project/pharo/pull/510/files >> >> Thanks to astares >> >> * 20731 Unused temps in HDCoverageReport and HDLintReport >> >> fix unused temps >> >> HDCoverageReport>>#generatePackage:method:on: >> HDLintReport>>#generateClass:source:on: >> >> >> >> https://pharo.fogbugz.com/f/cases/20731/Unused-temps-in-HDCoverageReport-an… >> >> >> Issue URL: https://pharo.fogbugz.com/f/cases/20731 Unused temps >> in HDCoverageReport and HDLintReport >> PR URL: https://github.com/pharo-project/pharo/pull/511 >> Diff URL: https://github.com/pharo-project/pharo/pull/511/files >> >> Thanks to astares >> >> * 20732 Unused temps in HistoryNodeTest >> >> fix unused temps >> >> HistoryNodeTest>>#testTwoConsecutiveCloseGroup >> HistoryNodeTest>>#testTwoGroups >> >> https://pharo.fogbugz.com/f/cases/20732/Unused-temps-in-HistoryNodeTest >> >> >> Issue URL: https://pharo.fogbugz.com/f/cases/20732 Unused temps >> in HistoryNodeTest >> PR URL: https://github.com/pharo-project/pharo/pull/512 >> Diff URL: https://github.com/pharo-project/pharo/pull/512/files >> >> Thanks to astares >> >> * 20733-update-bootstrap-emulation >> >> https://pharo.fogbugz.com/f/cases/20733/update-bootstrap-emulation >> >> >> Issue URL: https://pharo.fogbugz.com/f/cases/20733 >> PR URL: https://github.com/pharo-project/pharo/pull/516 >> Diff URL: https://github.com/pharo-project/pharo/pull/516/files >> >> Thanks to pavel-krivanek >> >> * 20384-Converted-rules-to-Renraku-architecture-2 >> >> Let's try this one, it should work >> >> >> Issue URL: https://pharo.fogbugz.com/f/cases/20384 >> PR URL: https://github.com/pharo-project/pharo/pull/445 >> Diff URL: https://github.com/pharo-project/pharo/pull/445/files >> >> Thanks to Uko >> >> * 20727-WeakAnnouncerTesttestWeakDoubleAnnouncer-should-be-long >> >> >> https://pharo.fogbugz.com/f/cases/20727/WeakAnnouncerTest-testWeakDoubleAnn… >> >> increse timeouts and decrease amount of explicit GC calls >> >> >> Issue URL: https://pharo.fogbugz.com/f/cases/20727 >> PR URL: https://github.com/pharo-project/pharo/pull/509 >> Diff URL: https://github.com/pharo-project/pharo/pull/509/files >> >> Thanks to pavel-krivanek >> >> * Avoid costly & useless LargeInteger arithmetics when >> raisedToFraction will be inexact >> >> >> This example was raised in >> >> >> https://pharo.fogbugz.com/f/cases/20432/vm-crash-when-using-rairedTo-with-f… >> >> (2009/2000) raisedTo: (3958333/100000) >> >> The fix is importing the changes from >> >> http://source.squeak.org/trunk/Kernel-nice.1111.diff >> >> Issue URL: https://pharo.fogbugz.com/f/cases/Avoid costly & >> useless LargeInteger arithmetics when raisedToFraction will be inexact >> PR URL: https://github.com/pharo-project/pharo/pull/506 >> Diff URL: https://github.com/pharo-project/pharo/pull/506/files >> >> Thanks to nicolas-cellier-aka-nice >> >> * 20723 Unused temps in AthensDemoMorph, Alien, AthensBalloonEngine, >> AthensBezier3Scene, AthensCairoPathBuilder >> >> Fix unused temps in >> >> AthensDemoMorph>>#figure9: >> Alien class>>#newCString: >> AthensBalloonEngine>>#drawImage:transform: >> AthensBezier3Scene>>#renderOn: >> AthensCairoPathBuilder>>#calcCenter:end:angle: >> AthensDemoMorph>>#figure10: >> AthensDemoMorph>>#figure2: >> AthensDemoMorph>>#figure3: >> AthensDemoMorph>>#figure6: >> >> >> Issue URL: https://pharo.fogbugz.com/f/cases/20723 Unused temps >> in AthensDemoMorph, Alien, AthensBalloonEngine, AthensBezier3Scene, >> AthensCairoPathBuilder >> PR URL: https://github.com/pharo-project/pharo/pull/503 >> Diff URL: https://github.com/pharo-project/pharo/pull/503/files >> >> Thanks to astares >> >> * 20724 Unused temps in EditorFindReplaceDialogWindow>>#update: >> >> fix unused temp >> >> >> Issue URL: https://pharo.fogbugz.com/f/cases/20724 Unused temps >> in EditorFindReplaceDialogWindow>>#update: >> PR URL: https://github.com/pharo-project/pharo/pull/504 >> Diff URL: https://github.com/pharo-project/pharo/pull/504/files >> >> Thanks to astares >> >> * 20725 Unused temps in DosTimestampTest, Decompiler, DiskStore, >> DosTimestampTest, DateTest >> >> Fix unused temps in >> >> DosTimestampTest>>#testFromDateAndTime >> Decompiler>>#statementsTo: >> DiskStore>>#rename:to: >> DosTimestampTest>>#testAsDateAndTime >> DateTest>>#testPrintFormat >> >> >> Issue URL: https://pharo.fogbugz.com/f/cases/20725 Unused temps >> in DosTimestampTest, Decompiler, DiskStore, DosTimestampTest, DateTest >> PR URL: https://github.com/pharo-project/pharo/pull/505 >> Diff URL: https://github.com/pharo-project/pharo/pull/505/files >> >> Thanks to astares >> >> * 20722 Unused temps in KMShortcutTest, KMDispatcher, KMKeymapTest >> >> Fix unused temps in >> >> KMShortcutTest>>#testComplexChainMatches >> KMDispatcher>>#dispatch: >> KMKeymapTest>>#testExecute >> >> >> https://pharo.fogbugz.com/f/cases/20722/Unused-temps-in-KMShortcutTest-KMDi… >> >> >> Issue URL: https://pharo.fogbugz.com/f/cases/20722 Unused temps >> in KMShortcutTest, KMDispatcher, KMKeymapTest >> PR URL: https://github.com/pharo-project/pharo/pull/502 >> Diff URL: https://github.com/pharo-project/pharo/pull/502/files >> >> Thanks to astares >> >> * 20720 Unused temps in Object, OCASTCheckerTest and >> OCASTClosureAnalyzerTest >> >> Fix unused temp vars >> >> Object>>#split: >> OCASTCheckerTest>>#testDoubleRemoteAnidatedBlocks >> OCASTCheckerTest>>#testExamplePrimitiveErrorCode >> OCASTCheckerTest>>#testExampleSelf >> OCASTCheckerTest>>#testExampleSuper >> OCASTCheckerTest>>#testExampleThisContext >> OCASTCheckerTest>>#testInstanceVar >> OCASTCheckerTest>>#testNoRemoteBlockArgument >> OCASTCheckerTest>>#testNoRemoteBlockReturn >> OCASTCheckerTest>>#testNoRemoteBlockTemp >> OCASTCheckerTest>>#testNoRemoteMethodTemp >> OCASTCheckerTest>>#testOptimizedBlocksAndSameNameTemps >> OCASTCheckerTest>>#testSingleRemoteDifferentBlocksSameArgumentName >> OCASTCheckerTest>>#testSingleRemoteMethodArgument >> OCASTClosureAnalyzerTest>>#testDoubleRemoteAnidatedBlocks >> OCASTClosureAnalyzerTest>>#testExampleBlockArgument >> OCASTClosureAnalyzerTest>>#testExampleSimpleBlockLocalWhile >> OCASTClosureAnalyzerTest>>#testExampleSimpleBlockNested >> OCASTClosureAnalyzerTest>>#testExampleWhileModificationBefore >> OCASTClosureAnalyzerTest>>#testNestedBlocksRemoteInBlockCase2 >> OCASTClosureAnalyzerTest>>#testNestedBlocksRemoteInBlockCase3 >> OCASTClosureAnalyzerTest>>#testNoRemoteBlockArgument >> OCASTClosureAnalyzerTest>>#testNoRemoteReadInBlock >> OCASTClosureAnalyzerTest>>#testNoRemoteReadNestedBlocks >> OCASTClosureAnalyzerTest>>#testOptimizedBlockReadInBlock >> OCASTClosureAnalyzerTest>>#testOptimizedBlockWriteInBlock >> OCASTClosureAnalyzerTest>>#testOptimizedBlockWriteInNestedBlock >> OCASTClosureAnalyzerTest>>#testOptimizedBlockWriteInNestedBlockCase2 >> OCASTClosureAnalyzerTest>>#testOptimizedBlockWriteInNestedBlockCase3 >> OCASTClosureAnalyzerTest>>#testOptimizedBlockWriteInNestedBlockCase4 >> OCASTClosureAnalyzerTest>>#testOptimizedBlockWrittenAfterClosedOverCase1 >> OCASTClosureAnalyzerTest>>#testOptimizedBlockWrittenAfterClosedOverCase2 >> OCASTClosureAnalyzerTest>>#testSingleRemoteDifferentBlocksSameArgumentName >> OCASTClosureAnalyzerTest>>#testSingleRemoteMethodArgument >> OCASTClosureAnalyzerTest>>#testSingleRemoteReadNestedBlocks >> OCASTClosureAnalyzerTest>>#testWrittenAfterClosedOver >> >> >> Issue URL: https://pharo.fogbugz.com/f/cases/20720 Unused temps >> in Object, OCASTCheckerTest and OCASTClosureAnalyzerTest >> PR URL: https://github.com/pharo-project/pharo/pull/500 >> Diff URL: https://github.com/pharo-project/pharo/pull/500/files >> >> Thanks to astares >> >> * 20721 Unused temps in ProtoObject>>#pointersToExcept: >> >> Fix unused temps in ProtoObject>>#pointersToExcept: >> >> >> Issue URL: https://pharo.fogbugz.com/f/cases/20721 Unused temps >> in ProtoObject>>#pointersToExcept: >> PR URL: https://github.com/pharo-project/pharo/pull/501 >> Diff URL: https://github.com/pharo-project/pharo/pull/501/files >> >> Thanks to astares >> >> * 20715 Unused temps in RBRefactoringChangeTests, >> RPackageClassesSynchronisationTest, RPackageIncrementalTest, ... >> >> Remove unused temps in >> >> RBRefactoringChangeTests>>#testPerformAddRemoveClassMethod >> >> RPackageClassesSynchronisationTest>>#testReorganizeClassByAddingExtensionProtocol >> >> RPackageClassesSynchronisationTest>>#testReorganizeClassByAddingNewProtocolDoesNothing >> >> RPackageExtensionMethodsSynchronisationTest>>#testAddMethodInExtensionCategoryNotExistingCreateANewPackage >> >> RPackageExtensionMethodsSynchronisationTest>>#testAddMethodInExtensionCategoryNotExistingCreateANewPackageAndInstallsMethodInIt >> >> RPackageExtensionMethodsSynchronisationTest>>#testModifyMethodByChangingCode >> RPackageIncrementalTest>>#testAddClassAfterMethods >> RPackageIncrementalTest>>#testAddClassAfterMethodsAtMetaclassToo >> RPackageIncrementalTest>>#testMethodAddition >> RPackageIncrementalTest>>#testPrivateClassRegisterUnregister >> RPackageIncrementalTest>>#testRemoveClassAfterMethods >> RPackageIncrementalTest>>#testRemoveClassRemovesExtensions >> >> RPackageIncrementalTest>>#testRemoveExtensionMethodRemovesExtensionsFromRPackage >> >> RPackageMethodsSynchronisationTest>>#testModifyMethodByMovingFromClassicCategoryToClassicCategoryDoesNothing >> RPackageMonticelloSynchronisationTest>>#testUnloadMCPackageRemovesRPackage >> >> RPackageMonticelloSynchronisationTest>>#testUnregisterMCPackageKeepsRPackage >> RPackageOrganizer>>#systemClassRemovedActionFrom: >> RBRefactoringChangeTests>>#testPerformAddRemoveMethod >> RBRefactoringChangeTests>>#testPerformAddRemoveMethodInteractively >> >> RPackageClassesSynchronisationTest>>#testRecategorizeClassRegisterTheClassMethodsInTheNewPackage >> >> RPackageClassesSynchronisationTest>>#testRecategorizeClassWithMetaClassMethodsRegisterAllClassMethodsInTheNewPackage >> >> RPackageClassesSynchronisationTest>>#testRenameClassUpdateClassDefinedInTheParentPackage >> >> RPackageClassesSynchronisationTest>>#testRenameClassUpdateClassDefinedSelectorsInTheParentPackage >> >> RPackageClassesSynchronisationTest>>#testRenameClassUpdateClassExtensionSelectorsInTheExtendingPackages >> >> RPackageClassesSynchronisationTest>>#testRenameClassUpdateMetaclassDefinedSelectorsInTheParentPackage >> >> RPackageClassesSynchronisationTest>>#testRenameClassUpdateMetaclassExtensionSelectorsInTheExtendingPackages >> >> RPackageClassesSynchronisationTest>>#testRenameClassUpdateOrganizerClassExtendingPackagesMapping >> >> RPackageClassesSynchronisationTest>>#testRenameClassUpdateOrganizerClassPackageMapping >> >> >> Issue URL: https://pharo.fogbugz.com/f/cases/20715 Unused temps >> in RBRefactoringChangeTests, RPackageClassesSynchronisationTest, >> RPackageIncrementalTest, ... >> PR URL: https://github.com/pharo-project/pharo/pull/495 >> Diff URL: https://github.com/pharo-project/pharo/pull/495/files >> >> Thanks to astares >> >> * 20716 Unused temps in MetacelloConfigurationResource, >> MetacelloCoreSymbolicVersionTest, MetacelloPackagesSpecTestCase, >> MetacelloMCProj >> >> Remove unused temps from >> >> MetacelloConfigurationResource>>#project >> MetacelloCoreSymbolicVersionTest>>#testBasicBleedingEdgeVersion >> MetacelloCoreSymbolicVersionTest>>#testBasicStableVersion >> MetacelloCoreSymbolicVersionTest>>#testBleedingEdgeMethod >> MetacelloCoreSymbolicVersionTest>>#testStableVersionMethod >> MetacelloPackagesSpecTestCase>>#testRemoveGroupB >> MetacelloPackagesSpecTestCase>>#testRemoveGroupC >> MetacelloMCProjectSpecTestCase>>#testMCProjectMergeSpec >> >> >> Issue URL: https://pharo.fogbugz.com/f/cases/20716 Unused temps >> in MetacelloConfigurationResource, MetacelloCoreSymbolicVersionTest, >> MetacelloPackagesSpecTestCase, MetacelloMCProj >> PR URL: https://github.com/pharo-project/pharo/pull/497 >> Diff URL: https://github.com/pharo-project/pharo/pull/497/files >> >> Thanks to astares >> >> * 20714-atatput--atatifAbsentPut-should-not-use-Dictionary >> >> >> https://pharo.fogbugz.com/f/cases/20714/at-at-put-at-at-ifAbsentPut-should-… >> >> use "self species" instead of hardcoded Dictionary >> >> >> Issue URL: https://pharo.fogbugz.com/f/cases/20714 >> PR URL: https://github.com/pharo-project/pharo/pull/496 >> Diff URL: https://github.com/pharo-project/pharo/pull/496/files >> >> Thanks to pavel-krivanek >> >> * 20709-do-not-create-pharo-core-symlink-during-the-image-building >> >> >> https://pharo.fogbugz.com/f/cases/20709/do-not-create-pharo-core-symlink-du… >> >> >> Issue URL: https://pharo.fogbugz.com/f/cases/20709 >> PR URL: https://github.com/pharo-project/pharo/pull/492 >> Diff URL: https://github.com/pharo-project/pharo/pull/492/files >> >> Thanks to pavel-krivanek >> >> * 20603-Integration-of-new-bytecode-set-Sista-V1-by-default-green-tests >> >> Issue URL: https://pharo.fogbugz.com/f/cases/20603 >> PR URL: https://github.com/pharo-project/pharo/pull/484 >> Diff URL: https://github.com/pharo-project/pharo/pull/484/files >> >> Thanks to clementbera >> >> * 20707 Unused temps in WindowsStore, WaitfreeQueue, >> VersionnerProjectPanel, >> >> Fix unused temp vars in >> - WindowsStore>>#checkName:fixErrors: >> - WaitfreeQueue>>#size >> - VersionnerProjectPanel>>#config: >> - VersionnerProjectPackagesPanel>>#removeSelectedPackage >> - VSSetDescriptionCommand>>#executeWithMessage: >> >> >> >> https://pharo.fogbugz.com/f/cases/20707/Unused-temps-in-WindowsStore-Waitfr… >> >> >> Issue URL: https://pharo.fogbugz.com/f/cases/20707 Unused temps >> in WindowsStore, WaitfreeQueue, VersionnerProjectPanel, >> PR URL: https://github.com/pharo-project/pharo/pull/490 >> Diff URL: https://github.com/pharo-project/pharo/pull/490/files >> >> Thanks to astares >> >> * 20711 Unused temps in RubTextEditor, RubParagraph, >> RubMethodEditingExample, ReflectiveMethod, RxMatcher >> >> Remove unused temps in >> >> ReflectiveMethod>>#recompileAST >> RubMethodEditingExample>>#open >> RubParagraph>>#selectionRectsFrom:to: >> RubSelectorChooserMorph>>#drawCommonPrefixAreasOn: >> RubTextEditor>>#addDeleteSelectionUndoRecord >> RubTextEditor>>#correctFrom:to:with: >> RubTextEditor>>#exchangeWith: >> RxMatcher>>#currentState >> >> >> Issue URL: https://pharo.fogbugz.com/f/cases/20711 Unused temps >> in RubTextEditor, RubParagraph, RubMethodEditingExample, >> ReflectiveMethod, RxMatcher >> PR URL: https://github.com/pharo-project/pharo/pull/494 >> Diff URL: https://github.com/pharo-project/pharo/pull/494/files >> >> Thanks to astares >> >> * >> 20704-remove-garbageCollect-from-PharoClassInstallermigrateClassestousing >> >> >> https://pharo.fogbugz.com/f/cases/20704/remove-garbageCollect-from-PharoCla… >> >> remove explicit garbage collection >> >> >> Issue URL: https://pharo.fogbugz.com/f/cases/20704 >> PR URL: https://github.com/pharo-project/pharo/pull/489 >> Diff URL: https://github.com/pharo-project/pharo/pull/489/files >> >> Thanks to pavel-krivanek >> >> * 20708 Unused temps in TSequencedConcatenationTest and TextEditor >> >> Remove unused temps in >> TextMorph>>#handleKeystroke: >> TSequencedConcatenationTest>>#testStreamContents >> TSequencedConcatenationTest>>#testStreamContentsProtocol >> TextConverter>>#next:putAll:startingAt:toStream: >> TextConverter>>#nextPutAll:toStream: >> TextEditor>>#addDeleteSelectionUndoRecord >> TextEditor>>#addTypeInUndoRecord >> TextEditor>>#correctFrom:to:with: >> TextEditor>>#dispatchCommandOn:return: >> TextEditor>>#dispatchOn: >> TextEditor>>#mouseUp: >> TextEditor>>#replace:with:and: >> TextEditor>>#unapplyAttribute: >> >> >> Issue URL: https://pharo.fogbugz.com/f/cases/20708 Unused temps >> in TSequencedConcatenationTest and TextEditor >> PR URL: https://github.com/pharo-project/pharo/pull/491 >> Diff URL: https://github.com/pharo-project/pharo/pull/491/files >> >> Thanks to astares >> >> * 20710 Unused temps in StringMorph, SimpleGridExample, >> SmalltalkEditor, SHMethodEditingMode, SelectorChooserMorph >> >> Remove unused temps from >> >> StringMorph>>#drawOnAthensCanvas: >> SimpleGridExample>>#treeMorph >> SmalltalkEditor>>#internalCallToBrowseIt >> SHMethodEditingMode>>#open >> SelectorChooserMorph>>#drawCommonPrefixAreasOn: >> >> >> Issue URL: https://pharo.fogbugz.com/f/cases/20710 Unused temps >> in StringMorph, SimpleGridExample, SmalltalkEditor, >> SHMethodEditingMode, SelectorChooserMorph >> PR URL: https://github.com/pharo-project/pharo/pull/493 >> Diff URL: https://github.com/pharo-project/pharo/pull/493/files >> >> Thanks to astares >> >> * 20697-Give-some-love-to-SocketAddress >> >> SocketAddress is hardly used in the system. >> It is possible to use it more and add some functionality to it. >> Comments and test could be improved as well. >> >> https://pharo.fogbugz.com/f/cases/20697/Give-some-love-to-SocketAddress >> >> >> Issue URL: https://pharo.fogbugz.com/f/cases/20697 >> PR URL: https://github.com/pharo-project/pharo/pull/486 >> Diff URL: https://github.com/pharo-project/pharo/pull/486/files >> >> Thanks to svenvc >> >> * 20702-Add-comments-to-hashMultiply >> >> https://pharo.fogbugz.com/f/cases/20702/Add-comments-to-hashMultiply >> >> use hashMultiply comments provided by Nicolas Celler with some >> >> modifications >> >> Issue URL: https://pharo.fogbugz.com/f/cases/20702 >> PR URL: https://github.com/pharo-project/pharo/pull/487 >> Diff URL: https://github.com/pharo-project/pharo/pull/487/files >> >> Thanks to pavel-krivanek >> >> * 20703-typo-in-WelcomeHelp >> >> https://pharo.fogbugz.com/f/cases/20703/typo-in-WelcomeHelp >> >> fix typo >> >> >> Issue URL: https://pharo.fogbugz.com/f/cases/20703 >> PR URL: https://github.com/pharo-project/pharo/pull/488 >> Diff URL: https://github.com/pharo-project/pharo/pull/488/files >> >> Thanks to pavel-krivanek >> >> * 20647-SortFunction-should-be-composable >> >> Make SortFunction composable >> >> https://pharo.fogbugz.com/f/cases/20647/SortFunction-should-be-composable >> >> Note: impossible to use iceberg to do the commit >> incomprehensible interface / unexpected failures / unclear >> >> error messages >> >> Issue URL: https://pharo.fogbugz.com/f/cases/20647 >> PR URL: https://github.com/pharo-project/pharo/pull/440 >> Diff URL: https://github.com/pharo-project/pharo/pull/440/files >> >> Thanks to nicolas-cellier-aka-nice >> >> * 19942-Glamour-Morphic-Renderer-Spotter-is-only-dead-code >> >> Glamour-Morphic-Renderer-Spotter is only dead code? >> >> >> https://pharo.fogbugz.com/f/cases/19942/Glamour-Morphic-Renderer-Spotter-is… >> >> >> Issue URL: https://pharo.fogbugz.com/f/cases/19942 >> PR URL: https://github.com/pharo-project/pharo/pull/480 >> Diff URL: https://github.com/pharo-project/pharo/pull/480/files >> >> Thanks to MarcusDenker >> >> * 20696-enable-bootstrapping-from-outside-the-repository >> >> >> https://pharo.fogbugz.com/f/cases/20696/enable-bootstrapping-from-outside-t… >> >> >> Issue URL: https://pharo.fogbugz.com/f/cases/20696 >> PR URL: https://github.com/pharo-project/pharo/pull/485 >> Diff URL: https://github.com/pharo-project/pharo/pull/485/files >> >> Thanks to pavel-krivanek >> >> * 20689-Make-Pharo-bootstrap-independent-on-source-repository >> >> >> https://pharo.fogbugz.com/f/cases/20689/Make-Pharo-bootstrap-independent-on… >> >> >> Issue URL: https://pharo.fogbugz.com/f/cases/20689 >> PR URL: https://github.com/pharo-project/pharo/pull/479 >> Diff URL: https://github.com/pharo-project/pharo/pull/479/files >> >> Thanks to pavel-krivanek >> >> * 20693-Incorrect-basename-of-empty-relative-path >> >> 20693 Incorrect basename of empty relative path >> >> - Modify Path and subclasses to return the current directory >> >> for an empty relative path. >> >> - Add PathTest>>testBasenameNoParent to confirm correct behaviour. >> >> >> Issue URL: https://pharo.fogbugz.com/f/cases/20693 >> PR URL: https://github.com/pharo-project/pharo/pull/481 >> Diff URL: https://github.com/pharo-project/pharo/pull/481/files >> >> Thanks to akgrant43 >> >> * 20678-selecting-of-a-method-version-causes-DNU >> >> Adding this message as a way of having polymorphism with the >> >> different versions of Message Browser >> >> >> Issue >> https://pharo.fogbugz.com/f/cases/20678/selecting-of-a-method-version-cause… >> >> >> Issue URL: https://pharo.fogbugz.com/f/cases/20678 >> PR URL: https://github.com/pharo-project/pharo/pull/482 >> Diff URL: https://github.com/pharo-project/pharo/pull/482/files >> >> Thanks to tesonep >> >> * 20686-disabling-of-FreeType-fonts-should-set-bitmap-Source-Pro-fonts >> >> >> https://pharo.fogbugz.com/f/cases/20686/disabling-of-FreeType-fonts-should-… >> >> set bitmap source pro fonts after disabling of FreeType >> >> >> Issue URL: https://pharo.fogbugz.com/f/cases/20686 >> PR URL: https://github.com/pharo-project/pharo/pull/476 >> Diff URL: https://github.com/pharo-project/pharo/pull/476/files >> >> Thanks to pavel-krivanek >> >> * 19291-suspendedEventHandler-property-seems-unused >> >> suspendedEventHandler property seems unused >> >> >> https://pharo.fogbugz.com/f/cases/19291/suspendedEventHandler-property-seem… >> >> >> Issue URL: https://pharo.fogbugz.com/f/cases/19291 >> PR URL: https://github.com/pharo-project/pharo/pull/466 >> Diff URL: https://github.com/pharo-project/pharo/pull/466/files >> >> Thanks to MarcusDenker >> >> * 20685-Do-not-use-hardcoded-URLs-in-system-baselines >> >> >> https://pharo.fogbugz.com/f/cases/20685/Do-not-use-hardcoded-URLs-in-system… >> >> use repository URL of the baseline package for loading of >> >> other baselines from the same repository >> >> Issue URL: https://pharo.fogbugz.com/f/cases/20685 >> PR URL: https://github.com/pharo-project/pharo/pull/475 >> Diff URL: https://github.com/pharo-project/pharo/pull/475/files >> >> Thanks to pavel-krivanek >> >> * 20166-wrong-cliprect-on-transformed-athens-canvas >> >> >> https://pharo.fogbugz.com/f/cases/20166/wrong-cliprect-on-transformed-athen… >> >> fix proposed by Nicolai Hess >> >> >> Issue URL: https://pharo.fogbugz.com/f/cases/20166 >> PR URL: https://github.com/pharo-project/pharo/pull/477 >> Diff URL: https://github.com/pharo-project/pharo/pull/477/files >> >> Thanks to pavel-krivanek >> >> * >> 20264-Date-gtInspectorDetailsIn-is-incorrectly-using-a-Block-for-the-title-so-selection-is-not-remembered >> >> Fix GT Inspector usage: title's should not be blocks but pure >> >> Strings for them to be remembered as selected in the UI >> >> >> Improve several GT Inspector views in small details (especially Socket) >> >> Touched Date, Time, DateAndTime, Duration, Socket, ZnMessage, >> >> ZnHeaders and ZnMimePart views. >> >> >> >> https://pharo.fogbugz.com/f/cases/20264/Date-gtInspectorDetailsIn-is-incorr… >> >> >> Issue URL: https://pharo.fogbugz.com/f/cases/20264 >> PR URL: https://github.com/pharo-project/pharo/pull/471 >> Diff URL: https://github.com/pharo-project/pharo/pull/471/files >> >> Thanks to svenvc >> >> * 20679-Reloading-of-OSWindow-SDL2-causes-Tonel-parsing-error >> >> >> https://pharo.fogbugz.com/f/cases/20679/Reloading-of-OSWindow-SDL2-causes-T… >> >> fix broken UTF8 character >> >> >> Issue URL: https://pharo.fogbugz.com/f/cases/20679 >> PR URL: https://github.com/pharo-project/pharo/pull/473 >> Diff URL: https://github.com/pharo-project/pharo/pull/473/files >> >> Thanks to pavel-krivanek >> >> * 20676 Categorize uncategorized methods in classes starting with K >> >> Categorize uncategorized methods >> >> No change in behavior, only categorization >> >> >> >> https://pharo.fogbugz.com/f/cases/20676/Categorize-uncategorized-methods-in… >> >> >> Issue URL: https://pharo.fogbugz.com/f/cases/20676 Categorize >> uncategorized methods in classes starting with K >> PR URL: https://github.com/pharo-project/pharo/pull/470 >> Diff URL: https://github.com/pharo-project/pharo/pull/470/files >> >> Thanks to astares >> >> * 20674 Categorize uncategorized methods in classes starting with J >> >> Categorize uncategorized methods in >> - JobProgressBarMorph >> - JoinSection >> - JoinSide >> >> >> Issue URL: https://pharo.fogbugz.com/f/cases/20674 Categorize >> uncategorized methods in classes starting with J >> PR URL: https://github.com/pharo-project/pharo/pull/468 >> Diff URL: https://github.com/pharo-project/pharo/pull/468/files >> >> Thanks to astares >> >> * 20677-Improve-system-dependencies-tests >> >> https://pharo.fogbugz.com/f/cases/20677/Improve-system-dependencies-testss >> >> clean system dependencies testing >> >> >> Issue URL: https://pharo.fogbugz.com/f/cases/20677 >> PR URL: https://github.com/pharo-project/pharo/pull/472 >> Diff URL: https://github.com/pharo-project/pharo/pull/472/files >> >> Thanks to pavel-krivanek >> >> * 20673 Categorize uncategorized methods in classes starting with H >> >> Categorize uncategorized methods in >> - HEFraction >> - HEScaledDecimal >> >> Only categorization, no change in behavior >> >> >> Issue URL: https://pharo.fogbugz.com/f/cases/20673 Categorize >> uncategorized methods in classes starting with H >> PR URL: https://github.com/pharo-project/pharo/pull/467 >> Diff URL: https://github.com/pharo-project/pharo/pull/467/files >> >> Thanks to astares >> >> * 20675 Categorize uncategorized methods in classes starting with D >> >> Categorize uncategorized method in DatePresenter >> >> >> Issue URL: https://pharo.fogbugz.com/f/cases/20675 Categorize >> uncategorized methods in classes starting with D >> PR URL: https://github.com/pharo-project/pharo/pull/469 >> Diff URL: https://github.com/pharo-project/pharo/pull/469/files >> >> Thanks to astares >> >> * 20671-Extend-system-dependencies-tests-on-whole-image >> >> >> https://pharo.fogbugz.com/f/cases/20671/Extend-system-dependencies-tests-on… >> >> dependency testing for whole image >> >> >> Issue URL: https://pharo.fogbugz.com/f/cases/20671 >> PR URL: https://github.com/pharo-project/pharo/pull/464 >> Diff URL: https://github.com/pharo-project/pharo/pull/464/files >> >> Thanks to pavel-krivanek >> >> * 20670-unused-var-in-generateDefaultFileOutResultsName >> >> unused var in #generateDefaultFileOutResultsName >> >> >> https://pharo.fogbugz.com/f/cases/20670/unused-var-in-generateDefaultFileOu… >> >> >> Issue URL: https://pharo.fogbugz.com/f/cases/20670 >> PR URL: https://github.com/pharo-project/pharo/pull/465 >> Diff URL: https://github.com/pharo-project/pharo/pull/465/files >> >> Thanks to MarcusDenker >> >> * 20668-add-breakpoints-menu-to-Nautilus-segment-icons >> >> https://pharo.fogbugz.com/f/cases/20668 >> >> fix breakpoints placement for wrapping text >> >> >> Issue URL: https://pharo.fogbugz.com/f/cases/20668 >> PR URL: https://github.com/pharo-project/pharo/pull/463 >> Diff URL: https://github.com/pharo-project/pharo/pull/463/files >> >> Thanks to pavel-krivanek >> >> * 20055-immediateByteSubclass-is-deadcoe >> >> immediateByteSubclass: is deadcoe >> >> https://pharo.fogbugz.com/f/cases/20055/immediateByteSubclass-is-deadcoe >> >> >> Issue URL: https://pharo.fogbugz.com/f/cases/20055 >> PR URL: https://github.com/pharo-project/pharo/pull/462 >> Diff URL: https://github.com/pharo-project/pharo/pull/462/files >> >> Thanks to MarcusDenker >> >> * >> 20263-Debugger-DoesNotUnderstandDebugAction-is-missing-a-defaultHelp-method-so-hover-help-shows-missing >> >> Debugger DoesNotUnderstandDebugAction is missing a >> >> #defaultHelp method so hover help shows missing >> >> >> https://pharo.fogbugz.com/f/cases/20263/ >> >> >> Issue URL: https://pharo.fogbugz.com/f/cases/20263 >> PR URL: https://github.com/pharo-project/pharo/pull/460 >> Diff URL: https://github.com/pharo-project/pharo/pull/460/files >> >> Thanks to MarcusDenker >> >> * >> 17654-SpecPreDebugWindow-and-subclasses-relies-on-doesNotUnderstand-delegation-to-find-the-stackPane >> >> SpecPreDebugWindow and subclasses relies on #doesNotUnderstand >> >> delegation to find the stackPane >> >> >> https://pharo.fogbugz.com/f/cases/17654 >> >> >> Issue URL: https://pharo.fogbugz.com/f/cases/17654 >> PR URL: https://github.com/pharo-project/pharo/pull/461 >> Diff URL: https://github.com/pharo-project/pharo/pull/461/files >> >> Thanks to MarcusDenker >> >> * >> 20363-ThemeIconsdownloadTo-has-an-argument-which-is-never-referenced-in-code >> >> fix for >> >> >> https://pharo.fogbugz.com/f/cases/20363/ThemeIcons-downloadTo-has-an-argume… >> >> Issue URL: https://pharo.fogbugz.com/f/cases/20363 >> PR URL: https://github.com/pharo-project/pharo/pull/453 >> Diff URL: https://github.com/pharo-project/pharo/pull/453/files >> >> Thanks to MarcusDenker >> >> * 20667-Be-able-to-install-breakpoints-by-clicking-on-segment-icons-area >> >> >> https://pharo.fogbugz.com/f/cases/20667/Be-able-to-install-breakpoints-by-c… >> >> click on segment icons area adds breakpoint at the beginning of the line >> >> >> Issue URL: https://pharo.fogbugz.com/f/cases/20667 >> PR URL: https://github.com/pharo-project/pharo/pull/459 >> Diff URL: https://github.com/pharo-project/pharo/pull/459/files >> >> Thanks to pavel-krivanek >> >> * 20582-atat-messages-call-errorKeyNotFound >> >> Fix for at:at: messages call errorKeyNotFound. >> - use errorKeyNotFound: >> >> >> https://pharo.fogbugz.com/f/cases/20582/at-at-messages-call-errorKeyNotFound >> >> >> Issue URL: https://pharo.fogbugz.com/f/cases/20582 >> PR URL: https://github.com/pharo-project/pharo/pull/454 >> Diff URL: https://github.com/pharo-project/pharo/pull/454/files >> >> Thanks to MarcusDenker >> >> * 20664-set-the-display-size-sooner >> >> https://pharo.fogbugz.com/f/cases/20664/set-the-display-size-sooner >> >> >> Issue URL: https://pharo.fogbugz.com/f/cases/20664 >> PR URL: https://github.com/pharo-project/pharo/pull/458 >> Diff URL: https://github.com/pharo-project/pharo/pull/458/files >> >> Thanks to pavel-krivanek >> >> * >> 20499-Examples-in-GlamourPresentationModel-should-have-no-gtExamplePragma >> >> 20499 >> Examples in GlamourPresentationModel should have no <gtExamplePragma> >> >> https://pharo.fogbugz.com/f/cases/20499 >> >> >> Issue URL: https://pharo.fogbugz.com/f/cases/20499 >> PR URL: https://github.com/pharo-project/pharo/pull/455 >> Diff URL: https://github.com/pharo-project/pharo/pull/455/files >> >> Thanks to MarcusDenker >> >> * 20662-displaying-method-versions-in-Nautilus-causes-DNU >> >> >> https://pharo.fogbugz.com/f/cases/20662/displaying-method-versions-in-Nauti… >> >> add clearUndoManager to DiffPresenter >> >> >> Issue URL: https://pharo.fogbugz.com/f/cases/20662 >> PR URL: https://github.com/pharo-project/pharo/pull/457 >> Diff URL: https://github.com/pharo-project/pharo/pull/457/files >> >> Thanks to pavel-krivanek >> >> * 20661-Fixing-test-from-debugger-should-mark-test-as-green-when-proceed- >> >> Now runCaseForDebug: removes passed test case from errors and failures. >> This logic is not inside addPass: method directly to not >> >> affect bug suite result collecting because it can become slow if it >> will clean errors and failures for every green test. >> >> Maybe in future we can improve this part. >> >> >> https://pharo.fogbugz.com/f/cases/20661/Fixing-test-from-debugger-should-ma… >> >> >> Issue URL: https://pharo.fogbugz.com/f/cases/20661 >> PR URL: https://github.com/pharo-project/pharo/pull/456 >> Diff URL: https://github.com/pharo-project/pharo/pull/456/files >> >> Thanks to dionisiydk >> >> * 20611-leftover-logCr-debug-logging-in-GLEmptyBrickarea >> >> remove left over debug code >> >> https://pharo.fogbugz.com/f/cases/20611/leftover-logCr-debug-logging-in-GLE… >> >> >> Issue URL: https://pharo.fogbugz.com/f/cases/20611 >> PR URL: https://github.com/pharo-project/pharo/pull/452 >> Diff URL: https://github.com/pharo-project/pharo/pull/452/files >> >> Thanks to MarcusDenker >> >> * >> 20552-Breakpoints-stay-in-the-breakpoints-browser-even-after-their-method-is-recompiled >> >> Issue URL: >> >> >> https://pharo.fogbugz.com/f/cases/20552/Breakpoints-stay-in-the-breakpoints… >> >> Breakpoint class now subscribes to the MethodChanged >> >> announcement, and remove from its list the breakpoints from methods >> that get recompiled. >> >> Also added a test for this behaviour. >> >> >> Issue URL: https://pharo.fogbugz.com/f/cases/20552 >> PR URL: https://github.com/pharo-project/pharo/pull/447 >> Diff URL: https://github.com/pharo-project/pharo/pull/447/files >> >> Thanks to dupriezt >> >> * 20657-Command-B-in-playground-does-not-work-the-save-way-as-printit >> >> https://pharo.fogbugz.com/f/cases/20657 >> >> try to select line if no AST node found >> >> >> Issue URL: https://pharo.fogbugz.com/f/cases/20657 >> PR URL: https://github.com/pharo-project/pharo/pull/450 >> Diff URL: https://github.com/pharo-project/pharo/pull/450/files >> >> Thanks to pavel-krivanek >> >> * 19972-Implementers-code-pane-undo-goes-too-far >> >> Clearing the undo history when changing the selected method in the list. >> Also adding a way of clearing this history from the TextPresenter >> >> >> Issue URL: https://pharo.fogbugz.com/f/cases/19972 >> PR URL: https://github.com/pharo-project/pharo/pull/451 >> Diff URL: https://github.com/pharo-project/pharo/pull/451/files >> >> Thanks to tesonep >> >> * 20656-Nautilus-comment-panel-got-broken-by-asLayoutFrame-cleans >> >> https://pharo.fogbugz.com/f/cases/20656 >> >> fix layout frame fraction >> >> >> Issue URL: https://pharo.fogbugz.com/f/cases/20656 >> PR URL: https://github.com/pharo-project/pharo/pull/449 >> Diff URL: https://github.com/pharo-project/pharo/pull/449/files >> >> Thanks to pavel-krivanek >> >> * 20650-Release-cleanup-failures >> >> https://pharo.fogbugz.com/f/cases/20650/Release-cleanup-failures >> >> >> Issue URL: https://pharo.fogbugz.com/f/cases/20650 >> PR URL: https://github.com/pharo-project/pharo/pull/448 >> Diff URL: https://github.com/pharo-project/pharo/pull/448/files >> >> Thanks to pavel-krivanek >> >> * 20648-Provide-Bitmap-variant-of-Source-Code-fonts >> >> >> https://pharo.fogbugz.com/f/cases/20648/Provide-Bitmap-variant-of-Source-Co… >> >> based on PR https://github.com/pharo-project/pharo/pull/439 >> >> >> Issue URL: https://pharo.fogbugz.com/f/cases/20648 >> PR URL: https://github.com/pharo-project/pharo/pull/441 >> Diff URL: https://github.com/pharo-project/pharo/pull/441/files >> >> Thanks to pavel-krivanek >> >> * 20644-Load-Bitmap-DejaVu-fonts-from-data-files-instead-of-a-Fuel-file >> >> >> https://pharo.fogbugz.com/f/cases/20644/Load-Bitmap-DejaVu-fonts-from-data-… >> >> >> Issue URL: https://pharo.fogbugz.com/f/cases/20644 >> PR URL: https://github.com/pharo-project/pharo/pull/439 >> Diff URL: https://github.com/pharo-project/pharo/pull/439/files >> >> Thanks to pavel-krivanek >> >> * 20643 Dark and light theme should not be version specific >> >> Rename Pharo3DarkTheme into PharoDarkTheme >> Rename Pharo3Theme into PharoLightTheme >> and deprecate empty subclasses like Pharo3DarkTheme >> and Pharo3Theme (but keep them for compatibility) >> >> >> Issue URL: https://pharo.fogbugz.com/f/cases/20643 Dark and >> light theme should not be version specific >> PR URL: https://github.com/pharo-project/pharo/pull/438 >> Diff URL: https://github.com/pharo-project/pharo/pull/438/files >> >> Thanks to astares >> >> * Care on dirty package OpalTools >> >> https://pharo.fogbugz.com/f/cases/20642/Care-on-dirty-package-OpalTools >> >> fix dirty package extension to be in OpalCompiler-Tools >> >> >> Issue URL: https://pharo.fogbugz.com/f/cases/Care on dirty >> package OpalTools >> PR URL: https://github.com/pharo-project/pharo/pull/437 >> Diff URL: https://github.com/pharo-project/pharo/pull/437/files >> >> Thanks to astares >> >> * 20520 Package "OpalTools" should be "OpalCompiler-Tools" >> >> Rename package OpalTools -> OpalCompiler-Tools >> >> >> https://pharo.fogbugz.com/f/cases/20520/Package-OpalTools-should-be-OpalCom… >> >> >> Issue URL: https://pharo.fogbugz.com/f/cases/20520 Package >> "OpalTools" should be "OpalCompiler >> PR URL: https://github.com/pharo-project/pharo/pull/436 >> Diff URL: https://github.com/pharo-project/pharo/pull/436/files >> >> Thanks to astares >> >> * Stupid use of asLayoutFrame should be eliminated first pass. >> >> Fuck my image just crashed again! ;((((((((((((((((((((((( >> >> >> Issue URL: https://pharo.fogbugz.com/f/cases/Stupid use of >> asLayoutFrame should be eliminated first pass. >> PR URL: https://github.com/pharo-project/pharo/pull/434 >> Diff URL: https://github.com/pharo-project/pharo/pull/434/files >> >> Thanks to Ducasse >> >> * 20640 Categorize uncategorized methods in classes starting with "P" >> >> Categorize methods. >> >> >> So only categorization - no change in behavior >> >> >> Issue URL: https://pharo.fogbugz.com/f/cases/20640 Categorize >> uncategorized methods in classes starting with "P" >> PR URL: https://github.com/pharo-project/pharo/pull/433 >> Diff URL: https://github.com/pharo-project/pharo/pull/433/files >> >> Thanks to astares >>

Nov. 23, 2017

Re: [Pharo-dev] OpalCompiler evaluate speed

by ClÃ©ment Bera

Hi Nicolas. Just some comments: Another thing you can try is to remove the allocation of Opal's IR. It seems people use the IR only through the IRBuilder, so the API can be kept but it can generate directly bytecode instead of IR then bytecode. Removing those allocations would speed things up. It means merging IRFix / IRTranslator / IRBytecodeGenerator somehow and have the IRBuilder API directly call the new resulting merged class. Another thing is that when Opal became the default compiler, I evaluated the speed and saw it was slower, but when loading large projects it seemed loading time was dominated by Monticello / source reading / source loading and the compilation time was overall not that significant (< 20% of time). I don't know if this is still the case with GIT. I have problems currently when editing some large methods (it seems in the IDE the method is compiled at each keystroke...) and when doing OpalCompiler recompileAll (which I do often since I edit bytecode sets) but else the performance of Opal seems to be OK. Evaluate performance may be relevant in some cases but I've never found such cases outside of the IDE in production. Best ! Clement On Thu, Nov 23, 2017 at 9:41 PM, Nicolas Cellier < nicolas.cellier.aka.nice(a)gmail.com> wrote: > > > 2017-11-22 0:31 GMT+01:00 Ben Coman <btc(a)openinworld.com>: > >> >> >> On 22 November 2017 at 05:49, Nicolas Cellier < >> nicolas.cellier.aka.nice(a)gmail.com> wrote: >> >>> >>> >>> 2017-11-21 14:19 GMT+01:00 Nicolas Cellier < >>> nicolas.cellier.aka.nice(a)gmail.com>: >>> >>>> I have an ArbitraryPrecisionFloatTests doing an exhaustive test for >>>> printing and reevaluating all positve half precision float. >>>> >>>> That's about 2^15 or approximately 32k loop which evaluate snippets like >>>> >>>> (ArbitraryPrecisionFloat readFrom: '1.123' readStream numBits: 10) >>>> >>>> The test was naively written with Compiler evaluate: and was using the >>>> legacy Compiler. >>>> >>>> If I rewrite self class compiler evaluate: the test times out. >>>> Let's see what increase is necessary: >>>> >>>> [ ArbitraryPrecisionFloatTest new testPrintAndEvaluate ] timeToRun. >>>> -> 3s with legacy Compiler >>>> -> 14s with OpalCompiler >>>> >>>> It's not unexpected that intermediate representation (IR) reification >>>> has a cost, but here the 4.5x is a bit too much... >>>> This test did account for 1/4 of total test duration already (3s out of >>>> 12s). >>>> With Opal, the total test duration doubles... (14s out of 23s) >>>> >>>> So let's analyze the hot spot with: >>>> >>>> MessageTally spyOn: [ ArbitraryPrecisionFloatTest new >>>> testPrintAndEvaluate ]. >>>> >>>> (I didn't use AndreasSystemProfiler becuase outputs seems a bit >>>> garbbled, no matter since the primitives do not account that much, a >>>> MessageTally will do the job) >>>> >>>> I first see a hot spot which does not seem that necessary: >>>> >>>> | |24.6% {3447ms} RBMethodNode(RBProgramNode)>>formattedCode >>>> >>>> From the comments I understand that AST-based stuff requires a pattern >>>> (DoIt) and an explicit return (^), but this expensive formatting seems too >>>> much for just evaluating. i think that we should change that. >>>> >>>> Then comes: >>>> >>>> | |20.7% {2902ms} RBMethodNode>>generate: >>>> >>>> which is split in two halves, ATS->IR and IR->bytecode >>>> >>>> | | |9.3% {1299ms} RBMethodNode>>generateIR >>>> >>>> | | | |11.4% {1596ms} IRMethod>>generate: >>>> >>>> But then I see this cost a 2nd time which also leave room for progress: >>>> >>>> | |10.9% {1529ms} RBMethodNode>>generateIR >>>> >>>> | | |12.9% {1814ms} IRMethod>>generate: >>>> >>>> The first is in RBMethodNode>>generateWithSource, the second in >>>> OpalCompiler>>compile >>>> >>>> Last comes the parse time (sourceCode -> AST) >>>> >>>> | 13.2% {1858ms} OpalCompiler>>parse >>>> >>>> Along with semantic analysis >>>> >>>> | 6.0% {837ms} OpalCompiler>>doSemanticAnalysis >>>> >>>> ----------------------------------- >>>> >>>> For comparison, the legacy Compiler decomposes into: >>>> >>>> | |61.5% {2223ms} Parser>>parse:class:category:n >>>> oPattern:context:notifying:ifFail: >>>> >>>> which more or less covers parse time + semantic analysis time. >>>> That means that Opal does a fair work for this stage. >>>> >>>> Then, the direct AST->byteCode phase is: >>>> >>>> | 16.9% {609ms} MethodNode>>generate >>>> >>>> IR costs almost a 5x on this phase, but we know it's the price to pay >>>> for the additional features that it potentially offers. If only we would do >>>> it once... >>>> >>>> And that's all for the legacy one... >>>> >>>> -------------------------------------- >>>> >>>> This little exercize shows that a 2x acceleration of OpalCompiler >>>> evaluate seems achievable: >>>> - simplify the uselessely expensive formatted code >>>> - generate bytecodes once, not twice >>>> >>>> Then it will be a bit more 2x slower than legacy, which is a better >>>> trade for yet to come superior features potentially brought by Opal. >>>> >>>> It would be interesting to carry same analysis on method compilation >>>> >>> >>> Digging further here is what I find: >>> >>> compile sends generate: and answer a CompiledMethod >>> translate sends compile but throw the CompiledMethod away, and just >>> answer the AST. >>> Most senders of translate will also generate: (thus we generate: twice >>> quite often, loosing a 2x factor in compilation). >>> >>> A 2x gain is a huge gain when installing big code bases, especially if >>> the custom is to throw image away and reconstruct. >>> No matter if a bot does the job, it does it for twice many watts and at >>> the end, we're waiting for the bot. >>> >>> However, before changing anything, further clarification is required: >>> translate does one more thing, it catches ReparseAfterSourceEditing and >>> retry compilation (once). >>> So my question: are there some cases when generate: will cause >>> ReparseAfterSourceEditing? >>> >> >> I don't know the full answer about other cases, but I can provide the >> background why ReparseAfterSourceEditing was added. >> >> IIRC, a few years ago with the move to an AST based system, there was a >> problem with syntax highlighting where >> the AST referenced its original source which caused highlighting offsets >> when reference to source modified in the editor. >> Trying to work backwards from modified source to update all AST elements >> source-location proved an intractable problem. >> The workaround I found was to move only in a forward direction >> regenerating AST from source every keystroke. >> Performance was acceptable so this became the permanent solution. >> >> I don't have access to an image to check, but you should find >> ReparseAfterSourceEditing raised only in one location near editor #changed: >> Maybe this should activate only for interactively modified code, and >> disabled/bypassed for bulk loading code. >> For testing purposes commenting it out should not harm the system, just >> produce visual artifacts in syntax highlighting. >> >> >> >>> That could happen in generation phase if some byte code limit is >>> exceeded, and an interactive handling corrects code... >>> I did not see any such condition, but code base is huge... >>> >> >> At worst, the impact should only be a temporary visual artifact. >> Corrected on the next keystroke. >> (unless ReparseAfterSourceEditing has been adopted for other than >> original purpose, but I'd guess not) >> >> cheers -ben >> >> Hi Ben, > Thanks for information. > We must keep ReparseAfterSourceEditing, it does its job. > > But it just sounds like we have an inversion: > > translate (source code->AST) does call compile (source code->AST->bytecode > in a CompiledMethod) > > I would expect the other way around: if we want to compile, we need to > translate first. > If we want to translate, we don't really need to compile, unless there's > an hidden reason... > Thus my question: is there an hidden reason? > -- ClÃ©ment BÃ©ra Pharo consortium engineer https://clementbera.wordpress.com/ BÃ¢timent B 40, avenue Halley 59650 Villeneuve d'Ascq

Nov. 23, 2017

Re: [Pharo-dev] Deploying using the latest minimal image of Pharo (6.1)

by despotadesdibujau

>Hi Gabriel >This is cool. >Thanks for sharing it with us. >I really want an object responsible for deploying an app. :) >Your effort is nice in that directory. Keep pushing >Stef Thanks!!! Maxi Tabacman suggests me to reify the deployment process. I thought of something like to get up a minimal image from inside the development image, then to start the deployment process from the development image. I suppose that I would need to use Espell Object Spaces (Guillermo Polito), but in this case, I would need a special virtual machine (Oz Virtual Machine)... Something like Tornado, but not using the "Run Fail Grow" approach, but using a BaselineOf or ConfigurationOf approach. Another idea (simpler than the idea above) is to communicate the two images using Teapot or Sockets: The Development image sends orders to the minimal image until it becomes on the deployment image. For the moment I need to test the process (on Pharo 6 and 7) using more complex applications until it becomes a reliable process. Gabriel -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Nov. 23, 2017

Re: [Pharo-dev] OpalCompiler evaluate speed

by Nicolas Cellier

2017-11-22 0:31 GMT+01:00 Ben Coman <btc(a)openinworld.com>: > > > On 22 November 2017 at 05:49, Nicolas Cellier <nicolas.cellier.aka.nice@ > gmail.com> wrote: > >> >> >> 2017-11-21 14:19 GMT+01:00 Nicolas Cellier <nicolas.cellier.aka.nice@gmai >> l.com>: >> >>> I have an ArbitraryPrecisionFloatTests doing an exhaustive test for >>> printing and reevaluating all positve half precision float. >>> >>> That's about 2^15 or approximately 32k loop which evaluate snippets like >>> >>> (ArbitraryPrecisionFloat readFrom: '1.123' readStream numBits: 10) >>> >>> The test was naively written with Compiler evaluate: and was using the >>> legacy Compiler. >>> >>> If I rewrite self class compiler evaluate: the test times out. >>> Let's see what increase is necessary: >>> >>> [ ArbitraryPrecisionFloatTest new testPrintAndEvaluate ] timeToRun. >>> -> 3s with legacy Compiler >>> -> 14s with OpalCompiler >>> >>> It's not unexpected that intermediate representation (IR) reification >>> has a cost, but here the 4.5x is a bit too much... >>> This test did account for 1/4 of total test duration already (3s out of >>> 12s). >>> With Opal, the total test duration doubles... (14s out of 23s) >>> >>> So let's analyze the hot spot with: >>> >>> MessageTally spyOn: [ ArbitraryPrecisionFloatTest new >>> testPrintAndEvaluate ]. >>> >>> (I didn't use AndreasSystemProfiler becuase outputs seems a bit >>> garbbled, no matter since the primitives do not account that much, a >>> MessageTally will do the job) >>> >>> I first see a hot spot which does not seem that necessary: >>> >>> | |24.6% {3447ms} RBMethodNode(RBProgramNode)>>formattedCode >>> >>> From the comments I understand that AST-based stuff requires a pattern >>> (DoIt) and an explicit return (^), but this expensive formatting seems too >>> much for just evaluating. i think that we should change that. >>> >>> Then comes: >>> >>> | |20.7% {2902ms} RBMethodNode>>generate: >>> >>> which is split in two halves, ATS->IR and IR->bytecode >>> >>> | | |9.3% {1299ms} RBMethodNode>>generateIR >>> >>> | | | |11.4% {1596ms} IRMethod>>generate: >>> >>> But then I see this cost a 2nd time which also leave room for progress: >>> >>> | |10.9% {1529ms} RBMethodNode>>generateIR >>> >>> | | |12.9% {1814ms} IRMethod>>generate: >>> >>> The first is in RBMethodNode>>generateWithSource, the second in >>> OpalCompiler>>compile >>> >>> Last comes the parse time (sourceCode -> AST) >>> >>> | 13.2% {1858ms} OpalCompiler>>parse >>> >>> Along with semantic analysis >>> >>> | 6.0% {837ms} OpalCompiler>>doSemanticAnalysis >>> >>> ----------------------------------- >>> >>> For comparison, the legacy Compiler decomposes into: >>> >>> | |61.5% {2223ms} Parser>>parse:class:category:n >>> oPattern:context:notifying:ifFail: >>> >>> which more or less covers parse time + semantic analysis time. >>> That means that Opal does a fair work for this stage. >>> >>> Then, the direct AST->byteCode phase is: >>> >>> | 16.9% {609ms} MethodNode>>generate >>> >>> IR costs almost a 5x on this phase, but we know it's the price to pay >>> for the additional features that it potentially offers. If only we would do >>> it once... >>> >>> And that's all for the legacy one... >>> >>> -------------------------------------- >>> >>> This little exercize shows that a 2x acceleration of OpalCompiler >>> evaluate seems achievable: >>> - simplify the uselessely expensive formatted code >>> - generate bytecodes once, not twice >>> >>> Then it will be a bit more 2x slower than legacy, which is a better >>> trade for yet to come superior features potentially brought by Opal. >>> >>> It would be interesting to carry same analysis on method compilation >>> >> >> Digging further here is what I find: >> >> compile sends generate: and answer a CompiledMethod >> translate sends compile but throw the CompiledMethod away, and just >> answer the AST. >> Most senders of translate will also generate: (thus we generate: twice >> quite often, loosing a 2x factor in compilation). >> >> A 2x gain is a huge gain when installing big code bases, especially if >> the custom is to throw image away and reconstruct. >> No matter if a bot does the job, it does it for twice many watts and at >> the end, we're waiting for the bot. >> >> However, before changing anything, further clarification is required: >> translate does one more thing, it catches ReparseAfterSourceEditing and >> retry compilation (once). >> So my question: are there some cases when generate: will cause >> ReparseAfterSourceEditing? >> > > I don't know the full answer about other cases, but I can provide the > background why ReparseAfterSourceEditing was added. > > IIRC, a few years ago with the move to an AST based system, there was a > problem with syntax highlighting where > the AST referenced its original source which caused highlighting offsets > when reference to source modified in the editor. > Trying to work backwards from modified source to update all AST elements > source-location proved an intractable problem. > The workaround I found was to move only in a forward direction > regenerating AST from source every keystroke. > Performance was acceptable so this became the permanent solution. > > I don't have access to an image to check, but you should find > ReparseAfterSourceEditing raised only in one location near editor #changed: > Maybe this should activate only for interactively modified code, and > disabled/bypassed for bulk loading code. > For testing purposes commenting it out should not harm the system, just > produce visual artifacts in syntax highlighting. > > > >> That could happen in generation phase if some byte code limit is >> exceeded, and an interactive handling corrects code... >> I did not see any such condition, but code base is huge... >> > > At worst, the impact should only be a temporary visual artifact. Corrected > on the next keystroke. > (unless ReparseAfterSourceEditing has been adopted for other than original > purpose, but I'd guess not) > > cheers -ben > > Hi Ben, Thanks for information. We must keep ReparseAfterSourceEditing, it does its job. But it just sounds like we have an inversion: translate (source code->AST) does call compile (source code->AST->bytecode in a CompiledMethod) I would expect the other way around: if we want to compile, we need to translate first. If we want to translate, we don't really need to compile, unless there's an hidden reason... Thus my question: is there an hidden reason?

Nov. 23, 2017

Re: [Pharo-dev] [PHARO 7.0A] NEXT ENHANCEMENTS

by Torsten Bergmann

Nov. 23, 2017

Re: [Pharo-dev] [Pharo-users] [ANN] Pharo TechTalk 21 Nov: Discord Demo

by Juraj Kubelka

Hi, the new version is available here: https://www.youtube.com/watch?v=y1EzOnfHUe0 <https://www.youtube.com/watch?v=y1EzOnfHUe0> Hopefully it helps :-) Juraj > On Nov 22, 2017, at 15:45, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > Juraj Kubelka wrote >> I will upload recording I have on my computer. It is clear. > > Thanks! > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html >

Nov. 23, 2017

[Pharo 7.0-dev] Build #322: 18217-Settings-What-are-Renkaku-rules

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #322 was: SUCCESS. The Pull Request #527 was integrated: "18217-Settings-What-are-Renkaku-rules" Pull request url: https://github.com/pharo-project/pharo/pull/527 Issue Url: https://pharo.fogbugz.com/f/cases/18217 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 23, 2017

Re: [Pharo-dev] nil inspect

by Dimitris Chloupis

ah ok my bad it was self that referred of course back to itself. if you inspect nil , you get indeed UndefinedObject and if you look at instance variables, it has self and it references nil. I was confused by that because I did not notice it was self. On Thu, Nov 23, 2017 at 6:26 PM Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > 2017-11-23 17:01 GMT+01:00 Dimitris Chloupis <kilon.alios(a)gmail.com>: > >> yeah i see it now, I asked earlier on because I did not have access to a >> computer (was replying from my tablet). I see now that is an object, though >> its weird that nil is an instance of UndefinedObject but yet, that class >> has nil as instance variable >> >> not one of the good designs of Smalltalk, if this is not Pharo specific. >> >> I do not see the point of being an instance of a class and also an >> instance variable of that class. Is there a point ? >> > > Where you find instance variable? > Class definition has no variables: > > Object subclass: #UndefinedObject > instanceVariableNames: '' > classVariableNames: '' > package: 'Kernel-Objects' > UndefinedObject class > instanceVariableNames: '' > > > >> >> On Thu, Nov 23, 2017 at 12:23 PM Guillermo Polito < >> guillermopolito(a)gmail.com> wrote: >> >>> Hi Dimitris, >>> >>> nil **is** an object. A normal object. >>> >>> From your wikipedia quote: The true, false, and nil pseudo-variables >>> are *singleton* <https://en.wikipedia.org/wiki/Singleton_pattern> >>> * instances*. >>> >>> You can try many things to try to convince yourself: >>> >>> - nil class => UndefinedObject >>> - nil sizeInMemory => 8 (2 object headers, no instance variables) >>> >>> You can also take a look at the bootstrap and see how it is created. >>> >>> And it may make sense to have the same inspection tabs as any other >>> normal object that has no instance variables. >>> >>> On Thu, Nov 23, 2017 at 11:14 AM, Dimitris Chloupis < >>> kilon.alios(a)gmail.com> wrote: >>> >>>> looks like wikipedia agrees with me, but I have to confess never looked >>>> at the Pharo implementation so I may still be wrong >>>> >>>> "*Smalltalk-80* syntax is rather minimalist, based on only a handful >>>> of declarations and reserved words. In fact, only six "keywords" are >>>> reserved in Smalltalk: true, false, nil, self, super, and thisContext. >>>> These are actually called *pseudo-variables*, identifiers that follow >>>> the rules for variable identifiers but denote bindings that the programmer >>>> cannot change. The true, false, and nil pseudo-variables are singleton >>>> <https://en.wikipedia.org/wiki/Singleton_pattern> instances. self and >>>> super refer to the receiver of a message within a method activated in >>>> response to that message, but sends to super are looked up in the >>>> superclass of the method's defining class rather than the class of the >>>> receiver, which allows methods in subclasses to invoke methods of the same >>>> name in superclasses. thisContext refers to the current activation >>>> record. The only built-in language constructs are message sends, >>>> assignment, method return and literal syntax for some objects. From its >>>> origins as a language for children of all ages, standard Smalltalk syntax >>>> uses punctuation in a manner more like English than mainstream coding >>>> languages. The remainder of the language, including control structures for >>>> conditional evaluation and iteration, is implemented on top of the built-in >>>> constructs by the standard Smalltalk class library. (For performance >>>> reasons, implementations may recognize and treat as special some of those >>>> messages; however, this is only an optimization and is not hardwired into >>>> the language syntax.)" >>>> >>>> https://en.wikipedia.org/wiki/Smalltalk >>>> >>>> Or maybe there is more here tha meets the eye ? >>>> >>>> On Thu, Nov 23, 2017 at 12:10 PM Dimitris Chloupis < >>>> kilon.alios(a)gmail.com> wrote: >>>> >>>>> is it ? I always thought it was just one of those things that is not >>>>> an object , together with super and self. I vaguelly remember that 5-6 >>>>> words in Smalltalk are not objects. >>>>> >>>>> If it is an actual object and not something else wrapped in a very >>>>> thin object, I can see the reason for inspection. Otherwise I cannot say I >>>>> see it. >>>>> >>>>> On Thu, Nov 23, 2017 at 10:45 AM Denis Kudriashov < >>>>> dionisiydk(a)gmail.com> wrote: >>>>> >>>>>> But it is not nothing. It is real object. >>>>>> >>>>>> 2017-11-23 9:03 GMT+01:00 Dimitris Chloupis <kilon.alios(a)gmail.com>: >>>>>> >>>>>>> Personally I love it >>>>>>> >>>>>>> what you find when you search for nothing ? >>>>>>> >>>>>>> Nothing >>>>>>> >>>>>>> :D >>>>>>> >>>>>>> On Wed, Nov 22, 2017 at 10:23 PM Stephane Ducasse < >>>>>>> stepharo.self(a)gmail.com> wrote: >>>>>>> >>>>>>>> Indeed I do not really like the blank window. >>>>>>>> >>>>>>>> On Sat, Nov 18, 2017 at 10:18 PM, Nicolas Cellier < >>>>>>>> nicolas.cellier.aka.nice(a)gmail.com> wrote: >>>>>>>> >>>>>>>>> Ah OK, it's expected then? >>>>>>>>> I find that surprising, because I could maybe want to look at meta >>>>>>>>> side like I can for other elementary objects: >>>>>>>>> >>>>>>>>> [image: Images intÃ©grÃ©es 1] >>>>>>>>> >>>>>>>>> 2017-11-18 22:03 GMT+01:00 Aliaksei Syrel <alex.syrel(a)gmail.com>: >>>>>>>>> >>>>>>>>>> Yes >>>>>>>>>> >>>>>>>>>> [image: Inline images 1] >>>>>>>>>> >>>>>>>>>> Cheers, >>>>>>>>>> Alex >>>>>>>>>> >>>>>>>>>> On 18 November 2017 at 21:56, Nicolas Cellier < >>>>>>>>>> nicolas.cellier.aka.nice(a)gmail.com> wrote: >>>>>>>>>> >>>>>>>>>>> Anyone tried 'nil inspect' recently? >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>> >>> >>> >>> -- >>> >>> >>> >>> Guille Polito >>> >>> Research Engineer >>> >>> Centre de Recherche en Informatique, Signal et Automatique de Lille >>> >>> CRIStAL - UMR 9189 >>> >>> French National Center for Scientific Research - *http://www.cnrs.fr >>> <http://www.cnrs.fr>* >>> >>> >>> *Web:* *http://guillep.github.io* <http://guillep.github.io> >>> >>> *Phone: *+33 06 52 70 66 13 <+33%206%2052%2070%2066%2013> >>> >> >

Nov. 23, 2017