- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Can not make the right mouse button work

by Mariano Martinez Peck

2009/6/18 Hernan Wilkinson <hernan.wilkinson(a)gmail.com> > Something is wrong with the right mouse button... It started to work as > expected after using the image for some time and then it stop working (I had > to press the wheel instead of the right button)... > Does anybody have the same problem? > I just download pharo0.1-10342dev09.06.3 and in my Linux 8.10 is working well out of the box. This is weird. > > 2009/6/18 Mariano Martinez Peck <marianopeck(a)gmail.com> > > See this thread: >> http://n2.nabble.com/swapMouseButtons-doesn%27t-work-td3039209.html#a3039209 >> >> >> 2009/6/17 Hernan Wilkinson <hernan.wilkinson(a)gmail.com> >> >>> I should have said that I'm using Ubuntu...(When I copy the image to a >>> windows system, after some time, yes some time, it started to work...) >>> >>> 2009/6/17 Nicolas Chillo <nchillo(a)gmail.com> >>> >>> Take a look at the VM Mouse Mapping attributes (In windows> right click >>>> in the squeak icon from taskbar). >>>> Activate the 3 Buttons mouse and it should work. >>>> >>>> Nicolas >>>> >>>> >>>> 2009/6/17 Hernan Wilkinson <hernan.wilkinson(a)gmail.com> >>>> >>>>> Hi, in the latest image I can not make the right mouse button >>>>> work.... >>>>> Preferences swapMouseButtons returns false as in the previous image >>>>> that worked... any idea? >>>>> >>>>> Thanks, >>>>> Hernan. >>>>> >>>>> _______________________________________________ >>>>> Pharo-project mailing list >>>>> Pharo-project(a)lists.gforge.inria.fr >>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>>> >>>> >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> Pharo-project(a)lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>> >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 19, 2009

Re: [Pharo-project] BlockContextTest

by Mariano Martinez Peck

2009/6/17 Gabriel Cotelli <g.cotelli(a)gmail.com> > This is the list of methods missing in BlockClosure but covered by the > BlockContextTest: > > - copyStack > - bottomContext > - findContextSuchThat: > - tempNamed: > - tempNamed:put: > > I don't known if has sense to implement that... I have no idea, but in my image (Pharo 10342) I see several senders: * copyStack Process>>copyStack * bottomContext ContextPart>>insertSender: Process>>terminate * findContextSuchThat: BlockContext>>activeHome ContextPart>>buttomContext ContextPart>>findSimilarSender ContextPart>>hasContext: ContextPart>>secondFromButtom Exception>>signalerContext MethodContext>>activeHome MethodContext>>activeOuterContext Process>>calleeOf: * tempNamed: * tempNamed:put: Mariano > > > On Wed, Jun 17, 2009 at 4:28 AM, Adrian Lienhard <adi(a)netstyle.ch> wrote: > >> Hi Gabriel >> >> Could you post a list of these methods? Probably it makes sense to >> copy some of them over to BlockClosure to preserve compatibility for >> external clients (we had this before, e.g., #argumentCount, IIRC which >> is used by GLORP or Seaside). >> >> Else these tests can be removed. >> >> Adrian >> >> On Jun 17, 2009, at 02:28 , Gabriel Cotelli wrote: >> >> > Hi, >> > >> > I'm looking the failing tests... some tests defined in >> > BlockContextTest >> > relies on behavior not implemented in BlockClosure (but implemented >> > in the >> > old BlockContext)... >> > >> > If the only senders of this methods are in this test cases can I >> > remove >> > them? >> > >> > If I don't miss anything BlockContext should not be used anymore... >> > >> > Waiting for your comments... >> > Gabriel >> > _______________________________________________ >> > Pharo-project mailing list >> > Pharo-project(a)lists.gforge.inria.fr >> > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 19, 2009

Re: [Pharo-project] Making pharo more tdd oriented

by Carlos Crosetti

