- Pharo-dev - lists.pharo.org

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

by Sven Van Caekenberghe

On 24 Jan 2011, at 08:25, Marcus Denker wrote: > 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 #select, #menu and #extra ? Then again, touch UI is different again. Sven

Jan. 24, 2011

Re: [Pharo-project] search stack tricks

by CÃ©drick BÃ©ler

hi, maybe UndeclaredVariable>>openMenuIn: aBlock > When I accept the method, the "Unknow variable...." dialog pops up. > > But I struggle to find from where this dialog has been created. > > So when you have a modal dialog and you want to find / explore the > stack/context from which it has been opened, how do you get it ? > I have 2 ways... look for the text or the dialog... with ALT + Shift + E (on Unknow for example), or I bring the halos and the inspect the model (but seems difficult there)... Cheers, > > Cheers, > > Laurent Laffont (@lolgzs) > > Pharo Smalltalk Screencasts: http://www.pharocasts.com/ > Blog: http://magaloma.blogspot.com/ > -- CÃ©drick

Jan. 24, 2011

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

by pharo＠googlecode.com

Comment #3 on issue 3583 by Benjamin...(a)gmail.com: Shout should only be active in code panes http://code.google.com/p/pharo/issues/detail?id=3583 And what about a PluggableTextMorph used to display code ? Maybe PluggableTextMoprh should have as a parameter during their creation a keyword to say if they want to be text styled or not like: PluggableTextMoprh new beStyled And by default a PluggableTextMorph isn't styled

Jan. 24, 2011

[Pharo-project] whisker browser

by Tudor Girba

Hi, Does anybody have an image with a working Whisker Browser? I would be interested in learning from it. Cheers, Doru -- www.tudorgirba.com "Next time you see your life passing by, say 'hi' and get to know her."

Jan. 24, 2011

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

by Marcus Denker

On Jan 24, 2011, at 9:36 AM, Nicolas Cellier wrote: > 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 *no* Colors have no *meaning* in this context. I can not even tell you the three colors we have now. And not at all which is supposed to be the middle one. Colors for buttons make no sense *at all* if your buttons have no colors. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Jan. 24, 2011

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