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

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

by Lukas Renggli

> My main current question is what are the reasons for OBInteractionRequest to subclass Notification? To be able to perform user interactions anywhere without having a global OBPlatform instance, and without having to pass OBPlatform in or store OBPlatform anywhere. There can be multiple UI platforms active at the same time and they can even change over the lifetime of a single browser window. Lukas -- Lukas Renggli www.lukas-renggli.ch

Jan. 24, 2011

Re: [Pharo-project] collapsing panes

by Tudor Girba

Thanks a lot, Gary! I gave it a try and it does go in the wanted direction. Now, the next question. I see that you are using a TableLayout. Is there a way to specify a proportion (like in the proportional layout?) for the initial extent of the inner panes? If yes, then I suppose we could merge the two layouts into one. Cheers, Doru On 24 Jan 2011, at 14:51, Benjamin wrote: > I love that :) > It could be very useful ^^ > > > Ben > > On Jan 24, 2011, at 2:36 PM, Gary Chambers wrote: > >> Tricky... >> Just an experiment, but try the following after filing in attached change set. >> Can make the re-proportioning explicit and maybe fix things to constrain to >> the owner morph if interested... >> >> >> | container morph1 morph2 morph3 ex1 ex2 ex3 sp1 sp2| >> morph1 := (PanelMorph new fillStyle: (SolidFillStyle color: Color red)) >> hResizing: #spaceFill; >> vResizing: #spaceFill. >> morph2 := (PanelMorph new fillStyle: (SolidFillStyle color: Color blue)) >> hResizing: #spaceFill; >> vResizing: #spaceFill. >> morph3 := (PanelMorph new fillStyle: (SolidFillStyle color: Color yellow)) >> hResizing: #spaceFill; >> vResizing: #spaceFill. >> ex1 := (UITheme builder newExpander: 'Red' for: morph1) >> expanded: true. >> ex2 := (UITheme builder newExpander: 'Blue' for: morph2) >> expanded: true. >> ex3 := (UITheme builder newExpander: 'Yellow' for: morph3) >> expanded: true. >> sp1 := EdgeGripMorph new >> target: ex1; >> edgeName: #bottom; >> vResizing: #rigid; >> extent: 24 @ ProportionalSplitterMorph splitterWidth; >> on: #mouseDown send: #expandedSizingRigid to: ex1. >> sp2 := EdgeGripMorph new >> target: ex2; >> edgeName: #bottom; >> vResizing: #rigid; >> extent: 24 @ ProportionalSplitterMorph splitterWidth; >> on: #mouseDown send: #expandedSizingRigid to: ex2. >> container := UITheme builder newColumn: { >> ex1. >> sp1. >> ex2. >> sp2. >> ex3}. >> container cellInset: 0. >> container extent: 400@400. >> container openInWindow. >> >> >> >> Have a play/fun. >> >> Regards, Gary >> >> ----- Original Message ----- From: "Tudor Girba" <tudor.girba(a)gmail.com> >> To: "Pharo-project(a)lists.gforge.inria.fr Development" <pharo-project(a)lists.gforge.inria.fr> >> Sent: Friday, January 21, 2011 11:18 PM >> Subject: [Pharo-project] collapsing panes >> >> >> Hi, >> >> I have a question about how to obtain an effect similar to minimizing a pane in Eclipse. Let's consider the example from below. I have a ProportionalLayout because I want to fill the entire space and be able to resize the inside panes. Now, I would also like to have some way of collapsing one of the panes and have the rest resize to fill the rest of the space. It's a bit like I would need some part of a behavior from the TableLayout. >> >> Can anyone provide me with some hints in this direction? Do I need to create a new Layout? >> >> | container morph1 morph2 morph3 window | >> container := PanelMorph new. >> morph1 := PanelMorph new fillStyle: (SolidFillStyle color: Color red). >> morph2 := PanelMorph new fillStyle: (SolidFillStyle color: Color blue). >> morph3 := PanelMorph new fillStyle: (SolidFillStyle color: Color yellow). >> container changeProportionalLayout. >> container addMorph: morph1 fullFrame: (LayoutFrame fractions: (0 @ 0 corner: 1 @ 0.33)). >> container addMorph: morph2 fullFrame: (LayoutFrame fractions: (0 @ 0.33 corner: 1 @ 0.66)). >> container addMorph: morph3 fullFrame: (LayoutFrame fractions: (0 @ 0.66 corner: 1 @ 1)). >> container addPaneSplitters. >> container fillStyle: (SolidFillStyle color: Color yellow). >> container extent: 400@400. >> container openInWindow. >> >> Cheers, >> Doru >> >> >> -- >> www.tudorgirba.com >> >> "Be rather willing to give than demanding to get." >> >> >> >> <ExpanderTweak.1.cs> > > -- www.tudorgirba.com "Every now and then stop and ask yourself if the war you're fighting is the right one."

