December 2008 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Notifiers

by Bill Schwab

That would be better than the current situation, but, among other questions I'm probably not going to think of, it might be easy to decide how many debuggers are open when the error occurs, but how many are trying to open? Maybe a shared queue would suffice. Anyway, I get a vote, and it's in favor of notifiers; if there is further a preference to skip that step, that's fine by me. Bill Wilhelm K. Schwab, Ph.D. University of Florida Department of Anesthesiology PO Box 100254 Gainesville, FL 32610-0254 Email: bschwab(a)anest.ufl.edu Tel: (352) 273-6785 FAX: (352) 392-7029 >>> pennell.david(a)gmail.com 12/20/08 4:52 PM >>> So only open one and recognize eecursive UHE and do something clever. Opening an infinite # of any kind of window sucks. -david On Dec 20, 2008, at 2:58 PM, "Bill Schwab" <BSchwab(a)anest.ufl.edu> wrote: > Stef, > > Under ordinary circumstances, it's ok, but OA tried this and then > quickly decided it was a bad idea. Imagine a budding recursive > chain of > errors; the extra load of opening the debugger can prevent a rescue > that > might be possible given a lightweight notifier. > > Bill > > > > > > Wilhelm K. Schwab, Ph.D. > University of Florida > Department of Anesthesiology > PO Box 100254 > Gainesville, FL 32610-0254 > > Email: bschwab(a)anest.ufl.edu > Tel: (352) 273-6785 > FAX: (352) 392-7029 > >>>> stephane.ducasse(a)inria.fr 12/20/08 2:37 PM >>> > ahh now I understand because I'm often working on pharo core and I > could not really understand > what was the problem. > > Now indeed what is wrong with getting just the debugger? assuming the > same error is raised? > stef > On Dec 20, 2008, at 6:51 PM, Lukas Renggli wrote: > >> On Sat, Dec 20, 2008 at 6:45 PM, Adrian Lienhard <adi(a)netstyle.ch> >> wrote: >>> I don't quite understand. When I do "1 foo" I get a notifier window >>> (the small one) and not the full debugger. >> >> I guess Bill is using the Dev-Image of Damien with OB-Tools loaded. >> >> Lukas >> >> -- >> Lukas Renggli >> http://www.lukas-renggli.ch >> >> _______________________________________________ >> 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

Dec. 20, 2008

Re: [Pharo-project] Notifiers

by David Pennell

So only open one and recognize eecursive UHE and do something clever. Opening an infinite # of any kind of window sucks. -david On Dec 20, 2008, at 2:58 PM, "Bill Schwab" <BSchwab(a)anest.ufl.edu> wrote: > Stef, > > Under ordinary circumstances, it's ok, but OA tried this and then > quickly decided it was a bad idea. Imagine a budding recursive > chain of > errors; the extra load of opening the debugger can prevent a rescue > that > might be possible given a lightweight notifier. > > Bill > > > > > > Wilhelm K. Schwab, Ph.D. > University of Florida > Department of Anesthesiology > PO Box 100254 > Gainesville, FL 32610-0254 > > Email: bschwab(a)anest.ufl.edu > Tel: (352) 273-6785 > FAX: (352) 392-7029 > >>>> stephane.ducasse(a)inria.fr 12/20/08 2:37 PM >>> > ahh now I understand because I'm often working on pharo core and I > could not really understand > what was the problem. > > Now indeed what is wrong with getting just the debugger? assuming the > same error is raised? > stef > On Dec 20, 2008, at 6:51 PM, Lukas Renggli wrote: > >> On Sat, Dec 20, 2008 at 6:45 PM, Adrian Lienhard <adi(a)netstyle.ch> >> wrote: >>> I don't quite understand. When I do "1 foo" I get a notifier window >>> (the small one) and not the full debugger. >> >> I guess Bill is using the Dev-Image of Damien with OB-Tools loaded. >> >> Lukas >> >> -- >> Lukas Renggli >> http://www.lukas-renggli.ch >> >> _______________________________________________ >> 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

Dec. 20, 2008

