- Pharo-users - lists.pharo.org

pharo image and vm

by Otto Behrens

Hi, I downloaded a new pharo from https://files.pharo.org/get-files/90/pharo64.zip https://files.pharo.org/get-files/90/pharo64-linux-stable.zip When I start up the image with the VM, I get "Your VM is too old for this image. Please download the latest VM" None of the shortcut keys seem to work. Something like <ctrl>-c does nothing. Does this have something to do with the incorrect VM? What am I missing here? Thanks for your help Otto Behrens +27 82 809 2375 [image: FINWorks] [image: FINWorks] <http://za.linkedin.com/in/waltherbehrens> www.finworks.biz Disclaimer & Confidentiality Note: This email is intended solely for the use of the individual or entity named above as it may contain information that is confidential and privileged. If you are not the intended recipient, be advised that any dissemination, distribution or copying of this email is strictly prohibited. FINWorks cannot be held liable by any person other than the addressee in respect of any opinions, conclusions, advice or other information contained in this email.

March 14, 2022

[ANN] Camp Smalltalk Supreme's Speaker Line-up

by horrido.hobbies＠gmail.com

Here it is: https://campsmalltalksupreme.wordpress.com/2020/06/28/daily-events/ Looks like a very strong event!

March 14, 2022

Re: Pharo with Style (new version) is now available as physical book

by Richard O'Keefe

Congratulations. On Sun, 13 Mar 2022 at 08:44, stephane ducasse <stephane.ducasse(a)inria.fr> wrote: > > https://www.amazon.fr/Pharo-Style-StÃ©phane-Ducasse/dp/232218201X/ref=sr_1_…MÃÅ½ÃÃ&crid=15GN4OFOFHK56&keywords=Pharo+with+style&qid=1647113931&sprefix=pharo+with+style%2Caps%2C60&sr=8-1 > <https://www.amazon.fr/Pharo-Style-St%C3%A9phane-Ducasse/dp/232218201X/ref=s…> > > https://www.decitre.fr/livre-pod/pharo-with-style-9782322182015.html > > > https://www.bod.fr/librairie/pharo-with-style-stephane-ducasse-9782322182015 > > I will update the web site as soon as I get time. > > S >

March 13, 2022

Pharo with Style (new version) is now available as physical book

by stephane ducasse

https://www.amazon.fr/Pharo-Style-StÃ©phane-Ducasse/dp/232218201X/ref=sr_1_…MÃÅ½ÃÃ&crid=15GN4OFOFHK56&keywords=Pharo+with+style&qid=1647113931&sprefix=pharo+with+style%2Caps%2C60&sr=8-1 <https://www.amazon.fr/Pharo-Style-St%C3%A9phane-Ducasse/dp/232218201X/ref=s…> https://www.decitre.fr/livre-pod/pharo-with-style-9782322182015.html <https://www.decitre.fr/livre-pod/pharo-with-style-9782322182015.html> https://www.bod.fr/librairie/pharo-with-style-stephane-ducasse-9782322182015 <https://www.bod.fr/librairie/pharo-with-style-stephane-ducasse-9782322182015> I will update the web site as soon as I get time. S

March 12, 2022

Re: Detecting keystrokes in Spec2 input fields

by stephane ducasse

