January 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] How to browse users of a Trait

by Noury Bouraqadi

Yes, there is no support for traits in OB :-( On 23 janv. 2011, at 09:11, laurent laffont wrote: > Hi, > > in the browser, when selecting a Trait -> right-click -> browse references the References browser is empty. > > Is it supposed to work or there's an another way to browse users of a Trait ? > > Laurent Laffont > > Pharo Smalltalk Screencasts: http://www.pharocasts.com/ > Blog: http://magaloma.blogspot.com/

Jan. 24, 2011

Re: [Pharo-project] What about a little rename in MouseEvent?

by Nicolas Cellier

Sure, we got the right to change historical code. But beware, naming actions with physical button positioncould be misleading... ... it does not take into account the logical indirection. We could as well use intention revealing names like selectButton operateButton haloButton... .. Err, no more halo in Pharo, these names are prematurely frozen and don't take future evolutions into account. Oh, we need some more neutral naming scheme, but for sure, something less colorfull that these childish st-80 and e toys. I suggest you use whiteButton greyButton blackButton, or maybe paleBlueButton, lightCyanButton to be more inline with an aqua theme ;) Nicolas 2011/1/24 Marcus Denker <marcus.denker(a)inria.fr>: > > On Jan 24, 2011, at 5:39 AM, Guillermo Polito wrote: > > I hate yellowButtonPressed and redButtonPressed and blueButtonPressed > messages. > > Why not lefClick, rightClick and "middleClick"? > > > Yes. > Back in the days, the color buttons where "holy cows". You just could not > even suggest to > change it. > For me, after 13 years of Squeak and later Pharo, I still have no clue which > color means what... > they have no meaning. There is no green button on my mouse. > Marcus > > > > > -- > Marcus Denker Â --Â http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. >

Jan. 24, 2011

Re: [Pharo-project] Issue 3583 in pharo: Shout should only be active in code panes

by pharo＠googlecode.com

Comment #2 on issue 3583 by tudor.gi...(a)gmail.com: Shout should only be active in code panes http://code.google.com/p/pharo/issues/detail?id=3583 Guillermo, could you propose a change set or a slice so that we can work on?

Jan. 24, 2011

Re: [Pharo-project] Issue 3583 in pharo: Shout should only be active in code panes

by pharo＠googlecode.com

Updates: Cc: guillermopolito marcus.denker stephane.ducasse Comment #1 on issue 3583 by tudor.gi...(a)gmail.com: Shout should only be active in code panes http://code.google.com/p/pharo/issues/detail?id=3583 From Guillermo: Why not delegate it in the used Editor ? SmalltalkEditor should use shout while the other editors should use the NullTextStyler. Maybe something like this: PluggableTextMorph>>useDefaultStyler self styler: textMorph editor styler Or better: PluggableTextMorph>>useDefaultStyler self styler: textMorph styler And then Editor>>styler ^NullTextStyler new SmalltalkEditor>>styler ^... ... Anyways, I'm looking that PluggableTextMorph>>textMorphClass "Answer the class used to create the receiver's textMorph" ^TextMorphForEditView and TextMorphForEditView>>editorClass ^ SmalltalkEditor So it's what I suggested needs a lot of work more... Guille

Jan. 24, 2011

Re: [Pharo-project] default styler is shout

by Tudor Girba

Hi, I opened a ticket. We should move the discussion there: http://code.google.com/p/pharo/issues/detail?id=3583 Cheers, Doru On 24 Jan 2011, at 08:31, Marcus Denker wrote: > > On Jan 24, 2011, at 2:19 AM, Guillermo Polito wrote: > >> But that imperfect solution won't be a good solution either, since we are not going to have shout styler anywhere :). >> > > So how is that solved in1.1? We need, for 1.2, just a *usable* compromise. Then we can iterate in 1.3 > > Marcus > > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > -- www.tudorgirba.com "In a world where everything is moving ever faster, one might have better chances to win by moving slower."

Jan. 24, 2011

[Pharo-project] Issue 3583 in pharo: Shout should only be active in code panes

by pharo＠googlecode.com

Status: Accepted Owner: tudor.gi...(a)gmail.com Labels: Type-Patch Milestone-1.2 Importance-High New issue 3583 by tudor.gi...(a)gmail.com: Shout should only be active in code panes http://code.google.com/p/pharo/issues/detail?id=3583 In the latest Morphic version, the default styler of the PluggableTextMorph is given by: useDefaultStyler "This should be changed to a proper registry but as long as there is only shout this will do" Smalltalk globals at: #SHTextStylerST80 ifPresent: [ :stylerClass | self styler: (stylerClass new view: self) ] ifAbsent: [ self styler: ( NullTextStyler new view: self) ] Thus, if Shout is loaded, you will get it in all text morphs by default. Given that TextMorph should be general and be used in all sorts of contexts, the default behavior should be the original: useDefaultStyler "This should be changed to a proper registry but as long as there is only shout this will do" self styler: (NullTextStyler new view: self; yourself).

Jan. 24, 2011

Re: [Pharo-project] doc on ob requests and commands

by Tudor Girba

Thanks, Lukas. I did read the comments. I understand why Commands and Requests are first class entities, and what they do individually. In Glamour, we have Actions which are similar to OB Commands. However, now we do not have explicit Requests, and I wanted to learn from OB. My main current question is what are the reasons for OBInteractionRequest to subclass Notification? Cheers, Doru On 23 Jan 2011, at 23:34, Lukas Renggli wrote: >> I am browsing OB to understand the design of the Requests and the commands. In particular, I am interested to understand why OBRequests are Notifications and how they link with the commands. >> >> Is there anywhere I can read about it? > > Please check the class comments of OBInteractionRequest and subclasses. > > "OBInteractionRequest is an abstract superclass for notifications that > request some interaction with the user. It's useful for catching such > notifications in an exception handler, while allowing other > notifications to operate normally." > > So all these requests are interacting in some way with the user, e.g. > they open a new browser, they close a browser, they refresh a browser, > they show a specific dialog, they change the mouse cursor, etc. And > depending on the current view these requests are handled differently. > In OB-Morphic the respective morphic actions are performed, in OB-Web > the request is serialized to JSON and performed on the client side, > ... and in the tests the events are silently captured and verified > using assertions. > > OBCommand is something entirely different. It represents the > first-class actions (menu items, buttons) in a browser. The only way > an OBCommand can interact with the user and for example request > additional information is through OBInteractionRequests that might be > triggered at any point. > > Lukas > > -- > Lukas Renggli > www.lukas-renggli.ch > -- www.tudorgirba.com "Being happy is a matter of choice."

Jan. 24, 2011

Re: [Pharo-project] default styler is shout

by Marcus Denker

On Jan 24, 2011, at 2:19 AM, Guillermo Polito wrote: > But that imperfect solution won't be a good solution either, since we are not going to have shout styler anywhere :). > So how is that solved in1.1? We need, for 1.2, just a *usable* compromise. Then we can iterate in 1.3 Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Jan. 24, 2011

Re: [Pharo-project] What about a little rename in MouseEvent?

by Marcus Denker

On Jan 24, 2011, at 5:39 AM, Guillermo Polito wrote: > I hate yellowButtonPressed and redButtonPressed and blueButtonPressed messages. > > Why not lefClick, rightClick and "middleClick"? > Yes. Back in the days, the color buttons where "holy cows". You just could not even suggest to change it. For me, after 13 years of Squeak and later Pharo, I still have no clue which color means what... they have no meaning. There is no green button on my mouse. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Jan. 24, 2011

[Pharo-project] What about a little rename in MouseEvent?

by Guillermo Polito

I hate yellowButtonPressed and redButtonPressed and blueButtonPressed messages. Why not lefClick, rightClick and "middleClick"? Cheers, Guille

Jan. 24, 2011