June 2015 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] block syntax experiments

by Ben Coman

I think that would confuse me, and maybe break syntax highlighting. It *looks* like a message send to nothing. How about something that gives more feeling of inserting... add <-- 3 , 4. add <<< 3 , 4. add <<: 3 <<: 4. add @:3 @:4. cheers -ben On Wed, Jun 3, 2015 at 8:17 AM, Francisco Garau <francisco.garau(a)gmail.com> wrote: > Hello, > > I'd like to make some syntax changes that would make block evaluation more > legible. > > Currently we define and evaluate blocks like this: > > inc := [ : x | x + 1 ]. > (inc value: 3) = 4. > addTo := [ : x : y | x + y ]. > (addTo value: 3 value: 4) = 7. > > > But I would like them to be defined like this: > > [ inc: x | x + 1 ]. > (inc: 3) = 4 > > [add: x to: y | x + y ]. > (add: 3 to: 4) = 7. > > > What do you think? Is it feasible? > > I presume it's Opal where I should start looking at implementing this > changes, but any hints/suggestions are welcomed. > > Cheers, > Francisco

June 3, 2015

Re: [Pharo-dev] block syntax experiments

by Peter UhnÃ¡k

> > But I would like them to be defined like this: > > [ inc: x | x + 1 ]. > (inc: 3) = 4 > > [add: x to: y | x + y ]. > (add: 3 to: 4) = 7. > > > What do you think? Is it feasible? > But you still need to have the block saved in a variable. You cannot pollute global namespace with names of parameters within the block, not to mention the fact that most blocks in the system have same parameter names. Now while the idea seems interesting; I cannot imagine how it would work in practice. Imagine collection's "do:" method explicitly stating the name of the argument, which would force me to name it in such and such way which would actually impair the readability. I am sure others will have different opinions. However if you want to try it out, you should apart from Opal have to look also at AST-Core since you are changing syntax. Also I am thinking that combination of variable name + named arguments could perhaps be done purely with overriding doesNotUnderstand: method in BlockClosure and calling value:value: internally. (Or even cull:cull:, but form what I've heard that has some dire performance issues); this could perhaps even solve my comment about enforced naming. Peter >

June 3, 2015

block syntax experiments

by Francisco Garau

Hello, I'd like to make some syntax changes that would make block evaluation more legible. Currently we define and evaluate blocks like this: inc := [ : x | x + 1 ]. (inc value: 3) = 4. addTo := [ : x : y | x + y ]. (addTo value: 3 value: 4) = 7. But I would like them to be defined like this: [ inc: x | x + 1 ]. (inc: 3) = 4 [add: x to: y | x + y ]. (add: 3 to: 4) = 7. What do you think? Is it feasible? I presume it's Opal where I should start looking at implementing this changes, but any hints/suggestions are welcomed. Cheers, Francisco

June 3, 2015

Re: [Pharo-dev] how can we use Spotter to find reference to a class without scrolling down?

by Tudor Girba

Hi, But, that is already possible: - Search for a class, like Object. - Dive in (Cmd+Right) - Type #ref And you will get the list of references to Object. Cheers, Doru On Wed, Jun 3, 2015 at 1:17 AM, Ben Coman <btc(a)openinworld.com> wrote: > I guess he means... Analyse > Class refs > and maybe wanting a syntax like... MyClass #ref > cheers -ben > > On Wed, Jun 3, 2015 at 4:12 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Hi, > > > > If you know the name of the spotter category, you can use the #category, > > like here: > > > http://www.humane-assessment.com/blog/scoping-for-specific-search-category-… > > > > Is this what you are looking for? > > > > Cheers, > > Doru > > > > > > > > On Tue, Jun 2, 2015 at 10:08 PM, stepharo <stepharo(a)free.fr> wrote: > >> > >> Hi guys > >> > >> I often know that I want to look not for the class, its package or > >> methods.... > >> but that I want to get the references to a class. > >> > >> Is there a syntax that I can use to instruct spotter about my needs? > >> > >> Stef > >> > > > > > > > > -- > > www.tudorgirba.com > > > > "Every thing has its own flow" > > -- www.tudorgirba.com "Every thing has its own flow"

