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

Overwrite repository in symbolic version

by Yuriy Tymchuk

Hi, Iâm using git for versioning, and usually I just work with master branch. Now I have created another branch, can I create at least temporal symbolic version that will work on a current baseline, but will use different ârepositoryâ and so other branch? Or is there another good way to handle branches? Uko

Feb. 1, 2015

Re: [Pharo-dev] Proposal for LiteralArray class

by Ben Coman

On Sun, Feb 1, 2015 at 7:39 PM, Nicolai Hess <nicolaihess(a)web.de> wrote: > > > 2015-02-01 10:52 GMT+01:00 Ben Coman <btc(a)openinworld.com>: > >> >> Looking into Image locking problems [1] caused by a recursive array such >> as this... >> >> literalArray := #( 1 2 3 ). >> literalArray at: 3 put: literalArray. >> >> I find that "literalArray printString" locks the image due to >> Array>>printOn: use of the recursive #shouldBePrintedAsLiteral method. Now >> its implementation is identical to #isLiteral and indeed "literalArray >> isLiteral" also locks the Image. So comparing implementors of #isLiteral... >> >> >> > > Squeak uses a Set to store all visited elements for > shouldBePrintedAsLiteral and this protects against the recursive loop. > > shouldBePrintedAsLiteralVisiting: aSet > self class == Array ifFalse: > [^false]. > (aSet includes: self) ifTrue: > [^false]. > aSet add: self. > ^self allSatisfy: [:each | each shouldBePrintedAsLiteralVisiting: aSet] > > > isn't there a common pattern to handle this kind of potential endless > recursion? > There was a squeak discussion including a passing suggestion for a generic DepthFirstfTraversal safe against cyclic structures... http://forum.world.st/The-Trunk-Collections-ul-564-mcz-td4741229.html > Object>>isLiteral ^false >> Boolean>>isLiteral ^true >> Character>>isLiteral ^true >> Integer>>isLiteral ^true >> String>>isLiteral ^true >> UndefinedObject>>isLiteral ^true >> >> ByteArray>>isLiteral ^self class == ByteArray >> Float>>isLiteral ^self isFinite "^(self - self) = 0.0" >> ScaledDecimal>>isLiteral ^denominator = 1 or: [(10 raisedTo: >> scale)\\denominator = 0] >> >> Array>>isLiteral ^self class == Array and: [self allSatisfy: [:each | >> each isLiteral]] >> >> ...I find most are very basic (might even say deterministic), with the >> recursion of Array>>isLiteral seeming an annomaly. Also, the big IF >> condition in Array>>printOn: smells like a design decision being made at >> runtime (Valloud AMCOS p12). >> >> Array>>printOn: aStream >> self shouldBePrintedAsLiteral ifTrue: [self printAsLiteralFormOn: >> aStream. ^ self]. >> self isSelfEvaluating ifTrue: [self printAsSelfEvaluatingFormOn: aStream. >> ^ self]. >> super printOn: aStream >> >> Flipping between two printString formats seems like selecting between two >> class types. Indeed, if we had a LiteralArray class, there would be no need >> for its printOn: to recursively search to determine its form, thus allowing >> #printStringLimitedTo: to do its thing to protect against infinite >> recursion. >> >> Also, instead of a recursive Array>>isLiteral we'd have something like >> LiteralArray>>isLiteral ^true >> Array>>isLiteral ^false >> which seems to align much better with the pattern of the other #isLiteral >> implementors. >> >> I notice there is both RBArrayNode and RBLiteralArrayNode. >> >> So what are the wider concerns that might apply? >> (In particular, I'm not sure how the #isSelfEvaluating (which is also >> recursive) fits into the big picture) >> >> cheers -ben >> >> [1] https://www.mail-archive.com/pharo-dev@lists.pharo.org/msg25156.html >> > > @Stef/Marcus, As part of this, since Array>>#shouldBePrintedAsLiteral implementation is the same as the Array>>isLiteral I was going to suggest removing the former, but I see the introduction of #shouldBePrintedAsLiteral was popular with you guys [1]. Is there some reason why Array>>shouldBePrintedAsLiteral should not be "^self isLiteral" or just removed, so Object>>shouldBePrintedAsLiteral is inherited ? [1] http://pharo-dev.pharo.narkive.com/KVAEE1Xv/pharo-project-issue-3426-in-pha… cheers -ben

Feb. 1, 2015

Re: [Pharo-dev] Adding an entry in the menu for GSpotter

by Tudor Girba

Yes, that is a problem we have to fix. I think for now we should add it to the World menu. Doru On Sun, Feb 1, 2015 at 2:58 PM, stepharo <stepharo(a)free.fr> wrote: > Hi > > Since I have probably (in fact I have no idea) a conflict between the mac > os x shortcuts and GSpotter I have > no way to > - open it > - find how to open it > - ... > > So having a menu entry with a shortcut would amazingly helps. > > Stef > > -- www.tudorgirba.com "Every thing has its own flow"

Feb. 1, 2015

Re: [Pharo-dev] How to browse a given keymap category

by Ben Coman

