February 2009 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Automatic focus on column upon moose enter

by David RÃ¶thlisberger

Hi > First of all, I did not authored this change. David did it. I guess > this was a request emanated by a bunch of people. Yes. > Personally, the only reason why I am happy with the auto-focus, is by > pressing Cmd-T to run tests. I find this quite convenient to simply > accept a method, then move the moose to the column and press Cmd-T, > without clicking. yes. Another scenario from Stef: Having a method selected in the method list, going with the mouse button to the first column while having selected the hierarchy button and press key up or down to conveniently browse the same method in super- or subclasses. > Although I do not see a scenario where auto-focus is > a real problem, I do understand that David made an arbitrary decision > without much consultation. Sorry about that. So, what do we do? Well, I did some "consultation" with Gary and Stef. But they left the decision to me, so I "decided" to be it like that for the moment to see how people react. I don't mind to, as Gary suggested, introduce yet another preference (there are already two related to this "auto-focus") saying whether one wants to ignore the mouseClickForKeyboardFocus preference in the browser's columns, although I personally think that such a preference is not needed as I can't imagine that this auto-focus for columns gets into the way too often (if at all). But if people want me to add such a pref, fine by me. I don't think we want to start a much ado about nothing discussion about this small change. ;) David > On 20 Feb 2009, at 14:38, Schwab,Wilhelm K wrote: > >> Alexandre, >> >> Can you give us an explanation or pointer to one? This sounds like >> something that Gary worked hard to stop from happening. I want you >> to have what you want from your image, and I need my future users to >> have what they will demand (loudly<g>). I am also convinced that >> there are things (e.g. mouse wheel input) that should "follow the >> mouse" without affecting keyboard focus, and this might be one of >> them, but referring to focus gives me the idea that keyboard input >> will go to the columns based on mouse position, and that >> (PLEASE!!!!!) needs to be optional - it drives me batty. I type >> quite fast, and if the input goes to what amount to commands instead >> of editing, it can get ugly. >> >> There are some preferences that control behavior like this, and any >> such overrides should be conditional on one being set, or moved into >> the themes, probably as an aspect vs. implied by the theme choice. >> By the latter, I am assuming that you want Motif style mouse/focus >> behavior in any old theme you happen to choose. That's fine, but it >> should be optional or we are taking a step backward in feel. >> >> Bill >> >> >> ---- >> Wilhelm K. Schwab, Ph.D. >> bschwab AT anest DOT ufl DOT edu >> >> ________________________________________ >> From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr >> ] On Behalf Of Alexandre Bergel [Alexandre.Bergel(a)inria.fr] >> Sent: Friday, February 20, 2009 5:04 AM >> To: Pharo Development >> Subject: [Pharo-project] Automatic focus on column upon moose enter >> >> David, >> You're a hero! >> Thanks for OB-Enhancements-dr.305 >> >> Alexandre >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> >> >> _______________________________________________ >> 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 >> >

Feb. 20, 2009

Re: [Pharo-project] Automatic focus on column upon moose enter

by Marcus Denker