June 2, 2015

Re: [Pharo-dev] how can we use Spotter to find reference to a class without scrolling down?

by Ben Coman

I guess he means... Analyse > Class refs and maybe wanting a syntax like... MyClass #ref cheers -ben On Wed, Jun 3, 2015 at 4:12 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > If you know the name of the spotter category, you can use the #category, > like here: > http://www.humane-assessment.com/blog/scoping-for-specific-search-category-… > > Is this what you are looking for? > > Cheers, > Doru > > > > On Tue, Jun 2, 2015 at 10:08 PM, stepharo <stepharo(a)free.fr> wrote: >> >> Hi guys >> >> I often know that I want to look not for the class, its package or >> methods.... >> but that I want to get the references to a class. >> >> Is there a syntax that I can use to instruct spotter about my needs? >> >> Stef >> > > > > -- > www.tudorgirba.com > > "Every thing has its own flow"

June 2, 2015

Re: [Pharo-dev] I need reviewer of https://pharo.fogbugz.com/default.asp?15646

by stepharo

I hate so much this bug.... Le 1/6/15 15:04, Ben Coman a Ã©crit : > Stef, I can now see all the dependent packages for the new slice, but > I still have a strange error. However I'm not sure if its a bug or > something unique at my end. > > Can someone try merging > SLICE-Issue-15646-Cleaning-method-category-api-should-be-protocol-part-1-StephaneDucasse.1 > > What I see at top of stack is two calls to MCVersionMerger>>addVersion: > > MCVersionMerger>>addVersion: aVersion > records add: (MCMergeRecord version: aVersion). > aVersion dependencies > do: [:ea | | dep satisfied | > dep := ea resolve. > satisfied := (records anySatisfy: [:r | r version = dep]). > satisfied ifFalse: [self addVersion: dep]] "<<< race? " > displayingProgress: [ :ea| 'Searching dependency: ', ea > package name] > "15646Note: variable /satisfied/ added for reporting/debugging" > > One level down from where the error occurs the debugger shows... > > /aVersion/ --> a > MCVersion(SLICE-Issue-15646-Cleaning-method-category-api-should-be-protocol-part-1-StephaneDucasse.1) > > /ea/ --> a MCVersionInfo(DebuggerActions-StephaneDucasse.75) > > /dep/ --> nil > > /satisfied/ --> false > > and the following which contradicts the value in /satisfied/ > > (records anySatisfy: [:r | r version = dep]) --> true. > > so there seems to be a race such that the ifFalse block is improperly > executed, such that the recursive call on top of stack has... > > /aVersion/-->nil > > hence MNU receiver of "dependencies" is nil. > > cheers -ben > > > On Mon, Jun 1, 2015 at 10:36 AM, Ben Coman <btc(a)openinworld.com> wrote: >> I tried, but it seems some packages are missing from the inbox. >> cheers -ben >> >> On Sun, May 31, 2015 at 2:19 PM, stepharo <stepharo(a)free.fr> wrote: >>> Hi >>> >>> I continued to clean that classes have categories and method protocols >>> because it was not finished. >>> This entry is just adding protocol in the classes that were missing it, >>> adding comments, and fixing some local senders >>> It does not remove the category API but puts it in a accessing-backward >>> protocol and in a second step I will fix all the senders I can (ie not >>> Metacello for example). >>> Category is really overloaded and we get lost when trying to understand >>> code. >>> I want to rename RBRule 'category' into 'kind' for this reason. >>> >>> Stef >>> >

June 2, 2015

Re: [Pharo-dev] how can we use Spotter to find reference to a class without scrolling down?

by Tudor Girba