Jan. 24, 2011

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

by Geert Claes

Ricardo Moran wrote: > > I totally agree with the color buttons being really confusing. What's > funny is that it's not even consistent. For instance, preference > "swapMouseButtons" comment is "if true, swaps mouse buttons 2 and 3". > What's > that suppose to mean? Weren't mouse buttons colored?? :) > > However, I have a question: once you change the names to left, right, > middle, what will happen if swapMouseButtons is true? Will "middleClick" > still mean "middleClick"? > True, I guess in a 3-button environment there will always be a "Primary", "Secondary" and "Middle" button, for left and right-handed people :) -- View this message in context: http://forum.world.st/What-about-a-little-rename-in-MouseEvent-tp3233363p32… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Jan. 24, 2011

Re: [Pharo-project] collapsing panes

by Benjamin

I love that :) It could be very useful ^^ Ben On Jan 24, 2011, at 2:36 PM, Gary Chambers wrote: > Tricky... > Just an experiment, but try the following after filing in attached change set. > Can make the re-proportioning explicit and maybe fix things to constrain to > the owner morph if interested... > > > | container morph1 morph2 morph3 ex1 ex2 ex3 sp1 sp2| > morph1 := (PanelMorph new fillStyle: (SolidFillStyle color: Color red)) > hResizing: #spaceFill; > vResizing: #spaceFill. > morph2 := (PanelMorph new fillStyle: (SolidFillStyle color: Color blue)) > hResizing: #spaceFill; > vResizing: #spaceFill. > morph3 := (PanelMorph new fillStyle: (SolidFillStyle color: Color yellow)) > hResizing: #spaceFill; > vResizing: #spaceFill. > ex1 := (UITheme builder newExpander: 'Red' for: morph1) > expanded: true. > ex2 := (UITheme builder newExpander: 'Blue' for: morph2) > expanded: true. > ex3 := (UITheme builder newExpander: 'Yellow' for: morph3) > expanded: true. > sp1 := EdgeGripMorph new > target: ex1; > edgeName: #bottom; > vResizing: #rigid; > extent: 24 @ ProportionalSplitterMorph splitterWidth; > on: #mouseDown send: #expandedSizingRigid to: ex1. > sp2 := EdgeGripMorph new > target: ex2; > edgeName: #bottom; > vResizing: #rigid; > extent: 24 @ ProportionalSplitterMorph splitterWidth; > on: #mouseDown send: #expandedSizingRigid to: ex2. > container := UITheme builder newColumn: { > ex1. > sp1. > ex2. > sp2. > ex3}. > container cellInset: 0. > container extent: 400@400. > container openInWindow. > > > > Have a play/fun. > > Regards, Gary > > ----- Original Message ----- From: "Tudor Girba" <tudor.girba(a)gmail.com> > To: "Pharo-project(a)lists.gforge.inria.fr Development" <pharo-project(a)lists.gforge.inria.fr> > Sent: Friday, January 21, 2011 11:18 PM > Subject: [Pharo-project] collapsing panes > > > Hi, > > I have a question about how to obtain an effect similar to minimizing a pane in Eclipse. Let's consider the example from below. I have a ProportionalLayout because I want to fill the entire space and be able to resize the inside panes. Now, I would also like to have some way of collapsing one of the panes and have the rest resize to fill the rest of the space. It's a bit like I would need some part of a behavior from the TableLayout. > > Can anyone provide me with some hints in this direction? Do I need to create a new Layout? > > | container morph1 morph2 morph3 window | > container := PanelMorph new. > morph1 := PanelMorph new fillStyle: (SolidFillStyle color: Color red). > morph2 := PanelMorph new fillStyle: (SolidFillStyle color: Color blue). > morph3 := PanelMorph new fillStyle: (SolidFillStyle color: Color yellow). > container changeProportionalLayout. > container addMorph: morph1 fullFrame: (LayoutFrame fractions: (0 @ 0 corner: 1 @ 0.33)). > container addMorph: morph2 fullFrame: (LayoutFrame fractions: (0 @ 0.33 corner: 1 @ 0.66)). > container addMorph: morph3 fullFrame: (LayoutFrame fractions: (0 @ 0.66 corner: 1 @ 1)). > container addPaneSplitters. > container fillStyle: (SolidFillStyle color: Color yellow). > container extent: 400@400. > container openInWindow. > > Cheers, > Doru > > > -- > www.tudorgirba.com > > "Be rather willing to give than demanding to get." > > > > <ExpanderTweak.1.cs>

Jan. 24, 2011

Re: [Pharo-project] search stack tricks

by Gary Chambers