Re: [Pharo-project] Notifiers

by Michael Roberts

you could have some logic that the first one opened the debugger but subsequent ones open a notifier if a debugger is already open.... Mike On Sat, Dec 20, 2008 at 8:58 PM, Bill Schwab <BSchwab(a)anest.ufl.edu> wrote: > Stef, > > Under ordinary circumstances, it's ok, but OA tried this and then > quickly decided it was a bad idea. Imagine a budding recursive chain of > errors; the extra load of opening the debugger can prevent a rescue that > might be possible given a lightweight notifier. > > Bill > > > > > > Wilhelm K. Schwab, Ph.D. > University of Florida > Department of Anesthesiology > PO Box 100254 > Gainesville, FL 32610-0254 > > Email: bschwab(a)anest.ufl.edu > Tel: (352) 273-6785 > FAX: (352) 392-7029 > >>>> stephane.ducasse(a)inria.fr 12/20/08 2:37 PM >>> > ahh now I understand because I'm often working on pharo core and I > could not really understand > what was the problem. > > Now indeed what is wrong with getting just the debugger? assuming the > same error is raised? > stef > On Dec 20, 2008, at 6:51 PM, Lukas Renggli wrote: > >> On Sat, Dec 20, 2008 at 6:45 PM, Adrian Lienhard <adi(a)netstyle.ch> >> wrote: >>> I don't quite understand. When I do "1 foo" I get a notifier window >>> (the small one) and not the full debugger. >> >> I guess Bill is using the Dev-Image of Damien with OB-Tools loaded. >> >> Lukas >> >> -- >> Lukas Renggli >> http://www.lukas-renggli.ch >> >> _______________________________________________ >> 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 >

Dec. 20, 2008

Re: [Pharo-project] Mac VM arguments access problem

by StÃ©phane Ducasse

tx I was not aware of that. On Dec 20, 2008, at 9:43 PM, Keith Hodges wrote: > StÃ©phane Ducasse wrote: >> Hi john >> >> Gwenael told that: >> >> SystemImage current getSystemAttribute: 1 >> returns well the image name >> >> SystemImage current getSystemAttribute: 2 >> does not return the other arguments passed >> >> Apparently this is working under linux. >> >> Then apparently when he launches the vm from the command line >> he cannot click but the mouse scrolling works. >> >> I asked to send a report but he is away. So sorry for the fuzzyness >> of >> my report. >> I prefer to report is than to forget. He will complement it if you >> need more info >> >> Stef >> > The Mac vm did have problems like this when accessed via a symbolic > link > > Keith > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Dec. 20, 2008

Re: [Pharo-project] Mac VM arguments access problem

by StÃ©phane Ducasse

Tx john I asked gwenael to reply. Stef On Dec 20, 2008, at 10:12 PM, John McIntosh wrote: > Yes if you link to the binary directly it cann't figure out where the > info.plist is to load the mouse click mapping The vmparm issue was > looked at earler this year and a change was done so which Vm is this > On 12/20/08, Keith Hodges <keith_hodges(a)yahoo.co.uk> wrote: >> StÃ©phane Ducasse wrote: >>> Hi john >>> >>> Gwenael told that: >>> >>> SystemImage current getSystemAttribute: 1 >>> returns well the image name >>> >>> SystemImage current getSystemAttribute: 2 >>> does not return the other arguments passed >>> >>> Apparently this is working under linux. >>> >>> Then apparently when he launches the vm from the command line >>> he cannot click but the mouse scrolling works. >>> >>> I asked to send a report but he is away. So sorry for the >>> fuzzyness of >>> my report. >>> I prefer to report is than to forget. He will complement it if you >>> need more info >>> >>> Stef >>> >> The Mac vm did have problems like this when accessed via a symbolic >> link >> >> Keith >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > -- > = > = > = > = > = > ====================================================================== > John M. McIntosh <johnmci(a)smalltalkconsulting.com> > Corporate Smalltalk Consulting Ltd. http:// > www.smalltalkconsulting.com > = > = > = > = > = > ====================================================================== > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Dec. 20, 2008

