- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Issue 2768 in pharo: FFT >> #transformForward: now uses FFTPlugin

by pharo＠googlecode.com

Updates: Status: Closed Comment #2 on issue 2768 by ryd...(a)gmail.com: FFT >> #transformForward: now uses FFTPlugin http://code.google.com/p/pharo/issues/detail?id=2768 In PharoSound.49

Jan. 24, 2011

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

by Geert Claes

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] Issue 3058 in pharo: Sound postCopy

by pharo＠googlecode.com

Updates: Status: Closed Comment #4 on issue 3058 by ryd...(a)gmail.com: Sound postCopy http://code.google.com/p/pharo/issues/detail?id=3058 PharoSound package includes these changes, that's where Nicolas took them from I presume, as they predate the squeak update by a month.

Jan. 24, 2011

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

by HernÃ¡n Morales Durand

2011/1/24 HernÃ¡n Morales Durand <hernan.morales(a)gmail.com>: > 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 >> > > " The original device connected to the Alto and Dorado machines had 3 > buttons labelled "yellow", "red" and "blue" " > From http://www.cosc.canterbury.ac.nz/wolfgang.kreutzer/cosc205/smalltalk1.html > BTW I guess colors were choosen by someone with background in color psychology, there are *a lot* studies about color symbolism. HernÃ¡n

Jan. 24, 2011

Re: [Pharo-project] Issue 3196 in pharo: Sound should be check to see if it uses pragma or not

by pharo＠googlecode.com

Updates: Status: Closed Comment #2 on issue 3196 by ryd...(a)gmail.com: Sound should be check to see if it uses pragma or not http://code.google.com/p/pharo/issues/detail?id=3196 The PharoSound package includes the change to use pragmas.

Jan. 24, 2011

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

by HernÃ¡n Morales Durand

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 > " The original device connected to the Alto and Dorado machines had 3 buttons labelled "yellow", "red" and "blue" " >From http://www.cosc.canterbury.ac.nz/wolfgang.kreutzer/cosc205/smalltalk1.html > > > > -- > Marcus Denker Â --Â http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. >

Jan. 24, 2011

[Pharo-project] [update 1.3] #13017

by Marcus Denker

13017 ----- Issue 3580: Some trivial code-critique cleanups Issue 3582: RecentMessageList should be reseted in #cleanUpForRelease -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Jan. 24, 2011

Re: [Pharo-project] Issue 3582 in pharo: RecentMessageList should be reseted in #cleanUpForRelease

by pharo＠googlecode.com

Updates: Status: Closed Comment #2 on issue 3582 by marcus.d...(a)gmail.com: RecentMessageList should be reseted in #cleanUpForRelease http://code.google.com/p/pharo/issues/detail?id=3582 13017

Jan. 24, 2011

Re: [Pharo-project] Issue 3580 in pharo: Some trivial code-critique cleanups

by pharo＠googlecode.com

Updates: Status: Closed Comment #1 on issue 3580 by marcus.d...(a)gmail.com: Some trivial code-critique cleanups http://code.google.com/p/pharo/issues/detail?id=3580 13017

Jan. 24, 2011

Re: [Pharo-project] Cant load NBOpenGL

by Igor Stasenko

On 24 January 2011 12:26, Fernando Olivero <fernando.olivero(a)usi.ch> wrote: > Igor, excelent that you made a Native Boost vm available for MacOSX. > I would like to try out your text rendering demos. > Yes, VM is ready for use.. but image side code are not still adopted for MacOS. Mac OS using a stack alignment (16 bytes), and if you not aligning the stack when doing external calls, it leads to exception(s) & crash. In other platforms there is no any restriction about stack alignment, and obviously that's why i was not care about it in code generator. Now i need to rewrite a code generation code to take this into account. This complicates things a little, and will slow down the callout code on macs , but i hope not really too much. So, until then , nativeboost for doing external calls on Macs is not ready for use. > But i have a problem while trying to load the NBOpenGL in the order > specified in squeaksource. > > > NBOpenGL-Win > > This package depends on the following classes: > Â NBWinTypes > Â NBWinConstants > So, this is a platform-specific (Windows) part of NBOpenGL, and no wonder, it requires a platform-specific NativeBoost package specifically for windows. In same way, there will be NBOpenGL-Mac (or most probably NBOpenGL-Unix) which will implement platform-specific parts needed for using OpenGL on it. > > Fernando > > -- Best regards, Igor Stasenko AKA sig.

Jan. 24, 2011