Hi, If you know the name of the spotter category, you can use the #category, like here: http://www.humane-assessment.com/blog/scoping-for-specific-search-category-… Is this what you are looking for? Cheers, Doru On Tue, Jun 2, 2015 at 10:08 PM, stepharo <stepharo(a)free.fr> wrote: > Hi guys > > I often know that I want to look not for the class, its package or > methods.... > but that I want to get the references to a class. > > Is there a syntax that I can use to instruct spotter about my needs? > > Stef > > -- www.tudorgirba.com "Every thing has its own flow"

June 2, 2015

how can we use Spotter to find reference to a class without scrolling down?

by stepharo

Hi guys I often know that I want to look not for the class, its package or methods.... but that I want to get the references to a class. Is there a syntax that I can use to instruct spotter about my needs? Stef

June 2, 2015

[pharo-project/pharo-core]

by GitHub

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

June 2, 2015

[pharo-project/pharo-core] b686a7: 50085

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: b686a7f6400aa9d5b4afc0483b53b11aa4bddf2b https://github.com/pharo-project/pharo-core/commit/b686a7f6400aa9d5b4afc048… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-06-02 (Tue, 02 Jun 2015) Changed paths: R Nautilus.package/AbstractNautilusUI.class/class/shortcut-old/buildCommentShortcutsOn_.st R Nautilus.package/AbstractNautilusUI.class/class/shortcut-old/buildEditorCommentKeymappingsOldOn_.st R Nautilus.package/AbstractNautilusUI.class/class/shortcuts/buildEditorCommentKeymappingsOn_.st M Nautilus.package/AbstractNautilusUI.class/definition.st A Nautilus.package/AbstractNautilusUI.class/instance/accessing/fullDisplayedComment.st A Nautilus.package/AbstractNautilusUI.class/instance/accessing/fullDisplayedComment_.st M Nautilus.package/AbstractNautilusUI.class/instance/accessing/updateCodePanel.st M Nautilus.package/AbstractNautilusUI.class/instance/build ui buttons/buildCommentButton.st R Nautilus.package/AbstractNautilusUI.class/instance/build ui text/buildCommentPane.st M Nautilus.package/AbstractNautilusUI.class/instance/build ui text/buildNewCommentText.st M Nautilus.package/AbstractNautilusUI.class/instance/buttons behavior/toggleShowComment.st M Nautilus.package/AbstractNautilusUI.class/instance/buttons behavior/toggleShowFullComment.st A Nautilus.package/AbstractNautilusUI.class/instance/class comment pane/classCommentTextModel.st A Nautilus.package/AbstractNautilusUI.class/instance/class comment pane/promptForCancel.st A Nautilus.package/AbstractNautilusUI.class/instance/class comment pane/takeCommentFromView.st A Nautilus.package/AbstractNautilusUI.class/instance/class comment pane/whenExtendCommentSwitch_.st A Nautilus.package/AbstractNautilusUI.class/instance/class comment pane/whenTextUpdatedInCommentPane_.st M Nautilus.package/AbstractNautilusUI.class/instance/code panel/buildCodePanelWithComment.st M Nautilus.package/AbstractNautilusUI.class/instance/code panel/buildCodePanelWithCommentOnRight.st M Nautilus.package/AbstractNautilusUI.class/instance/code panel/buildCodePanelWithoutComment.st M Nautilus.package/AbstractNautilusUI.class/instance/initialization/initialize.st R Nautilus.package/AbstractNautilusUI.class/instance/newcomment/newCommentTextModel.st R Nautilus.package/AbstractNautilusUI.class/instance/newcomment/updateCommentWith_.st R Nautilus.package/AbstractNautilusUI.class/instance/newcomment/whenTextUpdatedInCommentPane_.st R Nautilus.package/AbstractNautilusUI.class/instance/source code area/addComment_notifying_.st R Nautilus.package/AbstractNautilusUI.class/instance/source code area/commentTextArea.st M Nautilus.package/AbstractNautilusUI.class/instance/source code area/okToChangeComment.st M Nautilus.package/NautilusUI.class/instance/accessing/selectedClassWithoutChangingSelection_.st M Nautilus.package/NautilusUI.class/instance/private/unselectClass.st M Nautilus.package/NautilusUI.class/instance/private/updateOnClassSelection.st A NautilusCommon.package/NautilusExtendCommentSwitch.class/README.md A NautilusCommon.package/NautilusExtendCommentSwitch.class/definition.st A Rubric.package/RubCommentAnnotationDisplayer.class/README.md A Rubric.package/RubCommentAnnotationDisplayer.class/class/querying/key.st A Rubric.package/RubCommentAnnotationDisplayer.class/definition.st A Rubric.package/RubCommentAnnotationDisplayer.class/instance/accessing/backgroundColor.st A Rubric.package/RubCommentAnnotationDisplayer.class/instance/accessing/fontToUse.st A Rubric.package/RubCommentAnnotationDisplayer.class/instance/accessing/level.st A Rubric.package/RubCommentAnnotationDisplayer.class/instance/accessing/textColor.st A Rubric.package/RubCommentAnnotationDisplayer.class/instance/event handling/selectionChanged.st A Rubric.package/RubCommentAnnotationDisplayer.class/instance/event handling/textOfCharBlock_.st A Rubric.package/RubCommentAnnotationDisplayer.class/instance/event handling/updateContents.st A Rubric.package/RubCommentAnnotationDisplayer.class/instance/geometry/computedHeightFrom_.st A Rubric.package/RubCommentAnnotationDisplayer.class/instance/geometry/computedWidthFrom_.st A Rubric.package/RubCommentAnnotationDisplayer.class/instance/geometry/manageLayoutInBounds_.st A Rubric.package/RubCommentAnnotationDisplayer.class/instance/initialize-release/initialize.st A Rubric.package/RubCommentAnnotationDisplayer.class/instance/submorphs-accessing/changeExtendCommentPolicy.st A Rubric.package/RubCommentAnnotationDisplayer.class/instance/submorphs-accessing/changeLineNumbersDisplay.st A Rubric.package/RubCommentAnnotationDisplayer.class/instance/submorphs-accessing/changeWrappingPolicy.st A Rubric.package/RubCommentAnnotationDisplayer.class/instance/submorphs-accessing/extendCommentPolicyMorph.st A Rubric.package/RubCommentAnnotationDisplayer.class/instance/submorphs-accessing/lineNumbersDisplayLabel.st A Rubric.package/RubCommentAnnotationDisplayer.class/instance/submorphs-accessing/lineNumbersDisplayLabelMorph.st A Rubric.package/RubCommentAnnotationDisplayer.class/instance/submorphs-accessing/noteNewOwner_.st A Rubric.package/RubCommentAnnotationDisplayer.class/instance/submorphs-accessing/spacer_.st A Rubric.package/RubCommentAnnotationDisplayer.class/instance/submorphs-accessing/wrappingPolicyLabel.st A Rubric.package/RubCommentAnnotationDisplayer.class/instance/submorphs-accessing/wrappingPolicyLabelMorph.st M Rubric.package/RubEditingMode.class/instance/accessing/editorClass.st A Rubric.package/RubScrolledTextModel.class/instance/text managing/acceptEdits.st A Rubric.package/RubScrolledTextModel.class/instance/text managing/acceptEditsInView.st A Rubric.package/RubScrolledTextModel.class/instance/text managing/setInitialText_.st A Rubric.package/RubScrolledTextMorph.class/instance/accessing rulers/withCommentAnnotation.st M Rubric.package/RubScrolledTextMorph.class/instance/rulers handling/withRuler_.st M Rubric.package/RubSmalltalkEditor.class/class/keymapping/buildShortcutsOn_.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50084.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50085.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50084.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50085.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 50085 15644 empty comment pane in nautilus https://pharo.fogbugz.com/f/cases/15644 http://files.pharo.org/image/50/50085.zip

June 2, 2015