- Pharo-dev - lists.pharo.org

[ANN] MatchTool

by Yuriy Tymchuk

Hi everyone! Iâm happy to announce a new tool that can help you to understand to the pattern code is working in match & rewrite rules. You can read more on my blogpost: http://blog.yuriy.tymch.uk/2016/08/matchtool.html The tool is available for Pharo 6 from the catalog. Cheers! Uko

Aug. 4, 2016

[pharo-project/pharo-core]

by GitHub

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

Aug. 4, 2016

[pharo-project/pharo-core] 31f30e: 60168

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 31f30e5e8f01ec9696c792611dcd51f4d93b84b0 https://github.com/pharo-project/pharo-core/commit/31f30e5e8f01ec9696c79261… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-08-04 (Thu, 04 Aug 2016) Changed paths: A ConfigurationOfEpicea.package/ConfigurationOfEpicea.class/instance/tags/stable_.st R ConfigurationOfEpicea.package/ConfigurationOfEpicea.class/instance/versions/stable_.st A ConfigurationOfEpicea.package/ConfigurationOfEpicea.class/instance/versions/version798_.st A EpiceaBrowsers.package/EpLostChangesDetector.class/class/accessing/enabled_.st M EpiceaBrowsers.package/EpLostChangesDetector.class/class/startup - shutdown/startUp_.st A EpiceaBrowsers.package/EpLostChangesDetector.class/class/testing/isEnabled.st A EpiceaBrowsers.package/EpSettings.class/class/accessing/lostEventsDetectorEnabled.st A EpiceaBrowsers.package/EpSettings.class/class/accessing/lostEventsDetectorEnabledSettingOn_.st A EpiceaBrowsers.package/EpSettings.class/class/accessing/lostEventsDetectorEnabled_.st M EpiceaBrowsers.package/EpSettings.class/class/system settings/enabledSettingOn_.st M EpiceaBrowsers.package/EpSettings.class/class/system settings/groupSettingsOn_.st M Nautilus.package/AbstractNautilusUI.class/instance/system announcements/classDefinitionModified_.st M Ombu.package/OmFileStore.class/definition.st M Ring-Core-Kernel.package/RGMethodDefinition.class/instance/accessing/ast.st M Ring-Core-Kernel.package/RGMethodDefinition.class/instance/backward compatibility/messages.st A Ring-Core-Kernel.package/RGMethodDefinition.class/instance/private/astFromSource.st M Ring-Core-Kernel.package/RGMethodDefinition.class/instance/testing/isAbstract.st M Ring-Core-Kernel.package/RGMethodDefinition.class/instance/testing/isOverridden.st M Ring-Core-Kernel.package/RGMethodDefinition.class/instance/traits/argumentNames.st R Ring-Tests-Kernel.package/RGMethodDefinitionTest.class/instance/as yet unclassified/foo.st A Ring-Tests-Kernel.package/RGMethodDefinitionTest.class/instance/running/runCase.st A Ring-Tests-Kernel.package/RGMethodDefinitionTest.class/instance/running/tearDown.st A Ring-Tests-Kernel.package/RGMethodDefinitionTest.class/instance/test - accessing source/testASTExistingMethod.st A Ring-Tests-Kernel.package/RGMethodDefinitionTest.class/instance/test - accessing source/testASTNonExistingMethodWithNoSource.st A Ring-Tests-Kernel.package/RGMethodDefinitionTest.class/instance/test - accessing source/testASTNonExistingMethodWithSource.st A Ring-Tests-Kernel.package/RGMethodDefinitionTest.class/instance/test - accessing source/testArgumentNamesExistingMethod.st A Ring-Tests-Kernel.package/RGMethodDefinitionTest.class/instance/test - accessing source/testArgumentNamesNonExistingMethodWithNoSource.st A Ring-Tests-Kernel.package/RGMethodDefinitionTest.class/instance/test - accessing source/testArgumentNamesNonExistingMethodWithSource.st A Ring-Tests-Kernel.package/RGMethodDefinitionTest.class/instance/test - accessing source/testIsAbstractExistingMethod.st A Ring-Tests-Kernel.package/RGMethodDefinitionTest.class/instance/test - accessing source/testIsAbstractNonExistingMethod.st A Ring-Tests-Kernel.package/RGMethodDefinitionTest.class/instance/test - accessing source/testMessagesExistingMethod.st A Ring-Tests-Kernel.package/RGMethodDefinitionTest.class/instance/test - accessing source/testMessagesNonExistingMethodWithNoSource.st A Ring-Tests-Kernel.package/RGMethodDefinitionTest.class/instance/test - accessing source/testMessagesNonExistingMethodWithSource.st M Ring-Tests-Kernel.package/RGMethodDefinitionTest.class/instance/testing/testAsActive.st M Ring-Tests-Kernel.package/RGMethodDefinitionTest.class/instance/testing/testAsHistorical.st M Ring-Tests-Kernel.package/RGMethodDefinitionTest.class/instance/testing/testAsPassive.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60167.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60168.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60167.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60168.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60168 18856 After Epicea integration: "an OmReference(Pharo_2elhj7i:199) not found in OmSessionStore" https://pharo.fogbugz.com/f/cases/18856 17710 rename variable do not update class template https://pharo.fogbugz.com/f/cases/17710 18855 reduce calls on #compiledMethod in RGMethodDefinition https://pharo.fogbugz.com/f/cases/18855 18860 cleanup after running RGMethodDefintionTest https://pharo.fogbugz.com/f/cases/18860 http://files.pharo.org/image/60/60168.zip

