August 2014 - Pharo-dev - lists.pharo.org

[pharo-project/pharo-core]

by GitHub

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

Aug. 7, 2014

[pharo-project/pharo-core] 169593: 40155

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 16959331cd19e06bd5e2eed73d68b213ef119be0 https://github.com/pharo-project/pharo-core/commit/16959331cd19e06bd5e2eed7… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-08-07 (Thu, 07 Aug 2014) Changed paths: M Graphics-Primitives.package/Color.class/instance/conversions/asColorref.st A Graphics-Tests.package/ColorTest.class/instance/asserting/assertColorrefFor_equals_.st A Graphics-Tests.package/ColorTest.class/instance/testing/testAsColorrefPrimaryColors.st A Graphics-Tests.package/ColorTest.class/instance/testing/testPrintHtmlString.st R Graphics-Tests.package/ColorTest.class/instance/tests/testPrintHtmlString.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script155.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40155.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A Spec-Inspector.package/EyePointerExplorer.class/README.md A Spec-Inspector.package/EyePointerExplorer.class/class/accessing/label.st A Spec-Inspector.package/EyePointerExplorer.class/class/instance creation/openOn_.st A Spec-Inspector.package/EyePointerExplorer.class/class/instance creation/openStrongOn_.st A Spec-Inspector.package/EyePointerExplorer.class/definition.st A Spec-Inspector.package/EyePointerExplorer.class/instance/accessing/object_.st A Spec-Inspector.package/EyePointerExplorer.class/instance/accessing/roots.st A Spec-Inspector.package/EyePointerExplorer.class/instance/accessing/title.st A Spec-Inspector.package/EyePointerExplorer.class/instance/accessing/tree.st A Spec-Inspector.package/EyePointerExplorer.class/instance/api/childrenForObject_.st A Spec-Inspector.package/EyePointerExplorer.class/instance/api/onlyStrong.st A Spec-Inspector.package/EyePointerExplorer.class/instance/event-handling/objectChanged.st A Spec-Inspector.package/EyePointerExplorer.class/instance/initialization/initialize.st A Spec-Inspector.package/EyePointerWrapper.class/README.md A Spec-Inspector.package/EyePointerWrapper.class/class/instance creation/wrap_.st A Spec-Inspector.package/EyePointerWrapper.class/definition.st A Spec-Inspector.package/EyePointerWrapper.class/instance/accessing/wrappedObject.st A Spec-Inspector.package/EyePointerWrapper.class/instance/accessing/wrappedObject_.st A Spec-Inspector.package/EyePointerWrapper.class/instance/printing/printString.st A Spec-Inspector.package/PointerEyeElement.class/README.md A Spec-Inspector.package/PointerEyeElement.class/class/instance creation/host_value_.st A Spec-Inspector.package/PointerEyeElement.class/definition.st A Spec-Inspector.package/PointerEyeElement.class/instance/accessing/host_.st A Spec-Inspector.package/PointerEyeElement.class/instance/accessing/longLabel.st A Spec-Inspector.package/PointerEyeElement.class/instance/accessing/value.st A Spec-Inspector.package/PointerEyeElement.class/instance/accessing/value_.st R System-Support.package/extension/RGMethodDefinition/instance/callers.st R Tool-Base.package/extension/CompiledMethod/instance/callers.st Log Message: ----------- 40155 13774 EyePointerExplorer https://pharo.fogbugz.com/f/cases/13774 13792 remove #callers https://pharo.fogbugz.com/f/cases/13792 13784 Color>>#asColorref ignores blue https://pharo.fogbugz.com/f/cases/13784 http://files.pharo.org/image/40/40155.zip

Aug. 7, 2014

[pharo-project/pharo-core]

by GitHub

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

Aug. 7, 2014

