- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] confused about the "image opening session"

by Esteban Lorenzano

> On 06 Jul 2016, at 09:00, Christophe Demarey <Christophe.Demarey(a)inria.fr> wrote: > > yes, what is bad now is that there is âno crash detectorâ. > If you quit an image without saving, you will get the epicea browser. I do not want it in this case. When I do not save, it is on purpose. > Maybe a flag should be set when you quit the image (by saving or not). This way, if the flag is not present at image startup, you could guess a crash. +100 > >> Le 5 juil. 2016 Ã 21:50, stepharo <stepharo(a)free.fr> a Ã©crit : >> >> Hi >> >> I saw that we have a new cool feature that presents changes that would have been loaded but not save in the image. >> >> Now I got confused because several times I prompted with this list and I do not see how I ended up having it >> >> since I save my image and did not get crash (or idea that I lost changes). >> >> Is it me that do not understand correctly this feature? >> >> At the minimum it would be nice to have a little bit more explanation about what is happening. >> >> Because I imagine new guys coming and seeing this list without any further explanation could be confused. >> >> Stef >> >> > >

July 6, 2016

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

by Marcus Denker

> On 06 Jul 2016, at 10:12, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > >> 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. > I only know that there where problems. Marcus

July 6, 2016

[pharo-project/pharo-core]

by GitHub

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

July 6, 2016

[pharo-project/pharo-core] a813b2: 60138

by GitHub

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 Sven Van Caekenberghe

> 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

[pharo-project/pharo-core]

by GitHub

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

July 6, 2016

[pharo-project/pharo-core] ec7b0e: 60137

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: ec7b0efd3372758bb785c059576ee2264986477b https://github.com/pharo-project/pharo-core/commit/ec7b0efd3372758bb785c059… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-07-06 (Wed, 06 Jul 2016) Changed paths: M Epicea.package/EpClassRemoval.class/instance/accessing/behaviorAffectedName.st M Epicea.package/extension/Class/instance/asEpiceaRingDefinition.st M Graphics-Canvas.package/FormCanvas.class/instance/other/warpFrom_toRect_.st M Graphics-Display Objects.package/Form.class/instance/analyzing/rectangleEnclosingPixelsNotOfColor_.st M Graphics-Display Objects.package/Form.class/instance/scaling%2C rotation/magnify_by_smoothing_.st M Graphics-Primitives.package/BitBlt.class/class/deprecated/current.st M OpalCompiler-Core.package/DebuggerMethodMapOpal.class/instance/public/tempNamed_in_.st M OpalCompiler-Core.package/DebuggerMethodMapOpal.class/instance/public/tempNamed_in_put_.st M OpalCompiler-Core.package/DebuggerMethodMapOpal.class/instance/public/tempNamesForContext_.st A OpalCompiler-Tests.package/OCContextTempMappingTest.class/instance/test - block arguments/testAccessingBlockArgumentNoneOptimizedBlock.st A OpalCompiler-Tests.package/OCContextTempMappingTest.class/instance/test - block arguments/testAccessingBlockArgumentOptimizedBlock.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60136.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60137.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60136.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60137.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60137 18690 deprecated BitBlt class>>#current https://pharo.fogbugz.com/f/cases/18690 17434 debugger missing block local var for optimized blocks https://pharo.fogbugz.com/f/cases/17434 18674 Turn spotter catalog off by default https://pharo.fogbugz.com/f/cases/18674 18608 Impossible to delete a class https://pharo.fogbugz.com/f/cases/18608 http://files.pharo.org/image/60/60137.zip

July 6, 2016

Re: [Pharo-dev] confused about the "image opening session"

by Christophe Demarey

yes, what is bad now is that there is âno crash detectorâ. If you quit an image without saving, you will get the epicea browser. I do not want it in this case. When I do not save, it is on purpose. Maybe a flag should be set when you quit the image (by saving or not). This way, if the flag is not present at image startup, you could guess a crash. > Le 5 juil. 2016 Ã 21:50, stepharo <stepharo(a)free.fr> a Ã©crit : > > Hi > > I saw that we have a new cool feature that presents changes that would have been loaded but not save in the image. > > Now I got confused because several times I prompted with this list and I do not see how I ended up having it > > since I save my image and did not get crash (or idea that I lost changes). > > Is it me that do not understand correctly this feature? > > At the minimum it would be nice to have a little bit more explanation about what is happening. > > Because I imagine new guys coming and seeing this list without any further explanation could be confused. > > Stef > >

July 6, 2016

Re: [Pharo-dev] pharo 5 segfault (stack size?) [FreeBSD]

by Petr Fischer

> On Fri, Jun 17, 2016 at 8:04 PM, Max Leske <maxleske(a)gmail.com> wrote: > > Hi Petr, > > > > That looks like a bug with FreeType with our FFI. It should actually have been fixed but I donât know if the VM for FreeBSD is up to date. Can you post the output of âSmalltalk vm versionâ? > > > > Cheers, > > Max > > > > Petr, Based on Max's suggestion, have you tried turning FreeType off? > World > System > Settings > Apperance > Use Free Type. > IIUC this will fall back to using built-in Strike Fonts [1], and maybe > just bypass the issue?? With FreeType off - still segfaulting. I will move this topic (+ how to debug this segfaults) to the vm mailinglist. Thanks! > > [1] http://pharo.gemtalksystems.com/book/LanguageAndLibraries/fonts_in_pharo/st… > > P.S. Just curious, in the philosophy of trimming down the Pharo Image > size, are Strike Fonts a candidate for removal. It seems like having > an in-Image fall back is potentially useful when porting to new > platforms. > > cheers -ben > > > >> On 17 Jun 2016, at 13:26, Petr Fischer <petr.fischer(a)me.com> wrote: > >> > >> Hello, I got some random segfaults (while loading Seaside) with 32 bit spur vm on FreeBSD - can someone (with low level knowledge) decode attached log? > >> Is this some problem with stack size? Can I fix this? > >> > >> Log: > >> http://pastebin.com/raw/NpFUnjh0 > >> > >> There is "**StackOverflow**" lines n the log... > >> > >> Thanks! pf > >> > > > > >

July 6, 2016

Re: [Pharo-dev] confused about the "image opening session"

by Nicolas Passerini

Me too :) On Tue, Jul 5, 2016 at 9:50 PM, stepharo <stepharo(a)free.fr> wrote: > Hi > > I saw that we have a new cool feature that presents changes that would > have been loaded but not save in the image. > > Now I got confused because several times I prompted with this list and I > do not see how I ended up having it > > since I save my image and did not get crash (or idea that I lost changes). > > Is it me that do not understand correctly this feature? > > At the minimum it would be nice to have a little bit more explanation > about what is happening. > > Because I imagine new guys coming and seeing this list without any further > explanation could be confused. > > Stef > > >

July 5, 2016