March 2022 - Pharo-users - lists.pharo.org

Re: BlockClosure folding

by Richard O'Keefe

The motivating example can be written aHasDot := a includes: $.. bHasDot := b includes: $.. ^aHasDot = bHasDot ifFalse: [bHasDot] ifTrue: [aHasDot ifTrue: [a < b] ifFalse: [a > b]] (Dijkstra was right. People *do* forget that '=' is one of the standard Boolean operations, and it matters.) This is absolutely straightforward, and without wasting any time wondering what the three-headed IF monster is, we can go straight to the big puzzle: "I can see at a glance what this DOES, but what the heck does it MEAN?" When would this be useful? What would be a good name for this combination, however expressed? I think the moral here is "when you have code whose structure is so complex that you are tempted to construct special control flow objects to make it LOOK simpler, rewrite it so that it IS simpler." I once wrote a class called Distributor based on Boost 'signal's. It was an interesting exercise, and I am still finding mistakes in it. It was not entirely unlike ComplexCondition. What I *haven't* done in the 10 years since I wrote it is found any use for it. On Wed, 16 Mar 2022 at 07:15, <sean(a)clipperadams.com> wrote: > ComplexCondition as described in Andres Valloud, "A Mentoring Course on > Smalltalk" > <http://www.lulu.com/product/paperback/a-mentoring-course-on-smalltalk/37888…> > is available at http://www.squeaksource.com/ComplexCondition.html > > With it, you can do something like: > > ^[a includes: $.], [b includes: $.] > ifAllTrue: [a < b] > ifAnyTrue: [b includes: $.] > otherwise: [a > b] > >

March 16, 2022

Re: BlockClosure folding

by HernÃ¡n Morales Durand

This is an interesting pattern. Thank you for sharing. HernÃ¡n El mar, 15 mar 2022 a las 4:43, JuliÃ¡n Maestri (<serpi90(a)gmail.com>) escribiÃ³: > Not satisfying the equality, but you can use polymorphism. > > Block >> , aBlock > ^ BlockCompositor andAll: OrderedCollection with: self with: aBlock > > BlockCompositor >> #, aBlock > conditions add: aBlock. > > BlockCompositor >> value: anObject > ^ conditions allSatisfy: [:e | e value: anObject ] > > I don't really like the name BlockCompositor, but can't think of a better > name at the moment. > > You could also implement logic for #or: using #+ and: #anySatisfy: for > example, but need to safeguard against mixing both conditions. > > On Mon, 14 Mar 2022 at 22:29, HernÃ¡n Morales Durand < > hernan.morales(a)gmail.com> wrote: > >> I think I saw a coding pattern a while ago that allows you to do the >> following: >> >> cond1 , cond2 , cond3 , cond4 >> >> And providing a kind of folding selector condition #and: you would get: >> >> [ cond1 and: [ cond2 and: [ cond3 and: [ cond4 ] ] ] ]. >> >> for example: >> >> conditions := [ : each | each firstName = 'Boca' ] , >> [ : each | each lastName = 'Baret' ] , >> [ : each | each fullName = 'Virgasia' ]. >> >> such that the following assert is met: >> >> self assert: conditions equals: [ : each | each firstName = 'Boca' and: [ >> each lastName = 'Baret' and: [ each fullName = 'Virgasia' ] ] ]. >> >> Any ideas or pointers? >> >> Cheers, >> >> HernÃ¡n >> >>

March 16, 2022

Re: BlockClosure folding

by HernÃ¡n Morales Durand

Exactly. This was what I was looking for. Thank you Sean. HernÃ¡n El mar, 15 mar 2022 a las 19:15, <sean(a)clipperadams.com> escribiÃ³: > ComplexCondition as described in Andres Valloud, "A Mentoring Course on > Smalltalk" > <http://www.lulu.com/product/paperback/a-mentoring-course-on-smalltalk/37888…> > is available at http://www.squeaksource.com/ComplexCondition.html > > With it, you can do something like: > > ^[a includes: $.], [b includes: $.] > ifAllTrue: [a < b] > ifAnyTrue: [b includes: $.] > otherwise: [a > b] > >

March 16, 2022

Re: Null Object Pattern

by Todd Blanchard