Re: [Pharo-project] Mac VM arguments access problem

by John McIntosh

Yes if you link to the binary directly it cann't figure out where the info.plist is to load the mouse click mapping The vmparm issue was looked at earler this year and a change was done so which Vm is this On 12/20/08, Keith Hodges <keith_hodges(a)yahoo.co.uk> wrote: > StÃ©phane Ducasse wrote: >> Hi john >> >> Gwenael told that: >> >> SystemImage current getSystemAttribute: 1 >> returns well the image name >> >> SystemImage current getSystemAttribute: 2 >> does not return the other arguments passed >> >> Apparently this is working under linux. >> >> Then apparently when he launches the vm from the command line >> he cannot click but the mouse scrolling works. >> >> I asked to send a report but he is away. So sorry for the fuzzyness of >> my report. >> I prefer to report is than to forget. He will complement it if you >> need more info >> >> Stef >> > The Mac vm did have problems like this when accessed via a symbolic link > > Keith > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- =========================================================================== John M. McIntosh <johnmci(a)smalltalkconsulting.com> Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com ===========================================================================

Dec. 20, 2008

Re: [Pharo-project] knowing all the class using a trait?

by Adrian Lienhard

I don't know if this is in the GUI, but you can just send #users to a trait. TPureBehavior users --> an IdentitySet(TraitBehavior Behavior) Adrian On Dec 20, 2008, at 21:17 , StÃ©phane Ducasse wrote: > Hi david > > is there a way to know the classes that use a given trait? > > Stef > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Dec. 20, 2008

Re: [Pharo-project] Notifiers

by Bill Schwab

Stef, Under ordinary circumstances, it's ok, but OA tried this and then quickly decided it was a bad idea. Imagine a budding recursive chain of errors; the extra load of opening the debugger can prevent a rescue that might be possible given a lightweight notifier. Bill Wilhelm K. Schwab, Ph.D. University of Florida Department of Anesthesiology PO Box 100254 Gainesville, FL 32610-0254 Email: bschwab(a)anest.ufl.edu Tel: (352) 273-6785 FAX: (352) 392-7029 >>> stephane.ducasse(a)inria.fr 12/20/08 2:37 PM >>> ahh now I understand because I'm often working on pharo core and I could not really understand what was the problem. Now indeed what is wrong with getting just the debugger? assuming the same error is raised? stef On Dec 20, 2008, at 6:51 PM, Lukas Renggli wrote: > On Sat, Dec 20, 2008 at 6:45 PM, Adrian Lienhard <adi(a)netstyle.ch> > wrote: >> I don't quite understand. When I do "1 foo" I get a notifier window >> (the small one) and not the full debugger. > > I guess Bill is using the Dev-Image of Damien with OB-Tools loaded. > > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > _______________________________________________ > 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

Dec. 20, 2008

Re: [Pharo-project] Mac VM arguments access problem

by Keith Hodges

StÃ©phane Ducasse wrote: > Hi john > > Gwenael told that: > > SystemImage current getSystemAttribute: 1 > returns well the image name > > SystemImage current getSystemAttribute: 2 > does not return the other arguments passed > > Apparently this is working under linux. > > Then apparently when he launches the vm from the command line > he cannot click but the mouse scrolling works. > > I asked to send a report but he is away. So sorry for the fuzzyness of > my report. > I prefer to report is than to forget. He will complement it if you > need more info > > Stef > The Mac vm did have problems like this when accessed via a symbolic link Keith

Dec. 20, 2008

[Pharo-project] Mac VM arguments access problem

by StÃ©phane Ducasse

Hi john Gwenael told that: SystemImage current getSystemAttribute: 1 returns well the image name SystemImage current getSystemAttribute: 2 does not return the other arguments passed Apparently this is working under linux. Then apparently when he launches the vm from the command line he cannot click but the mouse scrolling works. I asked to send a report but he is away. So sorry for the fuzzyness of my report. I prefer to report is than to forget. He will complement it if you need more info Stef

Dec. 20, 2008