- Pharo-dev - lists.pharo.org

Parsing expressions and Opal
by Gisela Decuzzi Nov. 9, 2013

Nov. 9, 2013

Hello, we were working on the issue 10983 plus smart suggestion, specially for a class definition. In a moment I need to parse a class definition, I treat as the normal case: root := OpalCompiler new source: context code; useFaultyForParsing: true; parse. And as a result we obtain a Method Node, browsing the code we saw that Opal can parse code as an expresion, but instead it is treating the code as method because of: "self compilationContext noPattern" is false, when we changed the boolean to true we obtain a return node for the class definition and everything got messy. Can someone help us to use Opal in the right way?

3 3

Scroll bug since ever. Someone?
by Mariano Martinez Peck Nov. 9, 2013

Nov. 9, 2013

Hi guys. We have a bug with the scrolling since I can remember.... You know...when you scroll down fast, at some point it restarts the scroll in a higher position, making it impossible to really scroll down. If you scroll down slower, it works. I guess I am not the only one seeing this problem right? Tomorrow we have a sprint here in Argentina. Would I be loosing my hours trying to find this bug? Because as said, I think it's been here since ever.... Any point? Thanks, -- Mariano http://marianopeck.wordpress.com

4 3

Support understanding changes
by StÃ©phane Ducasse Nov. 9, 2013

Nov. 9, 2013

Now that we have epicea I would really love to have a tool that does not show me stupidly a diff but take into account the actions that have been performed like rename class, splitâ¦. Side questions: camillo and other giter, I was thinking that it would make sense to publish on git metadata (may be in ston) representing the semantics of the operation that led to the changes) so that tools can take advantage of this information to present semantical operation instead of plain stupid diff. For example split this method, rename class,â¦. Stef

4 12

NBOpenGL VM crash.
by Ronie Salgado Nov. 9, 2013

Nov. 9, 2013

I'm trying to use the latest version of NBOpenGL in Windows in Pharo 3.0. First I'm receiving a "Not suitable implementation" error message. This can be solved by adding the following at the class side of NBWin32GLContextDriver. NBWin32GLContextDriver>>supportsCurrentPlatform ^ NativeBoost platformId = NativeBoostConstants win32PlatformId Then, trying the following Roassal3D example produces a VM crash: R3Example new city Attached is the crash.dmp file. Currently, we are using an old pharo image for developing Roassal3D under windows. Greetings, Ronie Salgado

3 3

[pharo-project/pharo-core]
by GitHub Nov. 8, 2013

Nov. 8, 2013

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

1 0

[pharo-project/pharo-core] af944b: 30559
by GitHub Nov. 8, 2013

Nov. 8, 2013

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: af944bcc0a7c3bacfb8e29a1e412ccdbb1fcc82f https://github.com/pharo-project/pharo-core/commit/af944bcc0a7c3bacfb8e29a1… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2013-11-08 (Fri, 08 Nov 2013) Changed paths: M Collections-Unordered.package/Dictionary.class/instance/enumerating/valuesDo_.st A Files.package/SourceFileArray.class/instance/private/sourceDataPointers.st A Files.package/SourceFileArray.class/instance/source code management/protocolAt_.st A Files.package/SourceFileArray.class/instance/source code management/protocolAt_for_.st A Files.package/SourceFileArray.class/instance/source code management/sourceCodeAt_.st A Files.package/SourceFileArray.class/instance/source code management/sourcedDataAt_.st A Files.package/SourceFileArray.class/instance/source code management/timeStampAt_.st A Files.package/SourceFileArray.class/instance/source code management/timeStampAt_for_.st M NewList.package/NewList.class/instance/accessing/allowToSelect.st A NewList.package/NewList.class/instance/drag and drop/transferFor_from_.st A NewList.package/NewListAdapter.class/instance/drag and drop/transferFor_from_.st M NewList.package/NewListRenderer.class/instance/drag and drop/startDrag_.st M Polymorph-Widgets.package/PluggableTreeMorph.class/instance/morphic/startDrag_.st R Ring-Core-Kernel.package/extension/SourceFileArray/instance/protocolAt_.st R Ring-Core-Kernel.package/extension/SourceFileArray/instance/protocolAt_for_.st R Ring-Core-Kernel.package/extension/SourceFileArray/instance/sourceCodeAt_.st R Ring-Core-Kernel.package/extension/SourceFileArray/instance/sourceDataPointers.st R Ring-Core-Kernel.package/extension/SourceFileArray/instance/sourcedDataAt_.st R Ring-Core-Kernel.package/extension/SourceFileArray/instance/timeStampAt_.st R Ring-Core-Kernel.package/extension/SourceFileArray/instance/timeStampAt_for_.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script215.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30559.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Tools.package/FileList.class/instance/drag%27n%27drop/wantsDroppedMorph_event_inMorph_.st Log Message: ----------- 30559 12117 Fix NewList >> #allowToSelect to use new ValueHolder API https://pharo.fogbugz.com/f/cases/12117 12048 Incorporate Ring extension methods in SourceFileArray https://pharo.fogbugz.com/f/cases/12048 12104 Optimize Dictionary>>valuesDo:, part 2 https://pharo.fogbugz.com/f/cases/12104 12072 Get rid of last hardcoded references to TransferMorph https://pharo.fogbugz.com/f/cases/12072 http://files.pharo.org/image/30/30559.zip