Why do you not just do something like [ âcomplicated code that might fail somewhere in hereâ ] on: Error do: [:error | nil] Use the on:do: exception handling to stay safe. Result := [anObject long chain of messages that might return a nilValue ] on: Error do: [:e | nil]. > On Mar 15, 2022, at 11:16 AM, sean(a)clipperadams.com wrote: > > I had some chaining that was getting too complex due to many nil checks, so I started to refactor using a Null Object. > > However, Iâm struggling a bit with the refactor due to inlining. Since #ifNil: variants might be inlined, it seems that something like: > > anObject with a long chain of messages ifNotNil: [ :result | ââ¦â ] > > must be changed into something like: > > anObject with a long chain of messages isNil ifFalse: [ anObject with a long chain of messages ââ¦â ]. > > Obviously, I can use a temp to have: > > result := anObject with a long chain of messages. > > result isNil ifFalse: [ result ââ¦â ]. > > But both seem ugly and make me question using this pattern. > > What am I missing? > > After 40+ years of Mooreâs Law, can we turn off these inlines by default? >

March 16, 2022

Re: Null Object Pattern

by Bernardo Ezequiel Contreras

if you are using the null object pattern then you should not write those checks (ifNil:ifNotNil:, isNil, isNotNil). you should send the message to an instance of the null object and that object should decide what to do. just an opinion. On Tue, Mar 15, 2022 at 3:16 PM <sean(a)clipperadams.com> wrote: > I had some chaining that was getting too complex due to many nil checks, > so I started to refactor using a Null Object. > > However, Iâm struggling a bit with the refactor due to inlining. Since > #ifNil: variants might be inlined, it seems that something like: > > anObject with a long chain of messages ifNotNil: [ :result | ââ¦â ] > > must be changed into something like: > > anObject with a long chain of messages isNil ifFalse: [ anObject with a > long chain of messages ââ¦â ]. > > Obviously, I can use a temp to have: > > result := anObject with a long chain of messages. > > result isNil ifFalse: [ result ââ¦â ]. > > But both seem ugly and make me question using this pattern. > > 1. > > What am I missing? > 2. > > After 40+ years of Mooreâs Law, can we turn off these inlines by > default? > > -- Bernardo E.C. Sent from a cheap desktop computer in South America.

March 16, 2022

Re: Null Object Pattern

by Richard O'Keefe

I have a bad feeling about this. To start with, why do you CARE whether a particular method is inlined or not? <quote> However, Iâm struggling a bit with the refactor due to inlining. Since #ifNil: variants might be inlined, it seems that something like: anObject with a long chain of messages ifNotNil: [ :result | ââ¦â ] must be changed into something like: anObject with a long chain of messages isNil ifFalse: [ anObject with a long chain of messages ââ¦â ]. </quote> This makes absolutely no sense to me. What makes you think that the combination "_ isNil ifFalse: [_]" will NOT be inlined? In Squeak, x ifNotNil: [...] turns into x; nil; ==; jumpFalse and x isNil ifFalse: [...] turns into x; send isNil; jumpFalse where "send isNil" is a single byte. I don't see a substantial difference here. (I'd have checked in Pharo, but after many interface changes I no longer know how to do view|bytecode.) The thing that rings loud alarm bells for me is there being "long chains" in the first place. Can you give an example? In my own programming, I've generally found that nils turning up in the middle of a chain indicates a serious design error somewhere. On Wed, 16 Mar 2022 at 07:16, <sean(a)clipperadams.com> wrote: > I had some chaining that was getting too complex due to many nil checks, > so I started to refactor using a Null Object. > > However, Iâm struggling a bit with the refactor due to inlining. Since > #ifNil: variants might be inlined, it seems that something like: > > anObject with a long chain of messages ifNotNil: [ :result | ââ¦â ] > > must be changed into something like: > > anObject with a long chain of messages isNil ifFalse: [ anObject with a > long chain of messages ââ¦â ]. > > Obviously, I can use a temp to have: > > result := anObject with a long chain of messages. > > result isNil ifFalse: [ result ââ¦â ]. > > But both seem ugly and make me question using this pattern. > > 1. > > What am I missing? > 2. > > After 40+ years of Mooreâs Law, can we turn off these inlines by > default? > >

March 16, 2022

Re: Null Object Pattern

by Esteban Maringolo

+1 Inlining breaks the fundamental piece of OOP: Message sends. I'm sure there are use cases where inlining adds a significant speedup, but for some messages, I prefer them to be sent. Regards! Esteban A. Maringolo On Tue, Mar 15, 2022 at 3:16 PM <sean(a)clipperadams.com> wrote: > > I had some chaining that was getting too complex due to many nil checks, so I started to refactor using a Null Object. > > However, Iâm struggling a bit with the refactor due to inlining. Since #ifNil: variants might be inlined, it seems that something like: > > anObject with a long chain of messages ifNotNil: [ :result | ââ¦â ] > > must be changed into something like: > > anObject with a long chain of messages isNil ifFalse: [ anObject with a long chain of messages ââ¦â ]. > > Obviously, I can use a temp to have: > > result := anObject with a long chain of messages. > > result isNil ifFalse: [ result ââ¦â ]. > > But both seem ugly and make me question using this pattern. > > What am I missing? > > After 40+ years of Mooreâs Law, can we turn off these inlines by default?