On Sun, Feb 1, 2015 at 7:04 PM, stepharo <stepharo(a)free.fr> wrote: > Hi > > I wanted to fix https://pharo.fogbugz.com/default.asp?14845 > Selecting a class and pressing command B+M raises an error so either we > should check that the selected method is not nil (I do not like that much) > or the key binding should not work on classes (preferred solution). > Its not just that it should not work on classes. Open Nautilus and before selecting anything press CMD-B+M and you get the error. Also, select a method then click on it again to deselect it, then press CMD-B+M and you get the error cheers -ben

Feb. 1, 2015

Re: [Pharo-dev] How to browse a given keymap category

by stepharo

Thanks doru I was thinking about GTInspector when I could not find my way :) I will try to understand if I can fix the problem I found. Stef Le 1/2/15 13:54, Tudor Girba a Ã©crit : > Hi, > > Inspect KMRepository default and you will get all bindings and all > local bindings. > > For example, in the picture below: > - Inspect: KMRepository default > - Filter the Keys by: Cmd + B , > - Select the browseMessages entry and see the code. > > Inline image 1 > > > The picture below shows how to work with one category: > - Inspect: KMRepository default categories > - Select a the NautilusGlobalShortcuts > - Filter by: "Messages" > - Select the keymapping and see the code. > > Inline image 2 > > You can see more explanations here: > http://www.humane-assessment.com/blog/managing-morph-keybindings-with-gtins… > > Is this enough? > > Cheers, > Doru > > > On Sun, Feb 1, 2015 at 12:04 PM, stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>> wrote: > > Hi > > I wanted to fix https://pharo.fogbugz.com/default.asp?14845 > Selecting a class and pressing command B+M raises an error so > either we should check that the selected method is not nil (I do > not like that much) or the key binding should not work on classes > (preferred solution). > > buildBrowseShortcutsOn: aBuilder > <keymap> > > (aBuilder shortcut: #browseSenders) > category: #NautilusGlobalShortcuts > default: $b command , $n command > do: [:target | target browseSendersOfMessages ] > description: 'Browse senders of the selected method'. > > (aBuilder shortcut: #browseClassRefs) > category: #NautilusGlobalShortcuts > default: $b command, $n command shift > do: [ :target | target browseClassRefs ] > description: 'Browse class references'. > > (aBuilder shortcut: #browseImplementors) > category: #NautilusGlobalShortcuts > default: $b command , $m command > do: [:target | target browseMessages ] > ^^^^^^^^^^^^^^^^^^^^^^^^^ > description: 'Browse implementors of the selected method'. > > > a "bad solution to my eye" is > browseMessages > self selectedMethod iifNil: [^ self]. <<<<< > self browseMessagesFrom: self selectedMethod selector > > > Now my question is then how can I find the different categories of > bindings such as #NautilusGlobalShortCuts > I tried to inspect a builder from the debugger but I got lost and > should run to catch a train. > > Stef > > > > > -- > www.tudorgirba.com <http://www.tudorgirba.com> > > "Every thing has its own flow"

Feb. 1, 2015

Adding an entry in the menu for GSpotter

by stepharo

Hi Since I have probably (in fact I have no idea) a conflict between the mac os x shortcuts and GSpotter I have no way to - open it - find how to open it - ... So having a menu entry with a shortcut would amazingly helps. Stef

Feb. 1, 2015

Re: [Pharo-dev] How to browse a given keymap category

by Tudor Girba

Hi, Inspect KMRepository default and you will get all bindings and all local bindings. For example, in the picture below: - Inspect: KMRepository default - Filter the Keys by: Cmd + B , - Select the browseMessages entry and see the code. [image: Inline image 1] The picture below shows how to work with one category: - Inspect: KMRepository default categories - Select a the NautilusGlobalShortcuts - Filter by: "Messages" - Select the keymapping and see the code. [image: Inline image 2] You can see more explanations here: http://www.humane-assessment.com/blog/managing-morph-keybindings-with-gtins… Is this enough? Cheers, Doru On Sun, Feb 1, 2015 at 12:04 PM, stepharo <stepharo(a)free.fr> wrote: > Hi > > I wanted to fix https://pharo.fogbugz.com/default.asp?14845 > Selecting a class and pressing command B+M raises an error so either we > should check that the selected method is not nil (I do not like that much) > or the key binding should not work on classes (preferred solution). > > buildBrowseShortcutsOn: aBuilder > <keymap> > > (aBuilder shortcut: #browseSenders) > category: #NautilusGlobalShortcuts > default: $b command , $n command > do: [:target | target browseSendersOfMessages ] > description: 'Browse senders of the selected method'. > > (aBuilder shortcut: #browseClassRefs) > category: #NautilusGlobalShortcuts > default: $b command, $n command shift > do: [ :target | target browseClassRefs ] > description: 'Browse class references'. > > (aBuilder shortcut: #browseImplementors) > category: #NautilusGlobalShortcuts > default: $b command , $m command > do: [:target | target browseMessages ] > ^^^^^^^^^^^^^^^^^^^^^^^^^ > description: 'Browse implementors of the selected method'. > > > a "bad solution to my eye" is > browseMessages > self selectedMethod iifNil: [^ self]. <<<<< > self browseMessagesFrom: self selectedMethod selector > > > Now my question is then how can I find the different categories of > bindings such as #NautilusGlobalShortCuts > I tried to inspect a builder from the debugger but I got lost and should > run to catch a train. > > Stef > > -- www.tudorgirba.com "Every thing has its own flow"

