April 2012 - Pharo-dev - lists.pharo.org

[Pharo-project] Pharo-2.0-Tests Â» 32,linux - Build # 1 - Failure!
by jenkins-pharo.ci.inria.fr＠jenkins-server.lille.inria.fr April 23, 2012

April 23, 2012

1 0

[Pharo-project] ECompletion/Shout bug
by StÃ©phane Ducasse April 23, 2012

April 23, 2012

Hi I get a bug with OCompletion/Ecompletion TextEditor>>changeEmphasis try to type menuList nextPut: and you get a bug. Now in addition I do not understand what I see in the debugger: As you see model returns a debugger and the debugger title show FlatMessageListBrowser Stef

3 5

[Pharo-project] Feedback about SmallLint
by Mariano Martinez Peck April 23, 2012

April 23, 2012

Hi guys. After our meeting at Lille, I did a pass of SmallLint over Fuel project. I have to say that I enjoyed the tool and that. I love the manifiesto idea. I love to store metada and to be able to reject rules and scenarios to avoid having false positives again in the future. In addition, it looks like I had less false positive than with other tools. However, there were a couple of rules that I don't understand or may suggest something: 1) First, apart form showing the package between parenthesis, I would also show the protocol (category). Because some rules play with that, so it is handy if you can directly see them there, otherwise you need to browse the code. 2) RBContainsRule is not clear for me. *" 'Checks for the common code fragment: "(aCollection detect: [:each | ''some condition''] ifNone: [nil]) ~= nil". contains: can simplify this code to "aCollection contains: [:each | ''some condition'']". Not only is the contains: variant shorter, it better signifies what the code is doing.'"* That is not very true. #contains answers true or false, while detect:ifNone:[] answers whatever, and in your example it is nil. So, the answer will be different and hence it is not the same. Ok, in your example, you compare after with == nil... but... I don't really see a use case. For example, in my case it detected: classNamed: className ^ (migrations detect: [:m | m sourceClassName = className ] ifNone: [ ^ self globalClassNamed: className ]) targetClass. 3) RBLawOfDemeterRule: maybe you can exclude string concatenation? (#,) because it detected a lot of messages like this: signalWith: aGlobalName and: aSelector ^ self signal: 'Method ', aGlobalName, '>>#', aSelector, ' not found.' Also, what about excluding messages like #asXXX. For example, here it detected "self signature asByteArray". Is that completly breaking the law of demeter? mmm I don't think so. verifySignatureFrom: aDecoder | streamSignature | streamSignature := ByteArray new: self signature size. aDecoder nextEncodedBytesInto: streamSignature. (self signature asByteArray = streamSignature) ifFalse: [ FLBadSignature signalCurrentSignature: self signature streamSignature: streamSignature ]. 4) RBSentNotImplementedRule: I didn't understand why it has selected: largeIdentityHash <primitive: 75> self primitiveFailed both messages are implemented :( 5) RBClassInstVarNotInitializedRule could be smarter and search not only for #initialize but for #initializeXXX. Lots of times, I initialize my objects with data, using a particular nitialize method, such as: initializeWithBehaviors: someBehaviors extensionMethods: someExtensionMethods so the rule says there is no initialize...but I have that one ;) That's all the feedback so far. It helped me to find some things to improve so thanks! -- Mariano http://marianopeck.wordpress.com

4 5

[Pharo-project] completion lets some traces
by StÃ©phane Ducasse April 23, 2012

April 23, 2012

Esteban don't you have the same problem than me with ecompletion? I get a slow vanishing of propositions. Stef

2 2

[Pharo-project] Example Redline Smalltalk WEB app ...
by James Ladd April 23, 2012

April 23, 2012

import: 'st.redline.stout.Stout'. Stout < #Web. - initialize super initialize. self get: '/' do: [ 'Hello World from Smalltalk Web' ].

1 0

[Pharo-project] Redline Smalltalk ...
by James Ladd April 23, 2012

April 23, 2012

Redline Smalltalk has undergone some Big changes, maybe now is a good time for you to try it? http://redline.st

3 2

[Pharo-project] Nautilus first impression
by Sean P. DeNigris April 23, 2012

April 23, 2012

Wow, Nautilus is *really* fun to use! I have quite a few ideas for plugins... A few suggestions... * Hierarchical package list - also, since with Metacello the convention is (e.g. P-Core, P-UI, P-Tests) with no overarching package, it should group all packages matching P-*, even if they are technically separate packages * I miss the search bar from OB where I could just start typing as soon as I opened the window. It seems that Nautilus doesn't set the keyboard focus anywhere useful. Options: - search bar - typing brings up the class search dialog - give keyboard focus to the package list so I can use the shortcuts right away. This may be the best one because I have access to 3 options: - cmd-F to search packages - cmd-f to search classes - start typing to do a basic package search * creating new methods - when you click a protocol name, the "messageSelectorAndArgumentNames" template is displayed in the code pane, and is pre-selected. I found this very confusing as a newbie because the selection made me think that I could start typing to replace the template, but the keyboard focus is not on the template. It's also useless because when you click on the code pane, it unselects, so you have to double-click anyway. Two suggestions - from the class pane, protocol pane, or both, have an "add method" menu item that transfers focus to the preselected template - when just clicking on a protocol, don't pre-select the template * back/forward buttons for history navigation? * a centralized place to put/list plugins so we can share them Many thanks to Benjamin. This was sorely needed! Cheers, Sean -- View this message in context: http://forum.world.st/Nautilus-first-impression-tp4578301p4578301.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

7 23

[Pharo-project] Unresponsive 1.4 image
by Janko MivÅ¡ek April 22, 2012

April 22, 2012

Hi guys, Well, this bug is something you should finally find and solve ASAP, because it certainly don't give a confidence to the Pharo for serious work. So, I just have again an image unresponsive to keyboard and mouse input. Built from latest 1.4 OneClick. If someone wants it for debugging, I'm happy to send you the whole image. Image became unresponsive after I started it again. Image was otherwise snapshoted in background every hour. Is this maybe a reason? Best regards Janko -- Janko MivÅ¡ek Aida/Web Smalltalk Web Application Server http://www.aidaweb.si

7 30

Re: [Pharo-project] [ANN] Styled Text Editor for Cuis 4.0 Smalltalk
by Marcus Denker April 22, 2012

April 22, 2012

On Apr 21, 2012, at 9:17 PM, phil(a)highoctane.be wrote: > Great news! > > I am currently busy looking after Text, TextAttributes, TextConstants, Paragraph... and god, it went through the grinder and it shows. > Isn't it amazing how bad the Squeak code is for text and everything media considering that the goal was to be the media environment for the future? Marcus -- Marcus Denker -- http://marcusdenker.de

4 4

[Pharo-project] Morphic Event handler crap
by Guillermo Polito April 22, 2012

April 22, 2012

EventHandler>>on: eventName send: selector to: recipient eventName == #mouseDown ifTrue: [mouseDownRecipient := recipient. mouseDownSelector := selector. ^ self]. eventName == #mouseMove ifTrue: [mouseMoveRecipient := recipient. mouseMoveSelector := selector. ^ self]. eventName == #mouseStillDown ifTrue: [mouseStillDownRecipient := recipient. mouseStillDownSelector := selector. ^ self]. eventName == #mouseUp ifTrue: [mouseUpRecipient := recipient. mouseUpSelector := selector. ^ self]. eventName == #mouseEnter ifTrue: [mouseEnterRecipient := recipient. mouseEnterSelector := selector. ^ self]. eventName == #mouseLeave ifTrue: [mouseLeaveRecipient := recipient. mouseLeaveSelector := selector. ^ self]. eventName == #mouseEnterDragging ifTrue: [mouseEnterDraggingRecipient := recipient. mouseEnterDraggingSelector := selector. ^ self]. eventName == #mouseLeaveDragging ifTrue: [mouseLeaveDraggingRecipient := recipient. mouseLeaveDraggingSelector := selector. ^ self]. eventName == #click ifTrue: [clickRecipient := recipient. clickSelector := selector. ^ self]. eventName == #doubleClick ifTrue: [doubleClickRecipient := recipient. doubleClickSelector := selector. ^ self]. eventName == #doubleClickTimeout ifTrue: [doubleClickTimeoutRecipient := recipient. doubleClickTimeoutSelector := selector. ^ self]. eventName == #startDrag ifTrue: [startDragRecipient := recipient. startDragSelector := selector. ^ self]. eventName == #keyStroke ifTrue: [keyStrokeRecipient := recipient. keyStrokeSelector := selector. ^ self]. eventName == #gesture ifTrue: [ ^self onGestureSend: selector to: recipient ]. self error: 'Event name, ' , eventName , ' is not recognizable.' First) It is not handling KeyDown and keyUp :) Second) it does not support multiple handlers for the same event Moving it to announcements in a first attempt seems too agressive :P. Working a bit on it :). Guille

1 0