March 15, 2022

Null Object Pattern

by sean＠clipperadams.com

I had some chaining that was getting too complex due to many nil checks, so I started to refactor using a Null Object. However, Iâm struggling a bit with the refactor due to inlining. Since #ifNil: variants might be inlined, it seems that something like: anObject with a long chain of messages ifNotNil: \[ :result | ââ¦â \] must be changed into something like: anObject with a long chain of messages isNil ifFalse: \[ anObject with a long chain of messages ââ¦â \]. Obviously, I can use a temp to have: result := anObject with a long chain of messages. result isNil ifFalse: \[ result ââ¦â \]. But both seem ugly and make me question using this pattern. 1. What am I missing? 2. After 40+ years of Mooreâs Law, can we turn off these inlines by default?

March 15, 2022

Re: BlockClosure folding

by sean＠clipperadams.com

ComplexCondition as described in [Andres Valloud, "A Mentoring Course on Smalltalk"](http://www.lulu.com/product/paperback/a-mentoring-course-on-smalltalk/3788890) is available at http://www.squeaksource.com/ComplexCondition.html With it, you can do something like: ``` ^[a includes: $.], [b includes: $.] ifAllTrue: [a < b] ifAnyTrue: [b includes: $.] otherwise: [a > b] ```

March 15, 2022

Re: BlockClosure folding

by JuliÃ¡n Maestri

Not satisfying the equality, but you can use polymorphism. Block >> , aBlock ^ BlockCompositor andAll: OrderedCollection with: self with: aBlock BlockCompositor >> #, aBlock conditions add: aBlock. BlockCompositor >> value: anObject ^ conditions allSatisfy: [:e | e value: anObject ] I don't really like the name BlockCompositor, but can't think of a better name at the moment. You could also implement logic for #or: using #+ and: #anySatisfy: for example, but need to safeguard against mixing both conditions. On Mon, 14 Mar 2022 at 22:29, HernÃ¡n Morales Durand < hernan.morales(a)gmail.com> wrote: > I think I saw a coding pattern a while ago that allows you to do the > following: > > cond1 , cond2 , cond3 , cond4 > > And providing a kind of folding selector condition #and: you would get: > > [ cond1 and: [ cond2 and: [ cond3 and: [ cond4 ] ] ] ]. > > for example: > > conditions := [ : each | each firstName = 'Boca' ] , > [ : each | each lastName = 'Baret' ] , > [ : each | each fullName = 'Virgasia' ]. > > such that the following assert is met: > > self assert: conditions equals: [ : each | each firstName = 'Boca' and: [ > each lastName = 'Baret' and: [ each fullName = 'Virgasia' ] ] ]. > > Any ideas or pointers? > > Cheers, > > HernÃ¡n > >

March 15, 2022

BlockClosure folding

by HernÃ¡n Morales Durand

I think I saw a coding pattern a while ago that allows you to do the following: cond1 , cond2 , cond3 , cond4 And providing a kind of folding selector condition #and: you would get: [ cond1 and: [ cond2 and: [ cond3 and: [ cond4 ] ] ] ]. for example: conditions := [ : each | each firstName = 'Boca' ] , [ : each | each lastName = 'Baret' ] , [ : each | each fullName = 'Virgasia' ]. such that the following assert is met: self assert: conditions equals: [ : each | each firstName = 'Boca' and: [ each lastName = 'Baret' and: [ each fullName = 'Virgasia' ] ] ]. Any ideas or pointers? Cheers, HernÃ¡n

March 15, 2022

Re: pharo image and vm

by Esteban Lorenzano

but is true is not "recommended", I should phrase what is there better ;) Also VM should work anyway... but Ubuntu 16.04 is pretty old, I am no surprised it is not working properly (and no idea if we can make it work easily... I will let Pablo Tesone answer that)... in OBS we start by ubuntu 18.04 Esteban On Mar 14 2022, at 5:46 pm, Otto Behrens <otto(a)finworks.biz> wrote: > Thanks Esteban, > > I'm on Ubuntu 16.04. Where did I miss the "pointed in the download page"? If I go to https://pharo.org/download, I can see a section called > "Pharo standalone", with a link there to " > Pharo VM 9 for Linux: 64bit (default) (https://files.pharo.org/get-files/90/pharo64-linux-stable.zip) | 32bit (https://files.pharo.org/get-files/90/pharo-linux-stable.zip) > > > Why would that not work? > > I really prefer not to install a deb. More work for me now. > > > Otto Behrens > > > > +27 82 809 2375 > > > > > > > > > > > > > > > > > > > > > > > > www.finworks.biz (http://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. > > > > > > > > > > > > > > On Mon, Mar 14, 2022 at 6:39 PM Esteban Lorenzano <estebanlm(a)netc.eu (mailto:estebanlm@netc.eu)> wrote: > > Hi, > > > > which is your distribution? > > In anycase, as pointed in the download page, preferred way in linux to install the vm is through openbuildservice: > > > > https://software.opensuse.org/download.html?project=devel:languages:pharo:l… > > can you try one of that and tell us if problem remains? > > > > Esteban > > On Mar 14 2022, at 5:28 pm, Otto Behrens <otto(a)finworks.biz (mailto:otto@finworks.biz)> wrote: > > > 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 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > www.finworks.biz (http://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

