July 2016 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [pharo-project/pharo-core] ec7b0e: 60137

by Andrei Chis

+1 On Wed, Jul 6, 2016 at 8:19 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > I'll try once more to explain. > > You like the catalog, don't you ? It was your idea in the first place. > With this feature you can just type XML, CSV, JSON or whatever and it will > suggest a couple of catalog projects that you can install with just one > click, no need to open any tool you don't even know. This is especially > good for new people. IT IS A FANTASTIC FEATURE, IT IS THE WAY THINGS SHOULD > WORK. It leverages all the work put in the catalog. > > Is Spotter or any other part of Pharo perfect ? No. > > For many people, Spotter make a huge functional difference, we use it > every minute. If it would hang or block the image even once a day, any of > us would complain loudly. > > Conclusion: it works for 99% of the people/cases. > > Even in the 1% where there is a problem, it is not 100% sure it is related > to the catalog searching. In the last concrete issue reported, the guy > tried disabling the catalog searching AND IT MADE NO DIFFERENCE ! > > So again, why turn it off ? It is an overreaction, not engineering. > > The underlying problem is that in some very rare, hard to reproduce cases > we cannot reliably detect that there is no network. That's about it. > > Note also that almost every application or app today will do some network > calls, this is how the world work - we should be able to do the same with > Pharo, not run away and kill every feature that does a network call. > > > On 06 Jul 2016, at 18:14, stepharo <stepharo(a)free.fr> wrote: > > > > Who vote to put it in? > > > > Seriously I think that my main concern is about getting Pharo stable in > any occasion and not giving > > > > a bad impression of the system. I takes enough time to build traction > and such glitches can spoil > > > > our effort in no time. "Yes Pharo froze." > > > > So it would be nice to care take of such aspect. > > > > I do not understand why super users do not manage to put a reference to > on in the preferences. > > > > Sorry esteban but I do not buy your argument that something off is > remove. No it is off. > > > > Stef > >>> On 06 Jul 2016, at 09:52, GitHub <noreply(a)github.com> wrote: > >>> > >>> 18674 Turn spotter catalog off by default > >>> https://pharo.fogbugz.com/f/cases/18674 > >> We did not agree on this, at all, there was no public discussion, no > vote. > >> > >> > > > > > > >

July 6, 2016

Re: [Pharo-dev] AthensCairoSurface not getting garbage collected

by J.F. Rick

Nicolai, THANKS! That worked. I no longer have any AthensCairoCanvas hanging around after executing "CairoBackendCache flush". Cheers, Jeff On Sun, Jul 3, 2016 at 11:58 AM Nicolai Hess <nicolaihess(a)gmail.com> wrote: > Hi Jeff, > > if you use forms to paint on an AthensCairoCanvas, they are cached in the > CairoBackendCache, > can you try to flush that cache whith > CairoBackendCache flush. > > > 2016-06-18 18:36 GMT+02:00 J.F. Rick <self(a)je77.com>: > >> I'm using Athens rendering for my multi-touch applications on Pharo5. As >> part of that, I create a surface: >> surface := AthensCairoSurface extent: bounds extent asIntegerPoint. >> >> Though the object creating that surface is deleted, the surface sticks >> around. So, each time I run the app, I get another instance of >> AthensCairoSurface hanging around. That means all the forms stick around as >> well. So my image can quickly grow towards the 1GB size. >> >> Is there anything I can do about that? Can I manually get the surface to >> delete itself? >> >> Cheers, >> >> Jeff >> > >

July 6, 2016

Re: [Pharo-dev] [pharo-project/pharo-core] ec7b0e: 60137

by Sven Van Caekenberghe