Aug. 4, 2016

Re: [Pharo-dev] Stable configuration of PetitParser broken for stable PetitGui in Pharo 5

by Tudor Girba

Hi, Thanks for the report. PetitParser was not yet released for Pharo 5. It comes in the following days as part of the Moose release. Cheers, Doru > On Aug 4, 2016, at 7:18 AM, Martin McClure <martin(a)hand2mouse.com> wrote: > > Loading PetitGui with this expression: > > --- > Metacello new > configuration: 'PetitParser'; > version: #'stable'; > repository: 'http://smalltalkhub.com/mc/Moose/PetitParser/main/'; > load: 'PetitGui'. > --- > > loads, but any attempt to use the PetitParser GUI tool results in deprecation exceptions like this: > > --- > The method GLMCompositePresentation>>smalltalkCode has been deprecated. > Use #pharoMethod (if you need to display a method) > or #pharoScript (if you need to display snippets of code that do not belong to a method) > --- > > It looks like this problem may have been fixed in PetitGui-AndreiChis.156, but the stable configuration loads the earlier PetitGui-StefanReichhart.150. > > Perhaps the stable configuration needs to be updated for Pharo 5? It looks like the latest version of the configuration is still using the same version for Pharo 4 and Pharo 5. > > Regards, > > -Martin > > -- www.tudorgirba.com www.feenk.com "What we can governs what we wish."

Aug. 4, 2016

Stable configuration of PetitParser broken for stable PetitGui in Pharo 5

by Martin McClure

Loading PetitGui with this expression: --- Metacello new configuration: 'PetitParser'; version: #'stable'; repository: 'http://smalltalkhub.com/mc/Moose/PetitParser/main/'; load: 'PetitGui'. --- loads, but any attempt to use the PetitParser GUI tool results in deprecation exceptions like this: --- The method GLMCompositePresentation>>smalltalkCode has been deprecated. Use #pharoMethod (if you need to display a method) or #pharoScript (if you need to display snippets of code that do not belong to a method) --- It looks like this problem may have been fixed in PetitGui-AndreiChis.156, but the stable configuration loads the earlier PetitGui-StefanReichhart.150. Perhaps the stable configuration needs to be updated for Pharo 5? It looks like the latest version of the configuration is still using the same version for Pharo 4 and Pharo 5. Regards, -Martin

Aug. 4, 2016

Re: [Pharo-dev] [pharo-project/pharo-core] f57843: 60163

by Ben Coman

Thanks for the follow up post of this change log Marcus. cheers -ben On Wed, Aug 3, 2016 at 5:23 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > >> On 03 Aug 2016, at 11:07, GitHub <noreply(a)github.com> wrote: >> >> >> Log Message: >> ----------- >> 60163 >> 18831 Integrate new Epicea version >> https://pharo.fogbugz.com/f/cases/18831 >> > ChangeLog for this: > > - Case 18813: Implement redo and undo of protocol addition and removal. > > - Case 18612: disable drag&drop until TreeModel supports it correctly. > > - Case 18384: Redo and undo: show on any selection (not only when all selected entries are code changes). > > - Enhancement: Improve lost changes detection; show only the events actually lost. > > - Enhancement: Pass on filters. > > - Clean up: Do not show the "absent entry" item anymore since it was not useful at all. > > - Clean up: Remove unused "commit tags" in log browser. > > - Clean up: Remove unused tests. They were good idea, we can re-introduce them but working and covering more cases. > > - Clean up: Rename #displayWidget to #asMorph in EpLogBrowserItem''s hierarchy. It is more meaningful. > > - Workaround: Hide "Open in Sorter" menu action since it is useless until Treemodel drag&drop is fixed. > > > >> 18768 Inlined method const could be implemented by metalinks >> https://pharo.fogbugz.com/f/cases/18768 >> >> 18835 Update RBParser-Nodes class comments >> https://pharo.fogbugz.com/f/cases/18835 >> >> http://files.pharo.org/image/60/60163.zip >> >> > >