Re: pharo image and vm

by Otto Behrens

Thanks Esteban, I'm on Ubuntu 16.04. Where did I miss the "pointed in the download page"? If I go to https://pharo.org/download, I can see a section called "Pharo standalone", with a link there to " - Pharo VM 9 for Linux: 64bit (default) <https://files.pharo.org/get-files/90/pharo64-linux-stable.zip> | 32bit <https://files.pharo.org/get-files/90/pharo-linux-stable.zip> Why would that not work? I really prefer not to install a deb. More work for me now. 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. On Mon, Mar 14, 2022 at 6:39 PM Esteban Lorenzano <estebanlm(a)netc.eu> wrote: > Hi, > > which is your distribution? > In anycase, as pointed in the download page, preferred way in linux to > install the vm is through openbuildservice: > > > https://software.opensuse.org/download.html?project=devel:languages:pharo:l… > can you try one of that and tell us if problem remains? > > Esteban > > On Mar 14 2022, at 5:28 pm, Otto Behrens <otto(a)finworks.biz> wrote: > > 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

Re: pharo image and vm

by Esteban Lorenzano

Hi, which is your distribution? In anycase, as pointed in the download page, preferred way in linux to install the vm is through openbuildservice: https://software.opensuse.org/download.html?project=devel:languages:pharo:l… can you try one of that and tell us if problem remains? Esteban On Mar 14 2022, at 5:28 pm, Otto Behrens <otto(a)finworks.biz> wrote: > 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 > > > > > > > > > > > > > > > > > > > > > > > > www.finworks.biz (http://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

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

Re: SpDropListPresenter emptyList

by Russ Whaley

Yes, me too- and be careful, thereâs no going back - lots of deprecated methods in v10. Plus, for me, Iâm on MacOS Mojave. v10 wouldnât run - they fixed it so v10 runs - but now v9 wonât run for me, soâ¦ Iâm migrating to v10! On Sat, Mar 5, 2022 at 8:17 AM Robert Briggs via Pharo-users < pharo-users(a)lists.pharo.org> wrote: > Ah. OK. Thanks. Unfortunately I am working on a P9 image. I will have > to go through the chore of transferring my work to P10 I guess. > > > > Regards > > R > > > > *From: *Russ Whaley <whaley.russ(a)gmail.com> > *Reply to: *Any question about pharo is welcome < > pharo-users(a)lists.pharo.org> > *Date: *Saturday, 5 March 2022 at 12:49 > *To: *Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > *Subject: *[Pharo-users] Re: SpDropListPresenter emptyList > > > > I had this same issue and reported in v9. It appears to be fixed in v10 > and from what I understand there will be no âback-portâ. > > > > Russ > > > > On Sat, Mar 5, 2022 at 7:24 AM Robert Briggs via Pharo-users < > pharo-users(a)lists.pharo.org> wrote: > > I think this might be a bug. > > > > When I send emptyList to a non-empty SpDropListPresenter it reports > âSubscriptOutOfBounds: 1â. > > > > I seems to be due to emptyList setting the list model to a new empty > OrderedCollection and a later method trying to access the first item in the > collection. > > > > Attached screen shot shows the debugger window. > > > > If it is a bug please report it and if possible advise a workaround. > > > > If not a bug please advise the correct way to clear or change the > contents of a drop list. > > > > Many thanks > > Robert > > > > [image: Graphical user interface, text, application Description > automatically generated] > > -- > > Russ Whaley > whaley.russ(a)gmail.com > -- Russ Whaley whaley.russ(a)gmail.com

March 5, 2022