music to my ears.... :) 1) yes, make it a preference 2) concour 3 thru 7) no opinion very thanks -----Mensaje original----- De: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr]En nombre de Hernan Wilkinson Enviado el: Jueves, 18 de Junio de 2009 06:09 p.m. Para: pharo-project(a)lists.gforge.inria.fr Asunto: [Pharo-project] Making pharo more tdd oriented Hi, I have made some changes to pharo to make it more tdd oriented. I want to share them with you to know your opinion and then make the code public. The changes I made are: 1) When there is an error, the debugger opens directly. Reason: I found that I always press Debug when an error occurs in the Notifier window. Question: Should this option be a preference? 2) The debugger opens in a big window. Reason: I always want to debug! and I want to see as much as possible when debugging. Before I found myself making the debugger window bigger all the time 3) When compiling a method that sends a message not defined, it does not ask anymore if I want to change it. Reason: When doing TDD we work top-down, so we are always sending messages that are not defined and that we are going to define when running the test. Question: Should this option be a preference? 4) I added an option to save and run the test from the code pane of the omni browser (ctr+t). If the test fails, opens a debugger to fix it. Reason: It is very handful 5) I added an option to save and step a test from the code pane of the omni browser (ctrl+r). Reason: It is very handful (Problem: The debugger does not work well with breakpoints...) 6) I added a debugCase: message to TestResult and make some changes to the omni browser to show the result of debugging a test. Reason: Before, when debugging a test the browser was showing the test as not runned. 7) When running a test, the defualtAction of the MessageNotUndertood exception will ask you if you want to implement the method (if the receiver is not nil) so you don't have to select that option from the debugger stack list menu. Reason: When running a test 95% of the time a message not understood will be implemented and answering yes or no is easier that going to the stack menu of the debugger to select the option implement. What do you think? Comments welcome. Bye, Hernan.

June 18, 2009

Re: [Pharo-project] Making pharo more tdd oriented

by Schwab,Wilhelm K

David, Re (1), I must respectfully disagrree - Object Arts' experience was much more recent than the 80's, and they have never been shy about keeping up on hardware. They reached a surprisingly rapid and passionate conclusion in favor of the notifier. If you want an option to go straight to the debugger, that's fine by me, just warn me so I can turn it off. Bill ________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of David Mitchell Sent: Thursday, June 18, 2009 5:06 PM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] Making pharo more tdd oriented 1. +1 Direct to debug sounds good to me. Notifier window was for low power (in the 1980s). Don't care if it is a preference. Would prefer fewer preferences, but I can't bring myself to add a preference for it... 2. +1 Big Debugger. 3. -1 I work top-down as well and I still like the typo correction that comes from this step. 4. +1 Wish shortcuts weren't pane specific. 5. ? 6. ? 7. +1 2009/6/18 Hernan Wilkinson <hernan.wilkinson(a)gmail.com<mailto:hernan.wilkinson@gmail.com>> Hi, I have made some changes to pharo to make it more tdd oriented. I want to share them with you to know your opinion and then make the code public. The changes I made are: 1) When there is an error, the debugger opens directly. Reason: I found that I always press Debug when an error occurs in the Notifier window. Question: Should this option be a preference? 2) The debugger opens in a big window. Reason: I always want to debug! and I want to see as much as possible when debugging. Before I found myself making the debugger window bigger all the time 3) When compiling a method that sends a message not defined, it does not ask anymore if I want to change it. Reason: When doing TDD we work top-down, so we are always sending messages that are not defined and that we are going to define when running the test. Question: Should this option be a preference? 4) I added an option to save and run the test from the code pane of the omni browser (ctr+t). If the test fails, opens a debugger to fix it. Reason: It is very handful 5) I added an option to save and step a test from the code pane of the omni browser (ctrl+r). Reason: It is very handful (Problem: The debugger does not work well with breakpoints...) 6) I added a debugCase: message to TestResult and make some changes to the omni browser to show the result of debugging a test. Reason: Before, when debugging a test the browser was showing the test as not runned. 7) When running a test, the defualtAction of the MessageNotUndertood exception will ask you if you want to implement the method (if the receiver is not nil) so you don't have to select that option from the debugger stack list menu. Reason: When running a test 95% of the time a message not understood will be implemented and answering yes or no is easier that going to the stack menu of the debugger to select the option implement. What do you think? Comments welcome. Bye, Hernan. _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr<mailto:Pharo-project@lists.gforge.inria.fr> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

June 18, 2009

Re: [Pharo-project] Making pharo more tdd oriented

by Schwab,Wilhelm K