For me, if nothing else is going on, an Alt-. will get you there... Regards, Gary ----- Original Message ----- From: laurent laffont To: An open mailing list to discuss any topics related to an open-sourceSmalltalk Sent: Sunday, January 23, 2011 8:46 AM Subject: [Pharo-project] search stack tricks Hi, I'm trying to look at http://code.google.com/p/pharo/issues/detail?id=3579 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 ? Cheers, Laurent Laffont (@lolgzs) Pharo Smalltalk Screencasts: http://www.pharocasts.com/ Blog: http://magaloma.blogspot.com/

Jan. 24, 2011

[Pharo-project] Tabs and back button in browser?

by Janko MivÅ¡ek

Hi Pharoers, Are you thinking about introducing tabs and back/forward button, like in web browsers? Just because of web we are now all accustomized and used of tabbed browsing and navigation with a back and forward buttons. This habit now demands all other tools to follow. Tabs are now everywhere, also in Smalltalk. Look at Visualworks, also Dolphin. Introducing tabs soon in Pharo will therefore greatly improve user experience, so if someone would spend some time on it, his contribution will be very valuable! Best regards Janko -- Janko MivÅ¡ek AIDA/Web Smalltalk Web Application Server http://www.aidaweb.si

Jan. 24, 2011

Re: [Pharo-project] collapsing panes

by Gary Chambers

Tricky... Just an experiment, but try the following after filing in attached change set. Can make the re-proportioning explicit and maybe fix things to constrain to the owner morph if interested... | container morph1 morph2 morph3 ex1 ex2 ex3 sp1 sp2| morph1 := (PanelMorph new fillStyle: (SolidFillStyle color: Color red)) hResizing: #spaceFill; vResizing: #spaceFill. morph2 := (PanelMorph new fillStyle: (SolidFillStyle color: Color blue)) hResizing: #spaceFill; vResizing: #spaceFill. morph3 := (PanelMorph new fillStyle: (SolidFillStyle color: Color yellow)) hResizing: #spaceFill; vResizing: #spaceFill. ex1 := (UITheme builder newExpander: 'Red' for: morph1) expanded: true. ex2 := (UITheme builder newExpander: 'Blue' for: morph2) expanded: true. ex3 := (UITheme builder newExpander: 'Yellow' for: morph3) expanded: true. sp1 := EdgeGripMorph new target: ex1; edgeName: #bottom; vResizing: #rigid; extent: 24 @ ProportionalSplitterMorph splitterWidth; on: #mouseDown send: #expandedSizingRigid to: ex1. sp2 := EdgeGripMorph new target: ex2; edgeName: #bottom; vResizing: #rigid; extent: 24 @ ProportionalSplitterMorph splitterWidth; on: #mouseDown send: #expandedSizingRigid to: ex2. container := UITheme builder newColumn: { ex1. sp1. ex2. sp2. ex3}. container cellInset: 0. container extent: 400@400. container openInWindow. Have a play/fun. Regards, Gary ----- Original Message ----- From: "Tudor Girba" <tudor.girba(a)gmail.com> To: "Pharo-project(a)lists.gforge.inria.fr Development" <pharo-project(a)lists.gforge.inria.fr> Sent: Friday, January 21, 2011 11:18 PM Subject: [Pharo-project] collapsing panes Hi, I have a question about how to obtain an effect similar to minimizing a pane in Eclipse. Let's consider the example from below. I have a ProportionalLayout because I want to fill the entire space and be able to resize the inside panes. Now, I would also like to have some way of collapsing one of the panes and have the rest resize to fill the rest of the space. It's a bit like I would need some part of a behavior from the TableLayout. Can anyone provide me with some hints in this direction? Do I need to create a new Layout? | container morph1 morph2 morph3 window | container := PanelMorph new. morph1 := PanelMorph new fillStyle: (SolidFillStyle color: Color red). morph2 := PanelMorph new fillStyle: (SolidFillStyle color: Color blue). morph3 := PanelMorph new fillStyle: (SolidFillStyle color: Color yellow). container changeProportionalLayout. container addMorph: morph1 fullFrame: (LayoutFrame fractions: (0 @ 0 corner: 1 @ 0.33)). container addMorph: morph2 fullFrame: (LayoutFrame fractions: (0 @ 0.33 corner: 1 @ 0.66)). container addMorph: morph3 fullFrame: (LayoutFrame fractions: (0 @ 0.66 corner: 1 @ 1)). container addPaneSplitters. container fillStyle: (SolidFillStyle color: Color yellow). container extent: 400@400. container openInWindow. Cheers, Doru -- www.tudorgirba.com "Be rather willing to give than demanding to get."

Jan. 24, 2011

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

by Guillermo Polito