[pharo-project/pharo-core] dc3a94: 40154

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: dc3a940516ddca4f28ac8bdd5992a00da0d1a4c2 https://github.com/pharo-project/pharo-core/commit/dc3a940516ddca4f28ac8bdd… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-08-07 (Thu, 07 Aug 2014) Changed paths: R Morphic-Base.package/StringMorph.class/instance/drawing/lookTranslucent.st R OpalCompiler-Core.package/OCInstanceScope.class/instance/initializing/vars_.st R OpalCompiler-Core.package/OCInstanceVariable.class/README.md R OpalCompiler-Core.package/OCInstanceVariable.class/definition.st R OpalCompiler-Core.package/OCInstanceVariable.class/instance/accessing/index.st R OpalCompiler-Core.package/OCInstanceVariable.class/instance/accessing/index_.st R OpalCompiler-Core.package/OCInstanceVariable.class/instance/accessing/name.st R OpalCompiler-Core.package/OCInstanceVariable.class/instance/accessing/name_.st R OpalCompiler-Core.package/OCInstanceVariable.class/instance/emitting/emitStore_.st R OpalCompiler-Core.package/OCInstanceVariable.class/instance/emitting/emitValue_.st R OpalCompiler-Core.package/OCInstanceVariable.class/instance/testing/isInstance.st M OpalCompiler-Core.package/extension/Object/instance/mustBeBooleanInMagic_.st M Ring-Core-Containers.package/RGContainer.class/instance/adding%2Fremoving/addPackageNamed_.st M Ring-Core-Containers.package/RGNamespace.class/instance/adding elements/addGlobalVariableNamed_.st M Ring-Core-Containers.package/RGNamespace.class/instance/adding elements/addPoolNamed_.st R Ring-Core-Containers.package/extension/RGFactory/instance/createNamespaceNamed_.st R Ring-Core-Containers.package/extension/RGFactory/instance/createOrganization.st R Ring-Core-Containers.package/extension/RGFactory/instance/createPackageNamed_.st M Ring-Core-Kernel.package/RGClassDefinition.class/instance/accessing/stamp_.st M Ring-Core-Kernel.package/RGClassDefinition.class/instance/behavior/withMetaclass.st M Ring-Core-Kernel.package/RGClassDefinition.class/instance/class variables/addClassVarNamed_.st M Ring-Core-Kernel.package/RGFactory.class/class/class initialization/current.st R Ring-Core-Kernel.package/RGFactory.class/class/class initialization/initialize.st M Ring-Core-Kernel.package/RGFactory.class/definition.st R Ring-Core-Kernel.package/RGFactory.class/instance/factory-variable/createClassInstanceVariableNamed_.st R Ring-Core-Kernel.package/RGFactory.class/instance/factory-variable/createClassVariableNamed_.st R Ring-Core-Kernel.package/RGFactory.class/instance/factory-variable/createClassVariableNamed_parent_.st R Ring-Core-Kernel.package/RGFactory.class/instance/factory-variable/createGlobalVariableNamed_.st R Ring-Core-Kernel.package/RGFactory.class/instance/factory-variable/createInstanceVariableNamed_.st R Ring-Core-Kernel.package/RGFactory.class/instance/factory-variable/createInstanceVariableNamed_parent_.st R Ring-Core-Kernel.package/RGFactory.class/instance/factory-variable/createPoolVariableNamed_.st R Ring-Core-Kernel.package/RGFactory.class/instance/factory-variable/createPoolVariableNamed_parent_.st R Ring-Core-Kernel.package/RGFactory.class/instance/factory-variable/createSharedPoolNamed_.st R Ring-Core-Kernel.package/RGFactory.class/instance/factory/createClassNamed_.st R Ring-Core-Kernel.package/RGFactory.class/instance/factory/createClassNamed_subclassOf_.st A Ring-Core-Kernel.package/RGFactory.class/instance/factory/createClassVariableNamed_parent_.st R Ring-Core-Kernel.package/RGFactory.class/instance/factory/createComment.st M Ring-Core-Kernel.package/RGFactory.class/instance/factory/createComment_parent_.st A Ring-Core-Kernel.package/RGFactory.class/instance/factory/createInstanceVariableNamed_parent_.st R Ring-Core-Kernel.package/RGFactory.class/instance/factory/createMetaclassOf_.st R Ring-Core-Kernel.package/RGFactory.class/instance/factory/createMetatraitOf_.st R Ring-Core-Kernel.package/RGFactory.class/instance/factory/createMethodNamed_.st M Ring-Core-Kernel.package/RGFactory.class/instance/factory/createMethodNamed_parent_.st A Ring-Core-Kernel.package/RGFactory.class/instance/factory/createPoolVariableNamed_parent_.st A Ring-Core-Kernel.package/RGFactory.class/instance/factory/createSharedPoolNamed_.st M Ring-Core-Kernel.package/RGTraitDefinition.class/instance/accessing/stamp_.st M Ring-Core-Kernel.package/RGTraitDefinition.class/instance/behavior/withMetaclass.st M Ring-Core-Kernel.package/extension/ChangeRecord/instance/createMethodDefinition.st M Ring-Core-Kernel.package/extension/CompiledMethod/instance/asActiveRingDefinition.st M Ring-Core-Kernel.package/extension/CompiledMethod/instance/asHistoricalRingDefinition.st M Ring-Core-Kernel.package/extension/CompiledMethod/instance/asPassiveRingDefinition.st M Ring-Monticello.package/extension/MCMethodDefinition/instance/asRingDefinition.st M Ring-Monticello.package/extension/MCOrganizationDefinition/instance/asRingDefinition.st M Ring-Tests-Containers.package/RGNamespaceTest.class/instance/testing/testCreatingNamespace.st M Ring-Tests-Containers.package/RGPackageTest.class/instance/testing/testAddingClass.st M Ring-Tests-Containers.package/RGPackageTest.class/instance/testing/testAddingPackage.st M Ring-Tests-Containers.package/RGPackageTest.class/instance/testing/testNewPackage.st M Ring-Tests-Containers.package/RGSliceTest.class/instance/testing/testAddingClasses.st M Ring-Tests-Kernel.package/RGClassDefinitionTest.class/instance/testing/testWithComment.st M Ring-Tests-Kernel.package/RGClassDefinitionTest.class/instance/testing/testWithSuperclass.st M Ring-Tests-Kernel.package/RGCommentDefinitionTest.class/instance/testing/testCommentWithoutAuthor.st M Ring-Tests-Kernel.package/RGCommentDefinitionTest.class/instance/testing/testNewComment.st M Ring-Tests-Kernel.package/RGGlobalDefinitionTest.class/instance/testing/testEquality.st M Ring-Tests-Kernel.package/RGGlobalDefinitionTest.class/instance/testing/testGlobalVariableDefinition.st M Ring-Tests-Kernel.package/RGGlobalDefinitionTest.class/instance/testing/testPoolDefinition.st M Ring-Tests-Kernel.package/RGMethodDefinitionTest.class/instance/testing/testExistingMethodWithoutClass.st M Ring-Tests-Kernel.package/RGMethodDefinitionTest.class/instance/testing/testExtensionMethod.st M Ring-Tests-Kernel.package/RGMethodDefinitionTest.class/instance/testing/testNonExistingMethodWithClass.st M Ring-Tests-Kernel.package/RGVariableDefinitionTest.class/instance/testing/testClassInstanceVariable.st M Ring-Tests-Kernel.package/RGVariableDefinitionTest.class/instance/testing/testClassVariable.st M Ring-Tests-Kernel.package/RGVariableDefinitionTest.class/instance/testing/testInstanceVariable.st M Ring-Tests-Kernel.package/RGVariableDefinitionTest.class/instance/testing/testPoolVariable.st M Ring-Tests-Kernel.package/RGVariableDefinitionTest.class/instance/testing/testVariableEquality.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script154.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40154.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A Spec-Inspector.package/EyeSyntaxTreeInspector.class/README.md A Spec-Inspector.package/EyeSyntaxTreeInspector.class/class/accessing/label.st A Spec-Inspector.package/EyeSyntaxTreeInspector.class/definition.st A Spec-Inspector.package/EyeSyntaxTreeInspector.class/instance/api/childrenForObject_.st A Spec-Inspector.package/EyeSyntaxTreeInspector.class/instance/api/roots.st A Spec-Inspector.package/extension/RBMethodNode/class/additionalInspectorClasses.st M Tool-ProcessBrowser.package/CPUWatcher.class/instance/process operations/debugProcess_.st M Tool-SystemReporter.package/SystemReporter.class/instance/accessing-categories/categoryMenu_.st M Tool-SystemReporter.package/SystemReporter.class/instance/accessing-report/reportMenu_.st M Tool-SystemReporter.package/SystemReporter.class/instance/private/enumerate_startAt_on_.st M Tool-SystemReporter.package/SystemReporter.class/instance/reporting/reportVM_.st M Tool-Workspace.package/Workspace.class/instance/history/setContent_.st M Tool-Workspace.package/Workspace.class/instance/window menu/addModelItemsToWindowMenu_.st Log Message: ----------- 40154 13777 remove empty package Settings-Monticello https://pharo.fogbugz.com/f/cases/13777 13780 Wrong compilation context in mustBeBooleanInMagic: https://pharo.fogbugz.com/f/cases/13780 13762 OCInstanceVariable not needed https://pharo.fogbugz.com/f/cases/13762 13788 Unused method in StringMorph https://pharo.fogbugz.com/f/cases/13788 13776 EyeSyntaxTreeInspector https://pharo.fogbugz.com/f/cases/13776 13759 Small Code critique pass over 3 tools packages https://pharo.fogbugz.com/f/cases/13759 13760 Continue remvoving RGFactory https://pharo.fogbugz.com/f/cases/13760 http://files.pharo.org/image/40/40154.zip