Feb. 1, 2015

Re: [Pharo-dev] How to browse a given keymap category

by Ben Coman

On Sun, Feb 1, 2015 at 7:04 PM, stepharo <stepharo(a)free.fr> wrote: > > > how can I find the different categories of bindings such as > #NautilusGlobalShortCuts > Just from poking around, maybe "KMRepository default categories" ? cheers -ben

Feb. 1, 2015

Re: [Pharo-dev] Proposal for LiteralArray class

by Nicolai Hess

2015-02-01 10:52 GMT+01:00 Ben Coman <btc(a)openinworld.com>: > > Looking into Image locking problems [1] caused by a recursive array such > as this... > > literalArray := #( 1 2 3 ). > literalArray at: 3 put: literalArray. > > I find that "literalArray printString" locks the image due to > Array>>printOn: use of the recursive #shouldBePrintedAsLiteral method. Now > its implementation is identical to #isLiteral and indeed "literalArray > isLiteral" also locks the Image. So comparing implementors of #isLiteral... > > > Squeak uses a Set to store all visited elements for shouldBePrintedAsLiteral and this protects against the recursive loop. shouldBePrintedAsLiteralVisiting: aSet self class == Array ifFalse: [^false]. (aSet includes: self) ifTrue: [^false]. aSet add: self. ^self allSatisfy: [:each | each shouldBePrintedAsLiteralVisiting: aSet] isn't there a common pattern to handle this kind of potential endless recursion? > Object>>isLiteral ^false > Boolean>>isLiteral ^true > Character>>isLiteral ^true > Integer>>isLiteral ^true > String>>isLiteral ^true > UndefinedObject>>isLiteral ^true > > ByteArray>>isLiteral ^self class == ByteArray > Float>>isLiteral ^self isFinite "^(self - self) = 0.0" > ScaledDecimal>>isLiteral ^denominator = 1 or: [(10 raisedTo: > scale)\\denominator = 0] > > Array>>isLiteral ^self class == Array and: [self allSatisfy: [:each | > each isLiteral]] > > ...I find most are very basic (might even say deterministic), with the > recursion of Array>>isLiteral seeming an annomaly. Also, the big IF > condition in Array>>printOn: smells like a design decision being made at > runtime (Valloud AMCOS p12). > > Array>>printOn: aStream > self shouldBePrintedAsLiteral ifTrue: [self printAsLiteralFormOn: aStream. > ^ self]. > self isSelfEvaluating ifTrue: [self printAsSelfEvaluatingFormOn: aStream. > ^ self]. > super printOn: aStream > > Flipping between two printString formats seems like selecting between two > class types. Indeed, if we had a LiteralArray class, there would be no need > for its printOn: to recursively search to determine its form, thus allowing > #printStringLimitedTo: to do its thing to protect against infinite > recursion. > > Also, instead of a recursive Array>>isLiteral we'd have something like > LiteralArray>>isLiteral ^true > Array>>isLiteral ^false > which seems to align much better with the pattern of the other #isLiteral > implementors. > > I notice there is both RBArrayNode and RBLiteralArrayNode. > > So what are the wider concerns that might apply? > (In particular, I'm not sure how the #isSelfEvaluating (which is also > recursive) fits into the big picture) > > cheers -ben > > [1] https://www.mail-archive.com/pharo-dev@lists.pharo.org/msg25156.html >

Feb. 1, 2015

How to browse a given keymap category

by stepharo

Hi I wanted to fix https://pharo.fogbugz.com/default.asp?14845 Selecting a class and pressing command B+M raises an error so either we should check that the selected method is not nil (I do not like that much) or the key binding should not work on classes (preferred solution). buildBrowseShortcutsOn: aBuilder <keymap> (aBuilder shortcut: #browseSenders) category: #NautilusGlobalShortcuts default: $b command , $n command do: [:target | target browseSendersOfMessages ] description: 'Browse senders of the selected method'. (aBuilder shortcut: #browseClassRefs) category: #NautilusGlobalShortcuts default: $b command, $n command shift do: [ :target | target browseClassRefs ] description: 'Browse class references'. (aBuilder shortcut: #browseImplementors) category: #NautilusGlobalShortcuts default: $b command , $m command do: [:target | target browseMessages ] ^^^^^^^^^^^^^^^^^^^^^^^^^ description: 'Browse implementors of the selected method'. a "bad solution to my eye" is browseMessages self selectedMethod iifNil: [^ self]. <<<<< self browseMessagesFrom: self selectedMethod selector Now my question is then how can I find the different categories of bindings such as #NautilusGlobalShortCuts I tried to inspect a builder from the debugger but I got lost and should run to catch a train. Stef

Feb. 1, 2015