That's why in my mail I suggested primary, secondary and tertiary for example :). On Mon, Jan 24, 2011 at 10:21 AM, Alexander LazareviÄ <laza(a)blobworks.com>wrote: > 2011/1/24 Guillermo Polito <guillermopolito(a)gmail.com> > >> I hate yellowButtonPressed and redButtonPressed and blueButtonPressed >> messages. >> >> Why not lefClick, rightClick and "middleClick"? >> > > What's with lefties? Is their left button on the right side or on the left > side of the mouse? > What's with five button mice with three regular buttons and one additional > on each side? Are these lefter button and righter button? > > (What's with Wii remote? Is A left or B right or front or back? > So what's with touchpads, Dance Dance revolution pads and bongos?) > > I think left, right, middle ain't better than red, yellow, blue! Actually > it's worse. > > Alex >

Jan. 24, 2011

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

by Guillermo Polito

On Mon, Jan 24, 2011 at 10:22 AM, Nicolas Cellier < nicolas.cellier.aka.nice(a)gmail.com> wrote: > Exactly : logicalRight can be different than physicalRight. > If you tell me this distinction is useless, then I'll ask you to > consider touch screen and other modern input devices. > That's why I ask this community to reformulate and think. > Mmm, maybe we can work in little steps. I think that renaming is a good first step for a refactor. To refactor code you need to understand it, and the colors makes me not to understand it. > > Then you'll can argue at will whether the logical level shall be named > #right #logicalRight or #blue, I don't care. > Then we can change it again. > > For newer kind of events (gestures), we have a more difficult dilemna: > emulate the feel or use native OS facilities... > The question is of same nature as native look. > Even if we choose to rely on OS, we have to think of cross platform > portability and ways to emulate missing capabilities. > In other words, I doubt we can afford the elimination of a level of > indirection. > > Maybe it's time to refactor indeed, but please, bring up your brain > one level above this colour naming battle. > Don't replay battles of the past, turn toward the future. > Oh, that was no my intention. I didn't even know of past battles before this thread. I was only tired of unmeaningful colors. Please, don't turn the discussion like that, I didn't mean that :S. Guille > > Nicolas > > 2011/1/24 Geert Claes <geert.wl.claes(a)gmail.com>: > > > > > > Guillermo Polito wrote: > >> > >> I hate yellowButtonPressed and redButtonPressed and blueButtonPressed > >> messages. > >> > >> Why not lefClick, rightClick and "middleClick"? > >> > > > > I agree that the meaning of the colors is no longer useful, although > "hate" > > is maybe a bit harsh :) > > > > Surely this has already been addressed in other environments? > > http://api.jquery.com/mousedown api.jquery.com/mousedown for example > also > > refers to the left, middle and right button. > > > > Even Apple's multi-touch "magic-mouse" talks about left and right-clicks > > (which is ironic as they have long resisted to even add a second button) > ... > > but also mouse events for the "360Â° scroll", "Screen zoom" and > "two-finger > > swipe". > > -- > > View this message in context: > http://forum.world.st/What-about-a-little-rename-in-MouseEvent-tp3233363p32… > > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > > > > >

Jan. 24, 2011

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

by Nicolas Cellier

Exactly : logicalRight can be different than physicalRight. If you tell me this distinction is useless, then I'll ask you to consider touch screen and other modern input devices. That's why I ask this community to reformulate and think. Then you'll can argue at will whether the logical level shall be named #right #logicalRight or #blue, I don't care. For newer kind of events (gestures), we have a more difficult dilemna: emulate the feel or use native OS facilities... The question is of same nature as native look. Even if we choose to rely on OS, we have to think of cross platform portability and ways to emulate missing capabilities. In other words, I doubt we can afford the elimination of a level of indirection. Maybe it's time to refactor indeed, but please, bring up your brain one level above this colour naming battle. Don't replay battles of the past, turn toward the future. Nicolas 2011/1/24 Geert Claes <geert.wl.claes(a)gmail.com>: > > > Guillermo Polito wrote: >> >> I hate yellowButtonPressed and redButtonPressed and blueButtonPressed >> messages. >> >> Why not lefClick, rightClick and "middleClick"? >> > > I agree that the meaning of the colors is no longer useful, although "hate" > is maybe a bit harsh :) > > Surely this has already been addressed in other environments? > http://api.jquery.com/mousedown api.jquery.com/mousedown Â for example also > refers to the left, middle and right button. > > Even Apple's multi-touch "magic-mouse" talks about left and right-clicks > (which is ironic as they have long resisted to even add a second button) ... > but also mouse events for the "360Â° scroll", "Screen zoom" and "two-finger > swipe". > -- > View this message in context: http://forum.world.st/What-about-a-little-rename-in-MouseEvent-tp3233363p32… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > >

Jan. 24, 2011