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

[ANN] COVID-19 and JRMPC

by Richard Kenneth Eng

https://smalltalk.tech.blog/2020/03/13/covid-19-and-jrmpc/ This is very unfortunate. I was counting on the awards ceremony for a great deal of PR value. A virtual ceremony likely wouldn't have the same impact. Richard

March 14, 2020

Re: [Pharo-users] Corona virus

by Davide Grandi

That's true, and it will be a worldwide pandemia. Try to work @ home, limit contacts with other people, don't go in crowded places, and PROTECT YOUR PARENTS - GRANDPARENTS. The local newsmagazine of Dario's town, few km from mine, has normally ONE page of obituary. Yesterday ... TEN pages. bye, Davide On 14/03/2020 14:52, dario.trussardi65 wrote: > Ciao, > be very careful ... it's very dangerous ... > here in Bergamo it's a disaster. > We are losing our grandparents like leaves falling from the tree .... > Take all precautions .... Don't underestimate the situation..... > See you soon.... > Dario -- Ing. Davide Grandi email : davide.grandi(a)email.it

March 14, 2020

R: Corona virus

by Lorenzo

Ciao Dario, grazie per la segnalazione e tanti auguri a tutti voi. Lorenzo Da: Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] Per conto di dario.trussardi65 Inviato: sabato 14 marzo 2020 14:53 A: Any welcome question about pharo is <pharo-users(a)lists.pharo.org> Oggetto: [Pharo-users] Corona virus Ciao, be very careful ... it's very dangerous ... here in Bergamo it's a disaster. We are losing our grandparents like leaves falling from the tree .... Take all precautions .... Don't underestimate the situation..... See you soon.... Dario -- Questa e-mail Ã¨ stata controllata per individuare virus con Avast antivirus. https://www.avast.com/antivirus

March 14, 2020

Corona virus

by dario.trussardi65

Ciao, be very careful ... it's very dangerous ... here in Bergamo it's a disaster. We are losing our grandparents like leaves falling from the tree .... Take all precautions .... Don't underestimate the situation..... See you soon.... Dario

March 14, 2020

Re: [Pharo-users] Stale SQLite connection

by Erik Stel

Jeff, You could have a look at SmalltalkImage>>#addToShutDownList: and SmalltalkImage>>#addToStartUpList: to stop/(re)start the connection when image is closed or a snapshot is taken. Add a method #startUp: to handle reconnecting. See for example Clipboard>>#startUp: Cheers, Erik -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

March 13, 2020

Re: [Pharo-users] Clean up method like #exiting from VAST

by Erik Stel

Vince, You could check SmalltalkImage>>#addToShutDownList: Greetz, Erik -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

March 13, 2020

Re: [Pharo-users] Clean up method like #exiting from VAST

by N. Bouraqadi

Hi Vince, In Pharo there is startup list that is used also when quitting (in reverse upon shutdown). To register a class : Smalltalk addToStartUpList: aClass The class startup behavior should go in class method startUp: resumingBoolean The class quit behavior should go in a class method shutDown: quittingBoolean Noury -- Learn, Code & Make for the Planet https://nootrix.com <https://nootrix.com/> > On 13 Mar 2020, at 07:02, Vince Refiti <vince.refiti(a)trapezegroup.com.au> wrote: > > Hello > > In VAST there is a class-side method #exiting which can be implemented in an application and is called just before the image is shut down. I use it to typically implement clean-up code. > > Is there something similar in Pharo? > > If I use aBlock ensure: cleanUpBlock, is the cleanUpBlock guaranteed to run in what circumstances? > > Vince

March 13, 2020

Clean up method like #exiting from VAST

by Vince Refiti

Hello In VAST there is a class-side method #exiting which can be implemented in an application and is called just before the image is shut down. I use it to typically implement clean-up code. Is there something similar in Pharo? If I use aBlock ensure: cleanUpBlock, is the cleanUpBlock guaranteed to run in what circumstances? Vince

March 13, 2020

Re: [Pharo-users] Stale SQLite connection

by Vince Refiti

Hi Jeff Is this you from Brisbane? Did you used to come to the meetups at the State Library? Well anyway, I used to do something similar to what you describe, by lazy initializing the connection and also checking to see if it is open. dbConnection dbConnection ifNil: [ dbConenction := SQLiteConnection on: self dbFilePath ]. dbConnection isOpen ifFalse: [ dbConnection open ]. ^ dbConnection I have not noticed it being "slow", but then I use transactions wherever I can. Hope that helps. Vince -----Original Message----- From: Pharo-users <pharo-users-bounces(a)lists.pharo.org> On Behalf Of Jeff Gray Sent: Friday, 13 March 2020 3:21 PM To: pharo-users(a)lists.pharo.org Subject: [Pharo-users] Stale SQLite connection EXTERNAL: Do not click links or open attachments if you do not recognize the sender. In my code I'm opening a sqlite connection and keeping it open rather than opening and closing one on each transaction. Generally it's working well. I often save and close my image. When I then reopen the image I still have a connection and it says it's open, but using it gives me an error. This is easily recovered. I just open a new connection. Is there a way I can see if a connection is still good, in my code? Or should I be opening and closing connections every transaction? I haven't benchmarked it but I'm assuming it would be slower. I guess I could set my connection to nil in a start-up script. That would cause my code to get a new connection after a break from development. Any recommendations? Thanks, Jeff. -- Sent from: https://urldefense.com/v3/__http://forum.world.st/Pharo-Smalltalk-Users-f13…

March 13, 2020

Stale SQLite connection

by Jeff Gray

In my code I'm opening a sqlite connection and keeping it open rather than opening and closing one on each transaction. Generally it's working well. I often save and close my image. When I then reopen the image I still have a connection and it says it's open, but using it gives me an error. This is easily recovered. I just open a new connection. Is there a way I can see if a connection is still good, in my code? Or should I be opening and closing connections every transaction? I haven't benchmarked it but I'm assuming it would be slower. I guess I could set my connection to nil in a start-up script. That would cause my code to get a new connection after a break from development. Any recommendations? Thanks, Jeff. -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

March 13, 2020