Hernan, (1) going straight to a debugger is a really bad idea. Object Arts tried it, and promptly spoke out against it. If you want the option to skip the notifier, fine, but I want to the option to keep the buffer of the notifier. Imagine a recursive meltdown, and then make it an order of magnitude or two worse because every mention of the problem is a full debugger instead of a notifier. You've been warned :) (2) +1, maybe 2 (3) +3 :) Those prompts are seriously annoying. I even have places in my code that look like uninitializeTemp := uninitializeTemp. just to gag the "is it ok to remove xyz". It arises when I capture something in a temp knowing that I will need it later but have not coded that far yet. Not quite TTD, but not all that different. (4-5) options are generally good things. (6) Is there any impact on performance? OB is too slow as it is. Otherwise it's probably fine. (7) I'm not a big fan of the default action concept, but this is probably a good use. That said, I would probably not want to use it, and would ask that you make it optional. From a system stability standpoint, I am a little nervous about having an error invoke the GUI, especially if the tests make use of #fork: etc. Bill ________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Hernan Wilkinson Sent: Thursday, June 18, 2009 4:09 PM To: pharo-project(a)lists.gforge.inria.fr Subject: [Pharo-project] Making pharo more tdd oriented Hi, I have made some changes to pharo to make it more tdd oriented. I want to share them with you to know your opinion and then make the code public. The changes I made are: 1) When there is an error, the debugger opens directly. Reason: I found that I always press Debug when an error occurs in the Notifier window. Question: Should this option be a preference? 2) The debugger opens in a big window. Reason: I always want to debug! and I want to see as much as possible when debugging. Before I found myself making the debugger window bigger all the time 3) When compiling a method that sends a message not defined, it does not ask anymore if I want to change it. Reason: When doing TDD we work top-down, so we are always sending messages that are not defined and that we are going to define when running the test. Question: Should this option be a preference? 4) I added an option to save and run the test from the code pane of the omni browser (ctr+t). If the test fails, opens a debugger to fix it. Reason: It is very handful 5) I added an option to save and step a test from the code pane of the omni browser (ctrl+r). Reason: It is very handful (Problem: The debugger does not work well with breakpoints...) 6) I added a debugCase: message to TestResult and make some changes to the omni browser to show the result of debugging a test. Reason: Before, when debugging a test the browser was showing the test as not runned. 7) When running a test, the defualtAction of the MessageNotUndertood exception will ask you if you want to implement the method (if the receiver is not nil) so you don't have to select that option from the debugger stack list menu. Reason: When running a test 95% of the time a message not understood will be implemented and answering yes or no is easier that going to the stack menu of the debugger to select the option implement. What do you think? Comments welcome. Bye, Hernan.

June 18, 2009

Re: [Pharo-project] Making pharo more tdd oriented

by David Mitchell

1. +1 Direct to debug sounds good to me. Notifier window was for low power (in the 1980s). Don't care if it is a preference. Would prefer fewer preferences, but I can't bring myself to add a preference for it... 2. +1 Big Debugger. 3. -1 I work top-down as well and I still like the typo correction that comes from this step. 4. +1 Wish shortcuts weren't pane specific. 5. ? 6. ? 7. +1 2009/6/18 Hernan Wilkinson <hernan.wilkinson(a)gmail.com> > Hi, > I have made some changes to pharo to make it more tdd oriented. I want to > share them with you to know your opinion and then make the code public. > The changes I made are: > > 1) When there is an error, the debugger opens directly. Reason: I found > that I always press Debug when an error occurs in the Notifier window. > Question: Should this option be a preference? > 2) The debugger opens in a big window. Reason: I always want to debug! and > I want to see as much as possible when debugging. Before I found myself > making the debugger window bigger all the time > 3) When compiling a method that sends a message not defined, it does not > ask anymore if I want to change it. Reason: When doing TDD we work top-down, > so we are always sending messages that are not defined and that we are going > to define when running the test. Question: Should this option be a > preference? > 4) I added an option to save and run the test from the code pane of the > omni browser (ctr+t). If the test fails, opens a debugger to fix it. Reason: > It is very handful > 5) I added an option to save and step a test from the code pane of the omni > browser (ctrl+r). Reason: It is very handful (Problem: The debugger does not > work well with breakpoints...) > 6) I added a debugCase: message to TestResult and make some changes to the > omni browser to show the result of debugging a test. Reason: Before, when > debugging a test the browser was showing the test as not runned. > 7) When running a test, the defualtAction of the MessageNotUndertood > exception will ask you if you want to implement the method (if the receiver > is not nil) so you don't have to select that option from the debugger stack > list menu. Reason: When running a test 95% of the time a message not > understood will be implemented and answering yes or no is easier that going > to the stack menu of the debugger to select the option implement. > > What do you think? Comments welcome. > Bye, > Hernan. > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 18, 2009