I'll try once more to explain. You like the catalog, don't you ? It was your idea in the first place. With this feature you can just type XML, CSV, JSON or whatever and it will suggest a couple of catalog projects that you can install with just one click, no need to open any tool you don't even know. This is especially good for new people. IT IS A FANTASTIC FEATURE, IT IS THE WAY THINGS SHOULD WORK. It leverages all the work put in the catalog. Is Spotter or any other part of Pharo perfect ? No. For many people, Spotter make a huge functional difference, we use it every minute. If it would hang or block the image even once a day, any of us would complain loudly. Conclusion: it works for 99% of the people/cases. Even in the 1% where there is a problem, it is not 100% sure it is related to the catalog searching. In the last concrete issue reported, the guy tried disabling the catalog searching AND IT MADE NO DIFFERENCE ! So again, why turn it off ? It is an overreaction, not engineering. The underlying problem is that in some very rare, hard to reproduce cases we cannot reliably detect that there is no network. That's about it. Note also that almost every application or app today will do some network calls, this is how the world work - we should be able to do the same with Pharo, not run away and kill every feature that does a network call. > On 06 Jul 2016, at 18:14, stepharo <stepharo(a)free.fr> wrote: > > Who vote to put it in? > > Seriously I think that my main concern is about getting Pharo stable in any occasion and not giving > > a bad impression of the system. I takes enough time to build traction and such glitches can spoil > > our effort in no time. "Yes Pharo froze." > > So it would be nice to care take of such aspect. > > I do not understand why super users do not manage to put a reference to on in the preferences. > > Sorry esteban but I do not buy your argument that something off is remove. No it is off. > > Stef >>> On 06 Jul 2016, at 09:52, GitHub <noreply(a)github.com> wrote: >>> >>> 18674 Turn spotter catalog off by default >>> https://pharo.fogbugz.com/f/cases/18674 >> We did not agree on this, at all, there was no public discussion, no vote. >> >> > >

July 6, 2016

Re: [Pharo-dev] [pharo-project/pharo-core] a813b2: 60138

by Marcus Denker

> On 06 Jul 2016, at 18:16, stepharo <stepharo(a)free.fr> wrote: > > I always found such kind of changes totally obscure and it would be nice to have a description. > Fixes issues: - 18450 GT-Tools: "Do not use #ifNotNilDo:ifNil:, #ifNil:ifNotNilDo:, #ifNotNilDo:" - 18453 GT-Tools: "do not use #ifEmpty:ifNotEmptyDo: #ifNotEmptyDo: #ifNotEmptyDo:ifEmpty:â - 18431 attach glmpopplers shortcut to the textarea instead of the scroll pane - Esteban's change to GLMAction This was mostly me pushing for getting the trivial things *DONE* and not wait another 3 weeksâ¦ (I should have just committed slices, the overhead with committing and syncing is to high for trivial refactorings) Marcus

July 6, 2016

Re: [Pharo-dev] [pharo-project/pharo-core] a813b2: 60138

by stepharo

