- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Refactoring HelpTopic (needs review)

by stepharo

I will! I love to read nice comments Stef Le 28/7/16 Ã 00:38, Nicolai Hess a Ã©crit : > Hi, > > I recently added some class comments to the Refactoring-Package. > (RBBrowserEnvironments, RBRefactoring, RBNamespace). > > Now I added some more HelpTopics describing the refactoring framework, > some background information, RBPatternParser and Metavariables, some > examples and put the existing class comments into the HelpBook. > > see fogbugz issue 18829 > <https://pharo.fogbugz.com/f/cases/18829/Add-a-RefactoringFramework-System-H…> > Add a RefactoringFramework System HelpTopic > you can load the slice and open the HelpBook with > > HelpBrowser openOn: RefactoringHelp. > > Would be nice if someone can help with proofreading and of course, amy > feedback is welcome. > > nicolai

July 28, 2016

Re: [Pharo-dev] Pharo 5.0 Tiny Feature Request

by Sean P. DeNigris

Sean P. DeNigris wrote > Bump :) > [waiting patiently while all my build scripts are broken in Pharo 5.0] So close! Marked "Fix to include". Who can integrate it?! ----- Cheers, Sean -- View this message in context: http://forum.world.st/Pharo-5-0-Tiny-Feature-Request-tp4901682p4908459.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

July 28, 2016

Re: [Pharo-dev] Accept in Debugger Meltdown in Pharo 5.0

by Sean P. DeNigris

Tudor Girba-2 wrote > So, could you describe what you did in more details? I think it had to do with the combination of [messing with Magritte internals] + [Magritte GT integration]. I'll keep you posted if I find out more. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Accept-in-Debugger-Meltdown-in-Pharo-5-0-tp4908072p49… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

July 28, 2016

[pharo-project/pharo-core]

by GitHub

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

July 28, 2016

[pharo-project/pharo-core] c43e93: 60158

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: c43e937bd8228a14da811cd0a755ff7bde735fc0 https://github.com/pharo-project/pharo-core/commit/c43e937bd8228a14da811cd0… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-07-28 (Thu, 28 Jul 2016) Changed paths: M AST-Core.package/RBPatternParser.class/instance/private-parsing/parsePatternBlock_.st M AST-Core.package/RBPatternParser.class/instance/private-parsing/parseUnaryMessage.st A AST-Core.package/RBPatternParser.class/instance/private-parsing/parseWrapperPatternBlockWith_.st M Kernel-Tests.package/ClassTest.class/instance/testing - navigation/testMethodsReferencingClass.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60157.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60158.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60157.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60158.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Spec-MorphicAdapters.package/MorphicTreeAdapter.class/instance/drag and drop - private/acceptDroppingMorph_event_inMorph_.st M Spec-Tests.package/TabManagerModelTest.class/README.md M Spec-Tests.package/TabManagerModelTest.class/definition.st A Spec-Tests.package/TabManagerModelTest.class/instance/running/classToTest.st M Spec-Tests.package/TabManagerModelTest.class/instance/running/setUp.st R Spec-Tests.package/TabManagerModelTest.class/instance/running/tearDown.st M Spec-Tests.package/TabManagerModelTest.class/instance/tabs creation/redMorphTab.st M Spec-Tests.package/TabManagerModelTest.class/instance/tests/testAddTabOpened.st M Spec-Tests.package/TabManagerModelTest.class/instance/tests/testAddTabSetOwner.st M Spec-Tests.package/TabManagerModelTest.class/instance/tests/testAddTabUnopened.st M Spec-Tests.package/TabManagerModelTest.class/instance/tests/testInitialSelectedTab.st M Spec-Tests.package/TabManagerModelTest.class/instance/tests/testRemoveTab.st M Spec-Tests.package/TabManagerModelTest.class/instance/tests/testRemoveTabFromManager.st M Spec-Tests.package/TabManagerModelTest.class/instance/tests/testRemoveTabFromManager2.st M Spec-Tests.package/TabManagerModelTest.class/instance/tests/testRemoveTabFromMorphic.st M Spec-Tests.package/TabManagerModelTest.class/instance/tests/testRemoveTabUnsetOwner.st M Spec-Tests.package/TabModelTest.class/README.md M Spec-Tests.package/TabModelTest.class/definition.st M Spec-Tests.package/TabModelTest.class/instance/instance creation/redMorphTab.st A Spec-Tests.package/TabModelTest.class/instance/running/classToTest.st M Spec-Tests.package/TabModelTest.class/instance/running/setUp.st R Spec-Tests.package/TabModelTest.class/instance/running/tearDown.st M Spec-Tests.package/TabModelTest.class/instance/tests/testChangeLabel.st M Spec-Tests.package/TabModelTest.class/instance/tests/testSetOwner.st Log Message: ----------- 60158 18766 Change TabModelTest and TabManagerTest to use the abstract class https://pharo.fogbugz.com/f/cases/18766 18833 Error on TreeModels drag&drop https://pharo.fogbugz.com/f/cases/18833 18830 RBPatternParser should respect RBErrorNode when parsing pattern blocks https://pharo.fogbugz.com/f/cases/18830 18826 failing tests testMethodsReferencingClass on bootstrapped image https://pharo.fogbugz.com/f/cases/18826 http://files.pharo.org/image/60/60158.zip