Aug. 7, 2014

[pharo-project/pharo-core]

by GitHub

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

Aug. 7, 2014

[pharo-project/pharo-core] 3dc976: 40153

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 3dc9768a72d80e8e5bb5cfa3346dee3879acecf5 https://github.com/pharo-project/pharo-core/commit/3dc9768a72d80e8e5bb5cfa3… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-08-07 (Thu, 07 Aug 2014) Changed paths: M Morphic-Widgets-Tree.package/MorphTreeListManager.class/instance/keyboard managing/arrowEvent_key_.st M Nautilus.package/AbstractNautilusUI.class/class/menu/debugMenu_.st M Nautilus.package/Nautilus.class/class/settings/nautilusSettingsOn_.st A Nautilus.package/Nautilus.class/class/settings/showDebugMenus.st A Nautilus.package/Nautilus.class/class/settings/showDebugMenus_.st M Nautilus.package/Nautilus.class/definition.st A Nautilus.package/PackageTreeModel.class/instance/updating/okToChange.st R NautilusCommon.package/Refactor.class/README.md R NautilusCommon.package/Refactor.class/definition.st R NautilusCommon.package/Refactor.class/instance/accessing/script.st R NautilusCommon.package/Refactor.class/instance/as yet unclassified/createAbstractMethods.st R NautilusCommon.package/Refactor.class/instance/as yet unclassified/moveDetectedMethods.st R NautilusCommon.package/Refactor.class/instance/initialization/initialize.st M OpalCompiler-Core.package/SyntaxErrorNotification.class/README.md M OpalCompiler-Core.package/SyntaxErrorNotification.class/definition.st M OpalCompiler-Core.package/SyntaxErrorNotification.class/instance/accessing/errorMessage.st M OpalCompiler-Core.package/SyntaxErrorNotification.class/instance/accessing/setClass_category_code_doitFlag_errorMessage_location_.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script153.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40153.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st R Slot.package/LiteralVariable.class/instance/as yet unclassified/asWrapperFor_.st A Slot.package/LiteralVariable.class/instance/wrapping/asWrapperFor_.st A Slot.package/WorkspaceVariable.class/README.md A Slot.package/WorkspaceVariable.class/definition.st A Slot.package/WorkspaceVariable.class/instance/code generation/emitStore_.st A Slot.package/WorkspaceVariable.class/instance/code generation/emitValue_.st M Tool-Workspace.package/Workspace.class/instance/binding/bindingOf_.st Log Message: ----------- 40153 13763 SyntaxErrorNotification: errorMessage ivar not needed https://pharo.fogbugz.com/f/cases/13763 13782 add preference the DEBUG menu entires of Nautilus https://pharo.fogbugz.com/f/cases/13782 13767 packagetree changes visible selection even if okToChange is false https://pharo.fogbugz.com/f/cases/13767 13778 Workspace: fix non-declared temp vars https://pharo.fogbugz.com/f/cases/13778 13781 class Refactor not needed https://pharo.fogbugz.com/f/cases/13781 http://files.pharo.org/image/40/40153.zip