in general this is not a good style to set color directly. Using style will make sure that your components will support themes in a simpler way. Because you will not have to have case statements and check all the place where you change color. S > On 12 Mar 2022, at 15:53, Robert Briggs via Pharo-users <pharo-users(a)lists.pharo.org> wrote: > > > Thanks Esteban > > Iâve made it work based on your example. As you said I didnât need registerEvents. My original block just called a method that I used for trapping with the debugger to investigate how it worked. > > One question. Why can I not simply send borderColor: #red to the presenter rather than using the stylesheet method? > > Regards > Robert > > From: Esteban Lorenzano <estebanlm(a)netc.eu <mailto:estebanlm@netc.eu>> > Reply to: Any question about pharo is welcome <pharo-users(a)lists.pharo.org <mailto:pharo-users@lists.pharo.org>> > Date: Saturday, 12 March 2022 at 13:28 > To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > Cc: Robert Briggs <rbriggs2009(a)me.com> > Subject: [Pharo-users] Re: Detecting keystrokes in Spec2 input fields > > Hi, > no, you don't need to send any "registerEvents". This is internal and is sent on initialize, when you create the presenter. > precisely last week I make an example of what you are asking for: > > https://github.com/pharo-spec/Spec-QA/blob/main/qa005.md <https://github.com/pharo-spec/Spec-QA/blob/main/qa005.md> > cheers! > Esteban > > On Mar 12 2022, at 2:20 pm, Robert Briggs via Pharo-users <pharo-users(a)lists.pharo.org> wrote: >> Hi Kasper >> >> >> >> Problem solved. Iâve done some more experimenting and it seems that registerEvents needs to be sent to make whenTextChangedDo: active. Makes sense but havenât seen it documented anywhere. >> >> >> >> Regards >> >> Robert >> >> >> >> From: Kasper Osterbye <kasper.osterbye(a)gmail.com> >> Reply to: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> >> Date: Saturday, 12 March 2022 at 10:31 >> To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> >> Subject: [Pharo-users] Re: Detecting keystrokes in Spec2 input fields >> >> If it is in the TextPresenter you might be looking for >> >> whenTextChangedDo: or whenSubmitDo: >> Both inherited from SpAbstractTextPresenter >> >> Best, >> >> Kasper >> >> >> >> >>> On 12 Mar 2022, at 11.26, Robert Briggs via Pharo-users <pharo-users(a)lists.pharo.org <mailto:pharo-users@lists.pharo.org>> wrote: >>> >>> >>> Hi >>> >>> Is there a simple way to detect when a use makes a keystroke in for example a Spec 2 Text Input Presenter? >>> >>> Iâve been going through all the relevant classes and methods, even into Morphic, but so far I have not found a way to do it. >>> >>> I want to be able to identify when unaccepted changes have been made to the displayed text to ensure that a use does not leave a form without saving any input made. >>> >>> Regards >>> Robert

March 12, 2022

Re: Detecting keystrokes in Spec2 input fields

by Robert Briggs

Thanks Esteban Iâve made it work based on your example.Â As you said I didnât need registerEvents.Â My original block just called a method that I used for trapping with the debugger to investigate how it worked. One question.Â Why can I not simply send borderColor: #red to the presenter rather than using the stylesheet method? Regards Robert From: Esteban Lorenzano <estebanlm(a)netc.eu> Reply to: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> Date: Saturday, 12 March 2022 at 13:28 To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> Cc: Robert Briggs <rbriggs2009(a)me.com> Subject: [Pharo-users] Re: Detecting keystrokes in Spec2 input fields Hi, no, you don't need to send any "registerEvents". This is internal and is sent on initialize, when you create the presenter. precisely last week I make an example of what you are asking for: https://github.com/pharo-spec/Spec-QA/blob/main/qa005.md cheers! Esteban On Mar 12 2022, at 2:20 pm, Robert Briggs via Pharo-users <pharo-users(a)lists.pharo.org> wrote: Hi Kasper Problem solved. Iâve done some more experimenting and it seems that registerEvents needs to be sent to make whenTextChangedDo: active. Makes sense but havenât seen it documented anywhere. Regards Robert From: Kasper Osterbye <kasper.osterbye(a)gmail.com> Reply to: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> Date: Saturday, 12 March 2022 at 10:31 To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> Subject: [Pharo-users] Re: Detecting keystrokes in Spec2 input fields If it is in the TextPresenter you might be looking for whenTextChangedDo: or whenSubmitDo: Both inherited from SpAbstractTextPresenter Best, Kasper On 12 Mar 2022, at 11.26, Robert Briggs via Pharo-users <pharo-users(a)lists.pharo.org> wrote: Hi Is there a simple way to detect when a use makes a keystroke in for example a Spec 2 Text Input Presenter? Iâve been going through all the relevant classes and methods, even into Morphic, but so far I have not found a way to do it. I want to be able to identify when unaccepted changes have been made to the displayed text to ensure that a use does not leave a form without saving any input made. Regards Robert

March 12, 2022