I always found such kind of changes totally obscure and it would be nice to have a description. Stef Le 6/7/16 Ã 11:29, GitHub a Ã©crit : > Branch: refs/heads/6.0 > Home: https://github.com/pharo-project/pharo-core > Commit: a813b2cc8d72ea3442e7ab1e9be5856203ea4c3f > https://github.com/pharo-project/pharo-core/commit/a813b2cc8d72ea3442e7ab1e… > Author: Jenkins Build Server <board(a)pharo-project.org> > Date: 2016-07-06 (Wed, 06 Jul 2016) > > Changed paths: > M ConfigurationOfGTEventRecorder.package/ConfigurationOfGTEventRecorder.class/instance/versions/version018_.st > M ConfigurationOfGTPlaygroundCore.package/ConfigurationOfGTPlaygroundCore.class/instance/symbolic versions/stable_.st > M ConfigurationOfGTPlaygroundCore.package/ConfigurationOfGTPlaygroundCore.class/instance/versions/version310_.st > A ConfigurationOfGTPlaygroundCore.package/ConfigurationOfGTPlaygroundCore.class/instance/versions/version311_.st > M ConfigurationOfGTSpotter.package/ConfigurationOfGTSpotter.class/instance/versions/version212_.st > M GT-BytecodeDebugger.package/extension/Context/instance/gtBytecodeDebuggerRetrieveContextValues.st > M GT-EventRecorder.package/GTEventPacking.class/instance/private/updateAnnouncement_for_.st > A GT-EventRecorder.package/GlobalIdentifier.class/class/class initialization/initialize.st > A GT-EventRecorder.package/GlobalIdentifier.class/class/system startup/startUp_.st > R GT-Inspector.package/GTExample.class/class/examples/gtExample.st > A GT-Inspector.package/GTExample.class/class/examples/gtExampleFromPragma.st > R GT-Inspector.package/GTExample.class/instance/pragma-selectors/afterClass_selector_arguments_.st > R GT-Inspector.package/GTExample.class/instance/pragma-selectors/afterFinishClass_selector_.st > R GT-Inspector.package/GTExample.class/instance/pragma-selectors/afterFinishClass_selector_arguments_.st > R GT-Inspector.package/GTExample.class/instance/pragma-selectors/afterFinish_.st > R GT-Inspector.package/GTExample.class/instance/pragma-selectors/after_arguments_.st > A GT-Inspector.package/GTExample.class/instance/public/signalableExceptions.st > M GT-Inspector.package/GTExampleEvaluator.class/README.md > M GT-Inspector.package/GTExampleEvaluator.class/definition.st > M GT-Inspector.package/GTExampleEvaluator.class/instance/initializing/initialize.st > R GT-Inspector.package/GTExampleEvaluator.class/instance/primitives/primitiveProcessExampleAfterFinish_.st > R GT-Inspector.package/GTExampleEvaluator.class/instance/primitives/primitiveProcessExampleAfter_.st > M GT-Inspector.package/GTExampleEvaluator.class/instance/primitives/primitiveProcessExample_withArguments_.st > A GT-Inspector.package/GTExampleEvaluator.class/instance/private/newResultFor_.st > A GT-Inspector.package/GTExampleEvaluator.class/instance/private/processAfter_.st > A GT-Inspector.package/GTExampleEvaluator.class/instance/private/processAfter_withResult_.st > M GT-Inspector.package/GTExampleEvaluator.class/instance/private/process_withArguments_.st > R GT-Inspector.package/GTExampleEvaluator.class/instance/private/withLinkContextFor_do_.st > M GT-Inspector.package/GTExampleEvaluator.class/instance/public/result.st > R GT-Inspector.package/GTExampleLinkContext.class/README.md > R GT-Inspector.package/GTExampleLinkContext.class/definition.st > R GT-Inspector.package/GTExampleLinkContext.class/instance/accessing/example.st > R GT-Inspector.package/GTExampleLinkContext.class/instance/accessing/example_.st > R GT-Inspector.package/GTExampleLinkContext.class/instance/private/install.st > R GT-Inspector.package/GTExampleLinkContext.class/instance/private/onLinkNode_arguments_.st > R GT-Inspector.package/GTExampleLinkContext.class/instance/private/onLinkNode_at_put_.st > R GT-Inspector.package/GTExampleLinkContext.class/instance/private/uninstall.st > R GT-Inspector.package/GTExampleLinkContext.class/instance/private/withLinksDo_.st > R GT-Inspector.package/GTExampleLinkContext.class/instance/public/arguments.st > R GT-Inspector.package/GTExampleLinkContext.class/instance/public/do_.st > R GT-Inspector.package/GTExampleLinkContext.class/instance/testing/hasLinks.st > M GT-Inspector.package/GTExampleTestCase.class/instance/private/runExampleContainers_.st > A GT-Inspector.package/GTExampleTestCase.class/instance/private/runExample_.st > R GT-Inspector.package/GTExampleTestCase.class/instance/private/runExample_fromContainer_.st > M GT-Inspector.package/GTInspector.class/class/inspecting/inspectorExtendingMethods.st > M GT-Inspector.package/GTInspector.class/instance/building/compose.st > M GT-Inspector.package/GTInspectorHelp.class/class/accessing/pages.st > A GT-Inspector.package/extension/Class/instance/gtInspectorGTExamplesIn_.st > M GT-Inspector.package/extension/CompiledMethod/instance/gtExample.st > A GT-Inspector.package/extension/CompiledMethod/instance/gtExampleValue.st > A GT-Inspector.package/extension/CompiledMethod/instance/valueWithReceiver_possibleArguments_.st > M GT-Inspector.package/extension/ProtoObject/instance/gtInspectorPresentationsFromPragmas_In_inContext_.st > A GT-InspectorExtensions-Core.package/extension/MethodChunk/instance/gtDisplayOn_.st > A GT-InspectorExtensions-Core.package/extension/RBAbstractCondition/instance/gtInspectorChildren.st > A GT-InspectorExtensions-Core.package/extension/RBAbstractCondition/instance/gtInspectorTreeIn_.st > A GT-InspectorExtensions-Core.package/extension/RBConjunctiveCondition/instance/gtInspectorChildren.st > M GT-Spotter.package/GTSpotter.class/class/inspecting/spotterExtendingMethods.st > R GT-SpotterExtensions-Core.package/GTSelector.class/instance/ui/spotterSendersFor_.st > A GT-SpotterExtensions-Core.package/GTSelector.class/instance/ui/spotterUsersFor_.st > M GT-SpotterExtensions-Core.package/PragmaType.class/instance/accessing/pragmas.st > A GT-SpotterExtensions-Core.package/PragmaType.class/instance/accessing/users.st > M GT-SpotterExtensions-Core.package/PragmaType.class/instance/ui/gtInspectorPragmasIn_.st > A GT-SpotterExtensions-Core.package/PragmaType.class/instance/ui/gtInspectorUsersIn_.st > R GT-SpotterExtensions-Core.package/PragmaType.class/instance/ui/spotterSendersFor_.st > A GT-SpotterExtensions-Core.package/PragmaType.class/instance/ui/spotterUsersFor_.st > M GT-SpotterExtensions-Core.package/extension/MCWorkingCopy/class/gtExampleWorkingCopy.st > M GT-SpotterExtensions-Core.package/extension/MCWorkingCopy/instance/allAncestors.st > M GT-SpotterExtensions-Core.package/extension/MCWorkingCopy/instance/nextAncestors.st > M GT-SpotterExtensions-Core.package/extension/MCWorkingCopy/instance/spotterPackageFor_.st > M GT-SpotterExtensions-Core.package/extension/RPackage/instance/spotterMonticelloPackageFor_.st > M GT-SpotterExtensions-Core.package/extension/RPackage/instance/spotterMonticelloWorkingCopyFor_.st > M GT-Tests-Spotter.package/GTSpotterStepTest.class/instance/private-navigation/pragmas_inPackages_.st > A GT-Tests-Spotter.package/GTSpotterStepTest.class/instance/private-navigation/users_.st > A GT-Tests-Spotter.package/GTSpotterStepTest.class/instance/private-navigation/users_inPackages_.st > M GT-Tests-Spotter.package/GTSpotterStepTest.class/instance/tests/testProcessorForPragmasThenDiveIn.st > M Glamour-Core.package/GLMAction.class/definition.st > A Glamour-Core.package/GLMAction.class/instance/accessing/enabledCondition.st > A Glamour-Core.package/GLMAction.class/instance/accessing/enabledCondition_.st > A Glamour-Core.package/GLMAction.class/instance/testing/isEnabledOn_.st > A Glamour-Core.package/GLMPresentation.class/instance/scripting actions/selectionAct_entitled_enabledWhen_.st > M Glamour-Examples.package/GLMBasicExamples.class/instance/actions examples/staticAndDynamicMenu.st > M Glamour-Morphic-Renderer.package/GLMMorphicWidgetRenderer.class/instance/private/menuIn_for_.st > M Glamour-Morphic-Renderer.package/GLMMorphicWidgetRenderer.class/instance/private/moreToolbarActions_on_.st > M Glamour-Morphic-Widgets.package/GLMMorphicModel.class/instance/callbacks/menu_.st > M Glamour-Morphic-Widgets.package/GLMPopper.class/instance/private/updateWithString_from_.st > M Glamour-Morphic-Widgets.package/GLMPrintPopper.class/instance/public/openFromRubric_withResult_.st > M Glamour-Morphic-Widgets.package/GLMTreeMorphNodeModel.class/instance/menu/menu_shifted_.st > M PragmaCollector.package/PragmaCollector.class/instance/system changes/removedEventOccurs_.st > R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60137.st > A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60138.st > R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60137.st > A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60138.st > M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st > > Log Message: > ----------- > 60138 > Moose > > http://files.pharo.org/image/60/60138.zip > >