Aug. 7, 2014

Re: [Pharo-dev] xml-oo mapper?

by Tudor Girba

Hi, Thanks. I guess it is probably what I need. I will look at it more closely. I want to be able to map an XML structure on objects and support read/write at the object level. Cheers, Doru On Wed, Aug 6, 2014 at 11:28 AM, Norbert Hartl <norbert(a)hartl.name> wrote: > There is Magritte-XML. Or do you mean something different? It is in > Magritte3Addons on smallttalkhub > > Norbert > > > Am 06.08.2014 um 09:29 schrieb Tudor Girba <tudor(a)tudorgirba.com>: > > Hi, > > Does anyone know if there exists an XO mapper available in the Pharo? > > Cheers, > Doru > > -- > www.tudorgirba.com > > "Every thing has its own flow" > > > -- www.tudorgirba.com "Every thing has its own flow"

Aug. 7, 2014

New CogVMs available

by Eliot Miranda

...at http://www.mirandabanda.org/files/Cog/VM/VM.r3060/. CogVM binaries as per VMMaker.oscog-eem.844/r3060 Fix bad bug in interpreter to machine code frame conversion on backward branch. Old code would decrement branch even if backward branch checked for events and did a process switch, potentially converting frames at arbitrary unmappable pcs, not just backward branches. Neaten and comment the code. Neaten and update the pc mapping tests for multiple bytecode sets and for sets with extensions. Change default count to 40 from 10 to reduce number of startup methods jitted. Allow warnings to be treated as errors, adding -blockonwarn flag on Mac & Unix. -- best, Eliot