Re: Detecting keystrokes in Spec2 input fields

by Esteban Lorenzano

Hi, no, you don't need to send any "registerEvents". This is internal and is sent on initialize, when you create the presenter. precisely last week I make an example of what you are asking for: https://github.com/pharo-spec/Spec-QA/blob/main/qa005.md cheers! Esteban On Mar 12 2022, at 2:20 pm, Robert Briggs via Pharo-users <pharo-users(a)lists.pharo.org> wrote: > Hi Kasper > > > Problem solved. Iâve done some more experimenting and it seems that registerEvents needs to be sent to make whenTextChangedDo: active. Makes sense but havenât seen it documented anywhere. > > Regards > Robert > > From: Kasper Osterbye <kasper.osterbye(a)gmail.com> > Reply to: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > Date: Saturday, 12 March 2022 at 10:31 > To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > Subject: [Pharo-users] Re: Detecting keystrokes in Spec2 input fields > > > > > If it is in the TextPresenter you might be looking for > > whenTextChangedDo: or whenSubmitDo: > Both inherited from SpAbstractTextPresenter > > > > Best, > > > > Kasper > > > > > > On 12 Mar 2022, at 11.26, Robert Briggs via Pharo-users <pharo-users(a)lists.pharo.org (mailto:pharo-users@lists.pharo.org)> wrote: > > > > > > Hi > > > > > > Is there a simple way to detect when a use makes a keystroke in for example a Spec 2 Text Input Presenter? > > > > > > > > Iâve been going through all the relevant classes and methods, even into Morphic, but so far I have not found a way to do it. > > > > > > > > I want to be able to identify when unaccepted changes have been made to the displayed text to ensure that a use does not leave a form without saving any input made. > > > > > > > > Regards > > > > Robert > > > > > > > > >

March 12, 2022

Re: Detecting keystrokes in Spec2 input fields

by Robert Briggs

Hi Kasper Problem solved.Â Iâve done some more experimenting and it seems that registerEvents needs to be sent to make Â whenTextChangedDo: active.Â Makes sense but havenât seen it documented anywhere. Regards Robert From: Kasper Osterbye <kasper.osterbye(a)gmail.com> Reply to: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> Date: Saturday, 12 March 2022 at 10:31 To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> Subject: [Pharo-users] Re: Detecting keystrokes in Spec2 input fields If it is in the TextPresenter you might be looking for whenTextChangedDo: or whenSubmitDo: Both inherited from SpAbstractTextPresenter Best, Kasper On 12 Mar 2022, at 11.26, Robert Briggs via Pharo-users <pharo-users(a)lists.pharo.org> wrote: Hi Is there a simple way to detect when a use makes a keystroke in for example a Spec 2 Text Input Presenter? Iâve been going through all the relevant classes and methods, even into Morphic, but so far I have not found a way to do it. I want to be able to identify when unaccepted changes have been made to the displayed text to ensure that a use does not leave a form without saving any input made. Regards Robert

March 12, 2022

Re: Detecting keystrokes in Spec2 input fields

by Kasper Osterbye

If it is in the TextPresenter you might be looking for whenTextChangedDo: or whenSubmitDo: Both inherited from SpAbstractTextPresenter Best, Kasper > On 12 Mar 2022, at 11.26, Robert Briggs via Pharo-users <pharo-users(a)lists.pharo.org> wrote: > > Hi > > Is there a simple way to detect when a use makes a keystroke in for example a Spec 2 Text Input Presenter? > > Iâve been going through all the relevant classes and methods, even into Morphic, but so far I have not found a way to do it. > > I want to be able to identify when unaccepted changes have been made to the displayed text to ensure that a use does not leave a form without saving any input made. > > Regards > Robert

March 12, 2022

Detecting keystrokes in Spec2 input fields

by Robert Briggs

Hi Is there a simple way to detect when a use makes a keystroke in for example a Spec 2 Text Input Presenter? Iâve been going through all the relevant classes and methods, even into Morphic, but so far I have not found a way to do it. I want to be able to identify when unaccepted changes have been made to the displayed text to ensure that a use does not leave a form without saving any input made. Regards Robert

March 12, 2022