On 20.02.2009, at 15:11, Alexandre Bergel wrote: > I do not know what is mouseClickForKeyboardFocus > I just feel that when putting the moose over a column, in which an > item is selected, and pressing a shortcut for a command should execute > the OB command. Am I missing something obvious? > Would the selected textfield then loose the focus? That would be a bot annoying... (as "mouseClickFor.." exactly specifies that the focus only changes when you click). Marcus > Cheers, > Alexandre > > > On 20 Feb 2009, at 15:05, Gary Chambers wrote: > >> I've asked David if he would preference it... >> >> As for the mouse wheel, that does follow the mouse pointer so I was >> confused >> as to why anyone would want the keyboard focus to follow the mouse >> for OB >> columns irrespective of the mouseClickForKeyboardFocus preference. >> Each to >> their own (hence preference required). >> >> Regards, Gary >> >> ----- Original Message ----- >> From: "Schwab,Wilhelm K" <bschwab(a)anest.ufl.edu> >> To: <Pharo-project(a)lists.gforge.inria.fr> >> Sent: Friday, February 20, 2009 1:38 PM >> Subject: Re: [Pharo-project] Automatic focus on column upon moose >> enter >> >> >>> Alexandre, >>> >>> Can you give us an explanation or pointer to one? This sounds like >>> something that Gary worked hard to stop from happening. I want you >>> to >>> have what you want from your image, and I need my future users to >>> have >>> what they will demand (loudly<g>). I am also convinced that there >>> are >>> things (e.g. mouse wheel input) that should "follow the mouse" >>> without >>> affecting keyboard focus, and this might be one of them, but >>> referring to >>> focus gives me the idea that keyboard input will go to the columns >>> based >>> on mouse position, and that (PLEASE!!!!!) needs to be optional - it >>> drives >>> me batty. I type quite fast, and if the input goes to what amount >>> to >>> commands instead of editing, it can get ugly. >>> >>> There are some preferences that control behavior like this, and any >>> such >>> overrides should be conditional on one being set, or moved into the >>> themes, probably as an aspect vs. implied by the theme choice. By >>> the >>> latter, I am assuming that you want Motif style mouse/focus >>> behavior in >>> any old theme you happen to choose. That's fine, but it should be >>> optional or we are taking a step backward in feel. >>> >>> Bill >>> >>> >>> ---- >>> Wilhelm K. Schwab, Ph.D. >>> bschwab AT anest DOT ufl DOT edu >>> >>> ________________________________________ >>> From: pharo-project-bounces(a)lists.gforge.inria.fr >>> [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Alexandre >>> Bergel [Alexandre.Bergel(a)inria.fr] >>> Sent: Friday, February 20, 2009 5:04 AM >>> To: Pharo Development >>> Subject: [Pharo-project] Automatic focus on column upon moose enter >>> >>> David, >>> You're a hero! >>> Thanks for OB-Enhancements-dr.305 >>> >>> Alexandre >>> -- >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> Alexandre Bergel http://www.bergel.eu >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >>> >>> >>> >>> >>> _______________________________________________ >>> 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 >> > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Marcus Denker -- denker(a)acm.org http://www.marcusdenker.de

Feb. 20, 2009

Re: [Pharo-project] Automatic focus on column upon moose enter

by Alexandre Bergel

I do not know what is mouseClickForKeyboardFocus I just feel that when putting the moose over a column, in which an item is selected, and pressing a shortcut for a command should execute the OB command. Am I missing something obvious? Cheers, Alexandre On 20 Feb 2009, at 15:05, Gary Chambers wrote: > I've asked David if he would preference it... > > As for the mouse wheel, that does follow the mouse pointer so I was > confused > as to why anyone would want the keyboard focus to follow the mouse > for OB > columns irrespective of the mouseClickForKeyboardFocus preference. > Each to > their own (hence preference required). > > Regards, Gary > > ----- Original Message ----- > From: "Schwab,Wilhelm K" <bschwab(a)anest.ufl.edu> > To: <Pharo-project(a)lists.gforge.inria.fr> > Sent: Friday, February 20, 2009 1:38 PM > Subject: Re: [Pharo-project] Automatic focus on column upon moose > enter > > >> Alexandre, >> >> Can you give us an explanation or pointer to one? This sounds like >> something that Gary worked hard to stop from happening. I want you >> to >> have what you want from your image, and I need my future users to >> have >> what they will demand (loudly<g>). I am also convinced that there >> are >> things (e.g. mouse wheel input) that should "follow the mouse" >> without >> affecting keyboard focus, and this might be one of them, but >> referring to >> focus gives me the idea that keyboard input will go to the columns >> based >> on mouse position, and that (PLEASE!!!!!) needs to be optional - it >> drives >> me batty. I type quite fast, and if the input goes to what amount to >> commands instead of editing, it can get ugly. >> >> There are some preferences that control behavior like this, and any >> such >> overrides should be conditional on one being set, or moved into the >> themes, probably as an aspect vs. implied by the theme choice. By >> the >> latter, I am assuming that you want Motif style mouse/focus >> behavior in >> any old theme you happen to choose. That's fine, but it should be >> optional or we are taking a step backward in feel. >> >> Bill >> >> >> ---- >> Wilhelm K. Schwab, Ph.D. >> bschwab AT anest DOT ufl DOT edu >> >> ________________________________________ >> From: pharo-project-bounces(a)lists.gforge.inria.fr >> [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Alexandre >> Bergel [Alexandre.Bergel(a)inria.fr] >> Sent: Friday, February 20, 2009 5:04 AM >> To: Pharo Development >> Subject: [Pharo-project] Automatic focus on column upon moose enter >> >> David, >> You're a hero! >> Thanks for OB-Enhancements-dr.305 >> >> Alexandre >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> >> >> _______________________________________________ >> 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 > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Feb. 20, 2009

Re: [Pharo-project] Automatic focus on column upon moose enter

by Gary Chambers

I've asked David if he would preference it... As for the mouse wheel, that does follow the mouse pointer so I was confused as to why anyone would want the keyboard focus to follow the mouse for OB columns irrespective of the mouseClickForKeyboardFocus preference. Each to their own (hence preference required). Regards, Gary ----- Original Message ----- From: "Schwab,Wilhelm K" <bschwab(a)anest.ufl.edu> To: <Pharo-project(a)lists.gforge.inria.fr> Sent: Friday, February 20, 2009 1:38 PM Subject: Re: [Pharo-project] Automatic focus on column upon moose enter > Alexandre, > > Can you give us an explanation or pointer to one? This sounds like > something that Gary worked hard to stop from happening. I want you to > have what you want from your image, and I need my future users to have > what they will demand (loudly<g>). I am also convinced that there are > things (e.g. mouse wheel input) that should "follow the mouse" without > affecting keyboard focus, and this might be one of them, but referring to > focus gives me the idea that keyboard input will go to the columns based > on mouse position, and that (PLEASE!!!!!) needs to be optional - it drives > me batty. I type quite fast, and if the input goes to what amount to > commands instead of editing, it can get ugly. > > There are some preferences that control behavior like this, and any such > overrides should be conditional on one being set, or moved into the > themes, probably as an aspect vs. implied by the theme choice. By the > latter, I am assuming that you want Motif style mouse/focus behavior in > any old theme you happen to choose. That's fine, but it should be > optional or we are taking a step backward in feel. > > Bill > > > ---- > Wilhelm K. Schwab, Ph.D. > bschwab AT anest DOT ufl DOT edu > > ________________________________________ > From: pharo-project-bounces(a)lists.gforge.inria.fr > [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Alexandre > Bergel [Alexandre.Bergel(a)inria.fr] > Sent: Friday, February 20, 2009 5:04 AM > To: Pharo Development > Subject: [Pharo-project] Automatic focus on column upon moose enter > > David, > You're a hero! > Thanks for OB-Enhancements-dr.305 > > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > 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

Feb. 20, 2009

Re: [Pharo-project] Automatic focus on column upon moose enter

by Alexandre Bergel

I think we should have a protocol on how to solve this kind of conflicting position. We could vote maybe... I do not ming to have this behavior as optional, but I would like it to be set by default :-) Alexandre On 20 Feb 2009, at 14:38, Schwab,Wilhelm K wrote: > Alexandre, > > Can you give us an explanation or pointer to one? This sounds like > something that Gary worked hard to stop from happening. I want you > to have what you want from your image, and I need my future users to > have what they will demand (loudly<g>). I am also convinced that > there are things (e.g. mouse wheel input) that should "follow the > mouse" without affecting keyboard focus, and this might be one of > them, but referring to focus gives me the idea that keyboard input > will go to the columns based on mouse position, and that > (PLEASE!!!!!) needs to be optional - it drives me batty. I type > quite fast, and if the input goes to what amount to commands instead > of editing, it can get ugly. > > There are some preferences that control behavior like this, and any > such overrides should be conditional on one being set, or moved into > the themes, probably as an aspect vs. implied by the theme choice. > By the latter, I am assuming that you want Motif style mouse/focus > behavior in any old theme you happen to choose. That's fine, but it > should be optional or we are taking a step backward in feel. > > Bill > > > ---- > Wilhelm K. Schwab, Ph.D. > bschwab AT anest DOT ufl DOT edu > > ________________________________________ > From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr > ] On Behalf Of Alexandre Bergel [Alexandre.Bergel(a)inria.fr] > Sent: Friday, February 20, 2009 5:04 AM > To: Pharo Development > Subject: [Pharo-project] Automatic focus on column upon moose enter > > David, > You're a hero! > Thanks for OB-Enhancements-dr.305 > > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > 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 > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Feb. 20, 2009

Re: [Pharo-project] Automatic focus on column upon moose enter

by Alexandre Bergel

Hi Bill, First of all, I did not authored this change. David did it. I guess this was a request emanated by a bunch of people. Well before OB- Enhancements-dr.305 was produced, I discussed with a few people in my group, and we all agree that not having the automatic focus on column was missing. No much work was necessary to make this change happen: OBPluggableListMorph>>mouseEnter: and OBPluggableTreeMorph>>mouseEnter: were simply removed. This is exactly what OB-Enhancements-dr.305 contains. Personally, the only reason why I am happy with the auto-focus, is by pressing Cmd-T to run tests. I find this quite convenient to simply accept a method, then move the moose to the column and press Cmd-T, without clicking. Although I do not see a scenario where auto-focus is a real problem, I do understand that David made an arbitrary decision without much consultation. Sorry about that. So, what do we do? Cheers, Alexandre On 20 Feb 2009, at 14:38, Schwab,Wilhelm K wrote: > Alexandre, > > Can you give us an explanation or pointer to one? This sounds like > something that Gary worked hard to stop from happening. I want you > to have what you want from your image, and I need my future users to > have what they will demand (loudly<g>). I am also convinced that > there are things (e.g. mouse wheel input) that should "follow the > mouse" without affecting keyboard focus, and this might be one of > them, but referring to focus gives me the idea that keyboard input > will go to the columns based on mouse position, and that > (PLEASE!!!!!) needs to be optional - it drives me batty. I type > quite fast, and if the input goes to what amount to commands instead > of editing, it can get ugly. > > There are some preferences that control behavior like this, and any > such overrides should be conditional on one being set, or moved into > the themes, probably as an aspect vs. implied by the theme choice. > By the latter, I am assuming that you want Motif style mouse/focus > behavior in any old theme you happen to choose. That's fine, but it > should be optional or we are taking a step backward in feel. > > Bill > > > ---- > Wilhelm K. Schwab, Ph.D. > bschwab AT anest DOT ufl DOT edu > > ________________________________________ > From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr > ] On Behalf Of Alexandre Bergel [Alexandre.Bergel(a)inria.fr] > Sent: Friday, February 20, 2009 5:04 AM > To: Pharo Development > Subject: [Pharo-project] Automatic focus on column upon moose enter > > David, > You're a hero! > Thanks for OB-Enhancements-dr.305 > > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > 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 > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Feb. 20, 2009

Re: [Pharo-project] Debugger problem with Windows Vista

by Schwab,Wilhelm K

FWIW, on XP, I have found Pharo to require at least an Aug 2007 vm. Actually, that's too strong - I used an older vm initially, and then had a problem with the newer images hanging. I grabbed the "newer" vm, and the images were able to work; I assume that even newer vms will be ok too, and Torsten seems to be confirming that. Bill ---- Wilhelm K. Schwab, Ph.D. bschwab AT anest DOT ufl DOT edu ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Torsten Bergmann [astares(a)gmx.de] Sent: Friday, February 20, 2009 7:13 AM To: pharo-project(a)lists.gforge.inria.fr Subject: [Pharo-project] Debugger problem with Windows Vista Which Squeak VM version? I'm using the latest Squeak 3.10.10 from Nov. 2008 and the latest pharo image (#10238) without any problem. Bye Torsten -- Jetzt 1 Monat kostenlos! GMX FreeDSL - Telefonanschluss + DSL fÃ¼r nur 17,95 Euro/mtl.!* http://dsl.gmx.de/?ac=OM.AD.PD003K11308T4569a _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Feb. 20, 2009

Re: [Pharo-project] Automatic focus on column upon moose enter

by Schwab,Wilhelm K

Alexandre, Can you give us an explanation or pointer to one? This sounds like something that Gary worked hard to stop from happening. I want you to have what you want from your image, and I need my future users to have what they will demand (loudly<g>). I am also convinced that there are things (e.g. mouse wheel input) that should "follow the mouse" without affecting keyboard focus, and this might be one of them, but referring to focus gives me the idea that keyboard input will go to the columns based on mouse position, and that (PLEASE!!!!!) needs to be optional - it drives me batty. I type quite fast, and if the input goes to what amount to commands instead of editing, it can get ugly. There are some preferences that control behavior like this, and any such overrides should be conditional on one being set, or moved into the themes, probably as an aspect vs. implied by the theme choice. By the latter, I am assuming that you want Motif style mouse/focus behavior in any old theme you happen to choose. That's fine, but it should be optional or we are taking a step backward in feel. Bill ---- Wilhelm K. Schwab, Ph.D. bschwab AT anest DOT ufl DOT edu ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Alexandre Bergel [Alexandre.Bergel(a)inria.fr] Sent: Friday, February 20, 2009 5:04 AM To: Pharo Development Subject: [Pharo-project] Automatic focus on column upon moose enter David, You're a hero! Thanks for OB-Enhancements-dr.305 Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Feb. 20, 2009

[Pharo-project] Debugger problem with Windows Vista

by Torsten Bergmann

Which Squeak VM version? I'm using the latest Squeak 3.10.10 from Nov. 2008 and the latest pharo image (#10238) without any problem. Bye Torsten -- Jetzt 1 Monat kostenlos! GMX FreeDSL - Telefonanschluss + DSL fÃ¼r nur 17,95 Euro/mtl.!* http://dsl.gmx.de/?ac=OM.AD.PD003K11308T4569a

Feb. 20, 2009

Re: [Pharo-project] Question about Universes

by Keith Hodges

> but these images do not require to extend the compiler. > > There is no extension to the compiler. All it does is give the compiler the source up to the marker. The compiler is not changed at all. Matthew just felt that it was cleaner to subclass the compiler, than to put the methods in the class itself, as I used to do. Keith

Feb. 20, 2009