July 6, 2016

Re: [Pharo-dev] [pharo-project/pharo-core] ec7b0e: 60137

by stepharo

Who vote to put it in? Seriously I think that my main concern is about getting Pharo stable in any occasion and not giving a bad impression of the system. I takes enough time to build traction and such glitches can spoil our effort in no time. "Yes Pharo froze." So it would be nice to care take of such aspect. I do not understand why super users do not manage to put a reference to on in the preferences. Sorry esteban but I do not buy your argument that something off is remove. No it is off. Stef >> On 06 Jul 2016, at 09:52, GitHub <noreply(a)github.com> wrote: >> >> 18674 Turn spotter catalog off by default >> https://pharo.fogbugz.com/f/cases/18674 > We did not agree on this, at all, there was no public discussion, no vote. > >

July 6, 2016

Re: [Pharo-dev] Failure in Tests Cases

by Yuriy Tymchuk

Hi. while you are on this, Iâd also like to have fueled-out errors (this implies storing the errors in the report objects). Also there are two unresolved issues with worker: https://pharo.fogbugz.com/f/cases/18499/ https://pharo.fogbugz.com/f/cases/18502/ Maybe you will be able to uncover what is the problem while improving the worker. Cheers. Uko > On 06 Jul 2016, at 17:12, tesonep(a)gmail.com wrote: > > Hi to all, > I have tried to fix the CI process to show the failures and errors in the tests in a more descriptive way, not only showing the failed test case, but also the error and the stack trace of it. > > After checking the problem, I have seen that the failures (and also errors) are not registered with the Error that has produce the failure. > > Of course, then I remembered that is why the TestRunner reruns the tests to allow the debugging of the error. > > What do you think of adding the produced exception to the TestResult? > > Do you think it can have any other consequences? If it has, what if only adding to the CI process? > Or perhaps storing a reduced version of the error (perhaps a String representation, or something a lighter than the Error) > > Thanks for all. > > > -- > Pablo Tesone. > tesonep(a)gmail.com <mailto:tesonep@gmail.com>