Aug. 7, 2014

Re: [Pharo-dev] No projects on StHub?

by Alexandre Bergel

I did not known neither. I will have a serious look at GitHub. Alexandre > Le 05-08-2014 Ã 11:13, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> a Ã©crit : > > Wow, I didnât know that. Nice > > >> On 05 Aug 2014, at 17:01, Dale Henrichs <dale.henrichs(a)gemtalksystems.com> wrote: >> >> >> KIlon, >> >> If you use a a github reference in your configuration: >> >> github://username/projectname:commitish/repositoryDir >> >> Git is not required. Metacello will download a zipped version of the commitish referenced (a commitish is a branch name, SHA or tag name) and a read only filetree repository is created .... >> >> So folks should be able to use your project without installing git on their machine. >> >> Dale >> >> >>> On Mon, Aug 4, 2014 at 2:17 AM, kilon alios <kilon.alios(a)gmail.com> wrote: >>> yeah I will also move my latest project to github. I am already more active with github than I am in SThub anyway. The one thing that stopped me so far is that I don't want to force people to install git to get the latest version of my project. SThub is great for this. >>> >>> >>>> On Mon, Aug 4, 2014 at 12:03 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: >>>> Well, thankfully I keep all my latest projects on github, and I have configurations of them in the image. But CI is not working and anyway itâs a strange situation. Is there any other service where I can keep my configurations? Because thatâs the only thing I version with monticello are configurations as I want to use gofer to load my projects. And here reliability is much more important then other features. >>>> >>>> Uko >>>> >>>> >>>>> On 04 Aug 2014, at 10:59, kilon alios <kilon.alios(a)gmail.com> wrote: >>>>> >>>>> oh boy thats looks nasty bug, hope its not permanent. >>>>> >>>>> >>>>>> On Mon, Aug 4, 2014 at 11:44 AM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: >>>>>> Hi, >>>>>> >>>>>> I was on vacation last weak, have I missed anything? Because my SmaltalkHub user does not have any projects http://smalltalkhub.com/#!/~YuriyTymchuk (and I had a bunch of them). >>>>>> >>>>>> Uko >

Aug. 6, 2014

Re: [Pharo-dev] [Moose-dev] [Solved] Pharo image corruption and fatal VM error with Roassal

by Nicolai Hess