Re: [Pharo-project] Can not make the right mouse button work

by Hernan Wilkinson

Something is wrong with the right mouse button... It started to work as expected after using the image for some time and then it stop working (I had to press the wheel instead of the right button)... Does anybody have the same problem? 2009/6/18 Mariano Martinez Peck <marianopeck(a)gmail.com> > See this thread: > http://n2.nabble.com/swapMouseButtons-doesn%27t-work-td3039209.html#a3039209 > > > 2009/6/17 Hernan Wilkinson <hernan.wilkinson(a)gmail.com> > >> I should have said that I'm using Ubuntu...(When I copy the image to a >> windows system, after some time, yes some time, it started to work...) >> >> 2009/6/17 Nicolas Chillo <nchillo(a)gmail.com> >> >> Take a look at the VM Mouse Mapping attributes (In windows> right click in >>> the squeak icon from taskbar). >>> Activate the 3 Buttons mouse and it should work. >>> >>> Nicolas >>> >>> >>> 2009/6/17 Hernan Wilkinson <hernan.wilkinson(a)gmail.com> >>> >>>> Hi, in the latest image I can not make the right mouse button work.... >>>> Preferences swapMouseButtons returns false as in the previous image >>>> that worked... any idea? >>>> >>>> Thanks, >>>> Hernan. >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> Pharo-project(a)lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>> >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 18, 2009

[Pharo-project] Making pharo more tdd oriented

by Hernan Wilkinson

Hi, I have made some changes to pharo to make it more tdd oriented. I want to share them with you to know your opinion and then make the code public. The changes I made are: 1) When there is an error, the debugger opens directly. Reason: I found that I always press Debug when an error occurs in the Notifier window. Question: Should this option be a preference? 2) The debugger opens in a big window. Reason: I always want to debug! and I want to see as much as possible when debugging. Before I found myself making the debugger window bigger all the time 3) When compiling a method that sends a message not defined, it does not ask anymore if I want to change it. Reason: When doing TDD we work top-down, so we are always sending messages that are not defined and that we are going to define when running the test. Question: Should this option be a preference? 4) I added an option to save and run the test from the code pane of the omni browser (ctr+t). If the test fails, opens a debugger to fix it. Reason: It is very handful 5) I added an option to save and step a test from the code pane of the omni browser (ctrl+r). Reason: It is very handful (Problem: The debugger does not work well with breakpoints...) 6) I added a debugCase: message to TestResult and make some changes to the omni browser to show the result of debugging a test. Reason: Before, when debugging a test the browser was showing the test as not runned. 7) When running a test, the defualtAction of the MessageNotUndertood exception will ask you if you want to implement the method (if the receiver is not nil) so you don't have to select that option from the debugger stack list menu. Reason: When running a test 95% of the time a message not understood will be implemented and answering yes or no is easier that going to the stack menu of the debugger to select the option implement. What do you think? Comments welcome. Bye, Hernan.

June 18, 2009

[Pharo-project] NewInspector

by Alexandre Bergel

Hi! When I right-click in the workspace panel of a newinspector I get a rollback 'The getMenuSelector must be a 1- or 2-keyword symbol' Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

June 18, 2009

Re: [Pharo-project] Automatic/periodic image saves

by Schwab,Wilhelm K

John, Which OS are you using? How long has it been up? I am *very* interested in your experience with it, because I am starting to take a similar path; **please** keep us posted on performance/reliability. Nice work, and good luck with it! Bill -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of John Thornborrow Sent: Wednesday, June 17, 2009 5:12 AM To: Pharo Development Subject: [Pharo-project] Automatic/periodic image saves Hi, We've deployed a Pharo+Pier/Seaside image for our website, and (naturally) changes are made to the site via Pier. I'd like to know if there is a preferred method of saving the image to disk every, say, 12 hours? Many thanks, John. www.pinesoft.co.uk

June 18, 2009