July 6, 2016

Failure in Tests Cases

by tesonep＠gmail.com

Hi to all, I have tried to fix the CI process to show the failures and errors in the tests in a more descriptive way, not only showing the failed test case, but also the error and the stack trace of it. After checking the problem, I have seen that the failures (and also errors) are not registered with the Error that has produce the failure. Of course, then I remembered that is why the TestRunner reruns the tests to allow the debugging of the error. What do you think of adding the produced exception to the TestResult? Do you think it can have any other consequences? If it has, what if only adding to the CI process? Or perhaps storing a reduced version of the error (perhaps a String representation, or something a lighter than the Error) Thanks for all. -- Pablo Tesone. tesonep(a)gmail.com

July 6, 2016

[pharo-project/pharo-core]

by GitHub

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

July 6, 2016

[pharo-project/pharo-core] 382ab2: 60139

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 382ab247b7ff419185670b875e426a6d80765eab https://github.com/pharo-project/pharo-core/commit/382ab247b7ff419185670b87… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-07-06 (Wed, 06 Jul 2016) Changed paths: R Glamour-Morphic-Brick.package/GLMBrick.class/instance/brick-structure-testing/isFirstInOwner.st M Glamour-Morphic-Brick.package/GLMBrickStructureTrait.class/instance/brick-structure-testing/isFirstInOwner.st M Glamour-Morphic-Brick.package/GLMBrickStructureTrait.class/instance/brick-structure-testing/isLastInOwner.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60138.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60139.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60138.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60139.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Slot.package/AbstractClassModification.class/instance/accessing/layout_.st M Slot.package/extension/Behavior/instance/layout.st M Slot.package/extension/Behavior/instance/layout_.st M Traits.package/TBehavior.class/instance/accessing/typeOfClass.st Log Message: ----------- 60139 16636 Rename layout to classLayout (step 4 deprecate) https://pharo.fogbugz.com/f/cases/16636 18449 Glamour: "Do not use #ifNotNilDo:ifNil:, #ifNil:ifNotNilDo:, #ifNotNilDo:" https://pharo.fogbugz.com/f/cases/18449 http://files.pharo.org/image/60/60139.zip

July 6, 2016