July 28, 2016

Refactoring HelpTopic (needs review)

by Nicolai Hess

Hi, I recently added some class comments to the Refactoring-Package. (RBBrowserEnvironments, RBRefactoring, RBNamespace). Now I added some more HelpTopics describing the refactoring framework, some background information, RBPatternParser and Metavariables, some examples and put the existing class comments into the HelpBook. see fogbugz issue 18829 <https://pharo.fogbugz.com/f/cases/18829/Add-a-RefactoringFramework-System-H…> Add a RefactoringFramework System HelpTopic you can load the slice and open the HelpBook with HelpBrowser openOn: RefactoringHelp. Would be nice if someone can help with proofreading and of course, amy feedback is welcome. nicolai

July 27, 2016

Re: [Pharo-dev] Customizing semantic analysis for AST nodes

by Nicolai Hess

2016-07-27 15:16 GMT+02:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com>: > Hi, I have two questions about semantic analysis. > > Iâm working with expressions a lot now. And I want to highlight them, but > I donât want to pay attention for undeclared variables. So in terms of > analysis it would be nice to know global variables, but I donât care about > having marked others as undeclared. > > Second thing is more of a disturbing functionality. If you have `ast` > variable which is an RBPatternVariableNode and you do `ast > doSemanticAnalysis` after that ast may end up being a RBVariableNode. I > find this annoying because I donât expect my object to change just because > of an analysis. > But it is the same that happens with any global variable. After parsing an expression like RBPatternParser parseExpression:'Morph draw:`arg' Morph is just a RBVariableNode and you need to call #doSemanticAnalysis to get a RBGlobalNode instead. But I guess #doSemanticAnalysis is just not supposed to work with pattern nodes. > > Uko >

July 27, 2016

Customizing semantic analysis for AST nodes

by Yuriy Tymchuk

Hi, I have two questions about semantic analysis. Iâm working with expressions a lot now. And I want to highlight them, but I donât want to pay attention for undeclared variables. So in terms of analysis it would be nice to know global variables, but I donât care about having marked others as undeclared. Second thing is more of a disturbing functionality. If you have `ast` variable which is an RBPatternVariableNode and you do `ast doSemanticAnalysis` after that ast may end up being a RBVariableNode. I find this annoying because I donât expect my object to change just because of an analysis. Uko

July 27, 2016

Re: [Pharo-dev] Accept in Debugger Meltdown in Pharo 5.0

by Dale Henrichs

Doru, I think my "empty debugger problem"[1] is related ... of course I haven't seen the problem again and after trashing 3 or 4 rebuilds, I was able to code my way out of the problem and haven't seen it since .... Dale [1] http://forum.world.st/Empty-debugger-Pharo-5-0-td4907374.html On 7/27/16 1:20 AM, Tudor Girba wrote: > That is not good. Did it happen repeatedly, or only once? Do you remember the situation? > > Cheers, > Doru > > >> On Jul 27, 2016, at 8:49 AM, stepharo <stepharo(a)free.fr> wrote: >> >> I know that christophe and me got it too. >> >> Stef >> >> >> Le 26/7/16 Ã 19:00, Sean P. DeNigris a Ã©crit : >>> <http://forum.world.st/file/n4908072/Screenshot_2016-07-26_13.png> >>> >>> Mac spinning beachball of death followed after about a minute by "... quit >>> unexpectedly". Bugforeveryoneorjustme? >>> >>> >>> >>> ----- >>> Cheers, >>> Sean >>> -- >>> View this message in context: http://forum.world.st/Accept-in-Debugger-Meltdown-in-Pharo-5-0-tp4908072.ht… >>> Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >>> >>> >> > -- > www.tudorgirba.com > www.feenk.com > > "Presenting is storytelling." > >

July 27, 2016

Re: [Pharo-dev] Option for as-in-moose debugger layout

by Denis Kudriashov

I want it too (but I never try it). And maybe it is good time to force people taste it as default? (with setting to return classic one) 2016-07-27 9:08 GMT+02:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com>: > Hi, > > is it possible to have some setting to switch the debugger into the layout > that is used in Moose? I.e. have the stack vertically on the left. > > Because come on, look at this image: > > only 3 lines of variables? And you see all that empty space on the right > both in source code and variables pane? > > Cheers. > Uko >

July 27, 2016