In the solution I posted on the list, only TRCanvas holds the session and if it changes all attached Shapes resets its path. 2014-08-06 21:43 GMT+02:00 Alexandre Bergel <alexandre.bergel(a)me.com>: > Thanks Vincent! > It seems to work well. > > Included in Roassal! > > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > On Aug 6, 2014, at 12:29 PM, Blondeau Vincent < > vincent.blondeau(a)worldline.com> wrote: > > Solved ! > > You will found the changes in the attached .mcz. > > I added some sessions guards where some Athens external objects are used. > Stef you were right ;) > Particularly for checking the IV TRCanvas>>canvas and on TRShape>>path > that relies on Athens external objects. > > It seems to works for me. If it is the case for you, it we be nice to > integrate it quickly to be able to work fine :) > > Thanks > > Vincent > > -----Message d'origine----- > De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org > <pharo-dev-bounces(a)lists.pharo.org>] De la part de stepharo > EnvoyÃ© : jeudi 31 juillet 2014 22:58 > Ã : Pharo Development List > Objet : Re: [Pharo-dev] [Moose-dev] Pharo image corruption and fatal VM > error with Roassal > > Alexandre > > may be you should try to understand what is a session. > Because this is about 2 lines of code. > > When you open an image you save 2 min ago or 2 years ago, how the system > knows that an OS ressources is valid? > By checking the session id... > > Stef > > On 31/7/14 16:09, Alexandre Bergel wrote: > > Yes, and this is a mess. > I've spent quite some time in getting the session working with Roassal2 > and it still does not work. I would appreciate help on this. > > Alexandre > > > On Jul 31, 2014, at 8:58 AM, Nicolai Hess <nicolaihess(a)web.de> wrote: > > It looks like Trachel does not recreate athens external resources. > There is an example in AthensSceneView, on how to check and reload an > AthensSurface. > > > 2014-07-31 12:51 GMT+02:00 Usman Bhatti <usman.bhatti(a)gmail.com>: > > > > On Thu, Jul 31, 2014 at 11:17 AM, Blondeau Vincent < > vincent.blondeau(a)worldline.com> wrote: > Yes it is. But I will not do > > TRMorph allInstances do: #delete > > In command line every day... > > > It is only intended to recover your lost work in the image not for > everyday use :). > > > > > Vincent > > > > De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org > <pharo-dev-bounces(a)lists.pharo.org>] De la part > de Usman Bhatti EnvoyÃ© : jeudi 31 juillet 2014 10:59 Ã : Pharo > Development List Cc : Moose-related development > > > Objet : Re: [Pharo-dev] Pharo image corruption and fatal VM error > with Roassal > > > > This may be related to this known issue reported a few days back. > > https://code.google.com/p/moose-technology/issues/detail?id=1084 > > > > And there is a possible solution to recover your image. > > > > usman > > > > On Thu, Jul 31, 2014 at 10:50 AM, Blondeau Vincent < > vincent.blondeau(a)worldline.com> wrote: > > Hi, > > > > Yesterday, I was using GraphET (a part of Roassal) to do some charts and, > today, when I wanted to reopen the image. > > And I got that : > > <image001.png> > > It is *very* unpleasant... > > > > To reproduce the bug: > > 1 - You can do either: > > | builder | > > builder := GET2Line data: (0 to: 100) . > > builder > > y: [ :x | x*x ]. > > > > builder open. > > Or > > WorldMenu -> Roassal examples -> choose an item -> click on a graph . A > TRMorph should be opened. > > 2 - don't close the graph and save the pharo image. > > 3 - Close the pharo image > > 4 - Reopen it > > > > I am under W7 x64 with the latest moose image and the VM available on the > pharo.org website (http://files.pharo.org/platform/Pharo3.0-win.zip) from > the 10 july. > > You will find the crash dump attached. > > > > > > Thankfully, I managed to open the image with a latest VM ( > http://www.mirandabanda.org/files/Cog/VM/VM.r3056/cogwin-14.29.3056.zip) > > Thanks a lot Eliot ! :) > > > > And I got this: > > <image002.png> > > > > Thanks in advance > > > > Cheers, > > Vincent BLONDEAU > > > > > > > Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage > exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret > professionnel. Si vous recevez ce message par erreur, merci d'en avertir > immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne > pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra > Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs > efforts soient faits pour maintenir cette transmission exempte de tout > virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa > responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un > virus transmis. > > This e-mail and the documents attached are confidential and intended > solely for the addressee; it may also be privileged. If you receive this > e-mail in error, please notify the sender immediately and destroy it. As > its integrity cannot be secured on the Internet, the Worldline liability > cannot be triggered for the message content. Although the sender endeavours > to maintain a computer virus-free network, the sender does not warrant that > this transmission is virus-free and will not be liable for any damages > resulting from any virus transmitted. > > > > > > Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage > exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret > professionnel. Si vous recevez ce message par erreur, merci d'en avertir > immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne > pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra > Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs > efforts soient faits pour maintenir cette transmission exempte de tout > virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa > responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un > virus transmis. > > This e-mail and the documents attached are confidential and intended > solely for the addressee; it may also be privileged. If you receive this > e-mail in error, please notify the sender immediately and destroy it. As > its integrity cannot be secured on the Internet, the Worldline liability > cannot be triggered for the message content. Although the sender endeavours > to maintain a computer virus-free network, the sender does not warrant that > this transmission is virus-free and will not be liable for any damages > resulting from any virus transmitted. > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > > > > Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage > exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret > professionnel. Si vous recevez ce message par erreur, merci d'en avertir > immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne > pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra > Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs > efforts soient faits pour maintenir cette transmission exempte de tout > virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa > responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un > virus transmis. > > This e-mail and the documents attached are confidential and intended > solely for the addressee; it may also be privileged. If you receive this > e-mail in error, please notify the sender immediately and destroy it. As > its integrity cannot be secured on the Internet, the Worldline liability > cannot be triggered for the message content. Although the sender endeavours > to maintain a computer virus-free network, the sender does not warrant that > this transmission is virus-free and will not be liable for any damages > resulting from any virus transmitted. > <Trachel-VincentBlondeau.180.mcz> > _______________________________________________ > > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > >

Aug. 6, 2014