1 0

Pharo3 Theme not really active in CI built images
by Torsten Bergmann Nov. 8, 2013

Nov. 8, 2013

When I download a fresh Pharo3.0 Latest update: #30558 from CI the menues look awfull (dark gray) since I think the theme is not correctly initialized. Switching the theme or evaluating Pharo3Theme beCurrent fixes this easily. So there is no method to change, just some code to run. So I dont think this can be fixed with a metacello slice. How can we run the above "do it" to correct the images? Thx T.

2 1

[pharo-project/pharo-core] a400d2: 30558
by GitHub Nov. 8, 2013

Nov. 8, 2013

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: a400d2cd03f9c62dfa2406497ef0acaa48b19973 https://github.com/pharo-project/pharo-core/commit/a400d2cd03f9c62dfa240649… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2013-11-08 (Fri, 08 Nov 2013) Changed paths: A Collections-Weak.package/WeakIdentityKeyDictionary.class/instance/enumeration/valuesDo_.st A Collections-Weak.package/WeakKeyDictionary.class/instance/enumerating/valuesDo_.st A Collections-Weak.package/WeakValueDictionary.class/instance/enumerating/valuesDo_.st M Monticello.package/extension/Class/instance/asClassDefinition.st M MonticelloGUI.package/extension/PseudoClass/instance/asClassDefinition.st M NautilusRefactoring.package/RBClassRegexRefactoring.class/instance/private/copyFrom_to_.st R Refactoring-Changes.package/RBAddClassChange.class/instance/accessing/poolDictionaryNames.st A Refactoring-Changes.package/RBAddClassChange.class/instance/accessing/sharedPoolNames.st M Refactoring-Core.package/RBChildrenToSiblingsRefactoring.class/instance/private-variables/pullUpPoolVariables.st M Refactoring-Core.package/RBClass.class/instance/accessing/allPoolDictionaryNames.st M Refactoring-Core.package/RBClass.class/instance/accessing/definitionString.st R Refactoring-Core.package/RBClass.class/instance/accessing/poolDictionaryNames.st A Refactoring-Core.package/RBClass.class/instance/accessing/sharedPoolNames.st M Refactoring-Core.package/RBClass.class/instance/testing/directlyDefinesPoolDictionary_.st M Refactoring-Core.package/RBNamespace.class/instance/changes/defineClass_.st M Refactoring-Critics.package/RBClassVariableCapitalizationRule.class/instance/running/checkClass_.st M Refactoring-Tests-Changes.package/RBRefactoringChangeTests.class/instance/tests-pattern/testAddClassPattern.st M Refactoring-Tests-Changes.package/RBRefactoringChangeTests.class/instance/tests/testAddClassInteractively.st M Ring-Core-Kernel.package/extension/Class/instance/asRingDefinition.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script214.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30558.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M System-Announcements.package/ClassCommented.class/instance/accessing/oldComment.st R Traits.package/TBehavior.class/instance/accessing/poolDictionaryNames.st A Traits.package/TBehavior.class/instance/accessing/sharedPoolNames.st Log Message: ----------- 30558 12102 Optimize Dictionary>>valuesDo:, part 1 https://pharo.fogbugz.com/f/cases/12102 12112 Missing ^ in accessor method in ClassCommented https://pharo.fogbugz.com/f/cases/12112 12099 Rename #poolDictionaryNames to #sharedPoolNames https://pharo.fogbugz.com/f/cases/12099 http://files.pharo.org/image/30/30558.zip

1 0

[pharo-project/pharo-core]
by GitHub Nov. 8, 2013

Nov. 8, 2013

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

1 0

Opal, Pharo 3.0 and popup raising for none existing methods
by Mariano Martinez Peck Nov. 8, 2013

Nov. 8, 2013

Hi guys, In Pharo 2.0 we have the setting #warningAllowed in Parser. This allow us to disable the popups each time you save a method with a selector that doesn't exist. In Pharo 3.0 with the new Opal this setting doesn't exist anymore. Is there a way to get this behavior??? Thanks, -- Mariano http://marianopeck.wordpress.com

2 2