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

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

by pharo＠googlecode.com

Comment #8 on issue 3583 by marcus.d...(a)gmail.com: Shout should only be active in code panes http://code.google.com/p/pharo/issues/detail?id=3583 1319

Jan. 26, 2011

Re: [Pharo-project] Issue 3596 in pharo: 2nd part Headless

by pharo＠googlecode.com

Updates: Status: Closed Comment #1 on issue 3596 by marcus.d...(a)gmail.com: 2nd part Headless http://code.google.com/p/pharo/issues/detail?id=3596 13019

Jan. 26, 2011

Re: [Pharo-project] Issue 3590 in pharo: AntiAliased fix

by pharo＠googlecode.com

Updates: Status: Closed Comment #1 on issue 3590 by marcus.d...(a)gmail.com: AntiAliased fix http://code.google.com/p/pharo/issues/detail?id=3590 130019

Jan. 26, 2011

Re: [Pharo-project] Issue 3594 in pharo: Expander needs tweaking to enable resize in a TableLayout

by pharo＠googlecode.com

Comment #5 on issue 3594 by marcus.d...(a)gmail.com: Expander needs tweaking to enable resize in a TableLayout http://code.google.com/p/pharo/issues/detail?id=3594 13019

Jan. 26, 2011

Re: [Pharo-project] Issue 3594 in pharo: Expander needs tweaking to enable resize in a TableLayout

by pharo＠googlecode.com

Updates: Status: Closed Comment #4 on issue 3594 by marcus.d...(a)gmail.com: Expander needs tweaking to enable resize in a TableLayout http://code.google.com/p/pharo/issues/detail?id=3594 (No comment was entered for this change.)

Jan. 26, 2011

[Pharo-project] [update 1.2] #12322

by Marcus Denker

12322 ----- Issue 3583: Shout should only be active in code panes Issue 3594: Expander needs tweaking to enable resize in a TableLayout -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Jan. 26, 2011

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

by pharo＠googlecode.com

Updates: Status: Started Comment #7 on issue 3583 by marcus.d...(a)gmail.com: Shout should only be active in code panes http://code.google.com/p/pharo/issues/detail?id=3583 12322 TODO: 1.3

Jan. 26, 2011

Re: [Pharo-project] Issue 3594 in pharo: Expander needs tweaking to enable resize in a TableLayout

by pharo＠googlecode.com

Updates: Status: Fixed Comment #3 on issue 3594 by marcus.d...(a)gmail.com: Expander needs tweaking to enable resize in a TableLayout http://code.google.com/p/pharo/issues/detail?id=3594 12332 TODO: 1.3

Jan. 26, 2011

[Pharo-project] Issue 3596 in pharo: 2nd part Headless

by pharo＠googlecode.com

Status: Fixed Owner: marcus.d...(a)gmail.com Labels: Milestone-1.3 New issue 3596 by marcus.d...(a)gmail.com: 2nd part Headless http://code.google.com/p/pharo/issues/detail?id=3596 2nd part Headless changes... Attachments: NonInteractiveTools.2.cs 22.2 KB Simulation-Fix.2.cs 2.1 KB

Jan. 26, 2011

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

by Fernando Olivero

Regarding the "looking into the future" i was thinking that we will go the Smalltalk way, by reifying such new events. Instead of "reusing" plain old three button mouse events. And leave the MouseEvent for what they were originally conceived (the proposed renaming ) In this scenario a touch pad would generate a TouchPadEvent, and a multibutton mouse would generate "MultiButtonMouseEvent" Fernando On Tue, Jan 25, 2011 at 10:58 AM, Geert Claes <geert.wl.claes(a)gmail.com> wrote: > > > Lukas Renggli wrote: >> >> ... >> AFAIK, most operating systems number the mouse buttons. >> >> - The primary button is what you use to perform actions (typically left >> mouse button). >> - The secondary buttons is what you use to open context menu (typically >> right mouse button). >> - The third button is the middle button, the fourth button, ... >> >> Now I see that numbers are not that far from colors, but at least they >> have a logical order. I don't like #select, #menu, #extra because I does >> not make sense in any other context (for example games, or touch >> applications) than a traditional GUI. >> > > Agree, on one side there are the physical buttons (button 1, 2, 3 etc) and > on the other hand there are the Â events they trigger. Â e.g. for right-handed > people button 1 would be the primary button where for left-handed this could > very well be button 3. > > Then again, maybe it is time to look a bit further as it looks like the near > future is heading towards a world without any physical buttons where there > is no need to number or name buttons at all :) > > http://www.geek.com/articles/gadgets/new-apple-patent-puts-a-display-on-the… > > Additional gesture events: > http://www.youtube.com/watch?v=JKlkte1aOOw > > -- > 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. 26, 2011