Aug. 4, 2016

Re: [Pharo-dev] ifTrue ifFalse shortcuts

by stepharo

> exactlyâ¦ we even have the algorithm implemented for this. > I insist I would enhance ocompletion instead of adding an expansion shortcut. But the rules may not be the same and we will see what lukas will do. and if someone want to hack just that now then we can use it now. Stef > > Esteban > >> -- >> Cyril Ferlicot >> >> http://www.synectique.eu >> >> 165 Avenue Bretagne >> Lille 59000 France >> > >

Aug. 3, 2016

Re: [Pharo-dev] ifTrue ifFalse shortcuts

by stepharo

Le 3/8/16 Ã 14:21, Peter Uhnak a Ã©crit : >> thatâs a lot better than hardcoding specific expansions, yes. >> I still believe this is work of completion engine, thoughâ¦ >> > I don't know the current status (it's summer holidays), but we had a student that was interested in working on the completion engine as his bachelor thesis next year, so templates and such maybe could be part of it too. If nicolai wants to hack it now let him do. There are plenty of space for completion and to me completion and expansion are not automatically the same. Stef > > Peter > >

Aug. 3, 2016

Re: [Pharo-dev] ifTrue ifFalse shortcuts

by stepharo

> itf<ctrl-e> > > ==> ifTrue: [ ] ifFalse: [ ] > > The could be an interface to define these code expansions - initially > at least on a purely personal basis. > > > And this is not really for adding a new feature. This shortcut > already (always :) ) existed > > With a single shortcut for code expansion, perhaps a few other > existing combinations could be freed up. > > > good idea, some kind of template expansion with user defined templates + 1 like that we can create the one we like :) Excellent idea! Stef

Aug. 3, 2016

Re: [Pharo-dev] ifTrue ifFalse shortcuts

by stepharo

Hi ben I think that this it the way to go: Only one key binding to rule all the expansions :) Stef > On Wed, Aug 3, 2016 at 4:36 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> I will just re-post my first answer: >> >> if reintroduce them means reintroduce them hardcoded as before, then Iâm >> complete against it and I WILL NOT integrate such solution. >> Iâm sorry for being so strong here, but previous implementation was lame and >> we need to get rid of them. >> >> Now, I understand people are used to use those bindings and also some others >> (no idea which ones because I never used themâ¦ for me ocompletion is good >> enoughâ¦ but those are tastes). So I would be very happy to integrate a >> generic way to define keybindings and outputs (which is already there, with >> keymapping, but I mean an editor or something), and I would be very happy to >> integrate a default configuration (which of course, will include >> #ifTrue:/##ifFalse:) > I would guess code expansions could be many and varied between > different individuals, and quickly consume available keyboard > shortcuts. Perhaps a generic mechanism would be single shortcut for > "code expansion" which processes the letters preceding the cursor. > For example, using shortcut <ctrl-e> for code expansion and typing... > > itf<ctrl-e> > > ==> ifTrue: [ ] ifFalse: [ ] > > The could be an interface to define these code expansions - initially > at least on a purely personal basis. > >> And this is not really for adding a new feature. This shortcut already (always :) ) existed > With a single shortcut for code expansion, perhaps a few other > existing combinations could be freed up. > > cheers -ben > >> Esteban >> >> On 03 Aug 2016, at 10:30, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: >> >> >> 2016-08-03 10:27 GMT+02:00 Guille Polito <guillermopolito(a)gmail.com>: >>> I'm also against. >>> >>> - They take a place in the shortcuts that prevents others to use it >>> - If lazy people really needs this, the code completion should be >>> enhanced. This is a code completion concern... >> >> +1 >> >> >

Aug. 3, 2016