- Pharo-users - lists.pharo.org

Re: [Pharo-users] Externally signalling pharo VM for shutdown

by Norbert Hartl

> Am 10.02.2015 um 21:25 schrieb Esteban A. Maringolo <emaringolo(a)gmail.com>: > > Great. This is cool. > > Why this can't be part of the stock vm/image? > Because it needs OSProcess ;) A zinc server is always present in the image. Sven made a ZnReadEvalPrintDelegate that you can easily hook in to execute a smalltalk snippet (if your host is secured). The good thing about Sebastians approach is that whenever the OS is shut down it is called with SIGTERM from the OS. So should fit nicely with orchestration of the machine. Norbert > Regards! > Esteban A. Maringolo > > > 2015-02-10 16:28 GMT-03:00 Sebastian Sastre <sebastian(a)flowingconcept.com>: >> You can do it with >> >> kill -15 PID >> >> And, this (requires OSProcess): >> >> makeStopHook >> "Answers the process that hooks to the >> OS signal that makes this worker to shutdown >> when the VM process receives a TERM signal from >> the OS." >> >> ^ [|semaphore| >> semaphore := OSProcess accessor forwardSigTerm. >> semaphore wait. >> self onTerminationSignal] >> forkAt: Processor systemBackgroundPriority >> named: 'Image TERMâ >> >> >> >> onTerminationSignal >> "The process for the VM of this image >> has received a TERM signal from the OS. >> React accordingly" >> >> self log: 'That''s all folks. This worker is shutting down. Bye bye...' level:#messages. >> OSProcess accessor restoreSigTerm. >> SmalltalkImage current snapshot: false andQuit: true. >> >> >> >> >> >> >>> On Feb 10, 2015, at 4:58 PM, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: >>> >>> Is there a way I can externally signal a running pharo-vm in order to >>> request a shutdown equivalent to clicking on the close icon? >>> >>> I'd like to externally manage the start/stop of a Pharo image, but >>> because the image can be used during development, I'd like to provide >>> the user with a confirmation dialog instead of simply killing the >>> process. >>> >>> Regards! >>> >>> >>> Esteban A. Maringolo >>> >> >> >

Feb. 10, 2015

Re: [Pharo-users] recover lost changes

by Norbert Hartl

> Am 10.02.2015 um 20:59 schrieb stepharo <stepharo(a)free.fr>: > > Yes this should be fixed. > You mean fix the current implementation or swap it for epicea? Norbert > Le 10/2/15 16:42, Martin BÃ¤hr a Ã©crit : >> Excerpts from Hartmut's message of 2015-02-10 15:58:13 +0100: >>> Working with Pharo 3.0 I noticed for a while that I could not recover >>> class definitions (do it's) from the "Recent Changes". >> i noticed this too. >> methods worked fine, but i couldn't recover methods to new classes until i >> recreated the class manually. >> >> greetings, martin. >> > >

Feb. 10, 2015

Re: [Pharo-users] Externally signalling pharo VM for shutdown

by Esteban A. Maringolo

Great. This is cool. Why this can't be part of the stock vm/image? Regards! Esteban A. Maringolo 2015-02-10 16:28 GMT-03:00 Sebastian Sastre <sebastian(a)flowingconcept.com>: > You can do it with > > kill -15 PID > > And, this (requires OSProcess): > > makeStopHook > "Answers the process that hooks to the > OS signal that makes this worker to shutdown > when the VM process receives a TERM signal from > the OS." > > ^ [|semaphore| > semaphore := OSProcess accessor forwardSigTerm. > semaphore wait. > self onTerminationSignal] > forkAt: Processor systemBackgroundPriority > named: 'Image TERMâ > > > > onTerminationSignal > "The process for the VM of this image > has received a TERM signal from the OS. > React accordingly" > > self log: 'That''s all folks. This worker is shutting down. Bye bye...' level:#messages. > OSProcess accessor restoreSigTerm. > SmalltalkImage current snapshot: false andQuit: true. > > > > > > >> On Feb 10, 2015, at 4:58 PM, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: >> >> Is there a way I can externally signal a running pharo-vm in order to >> request a shutdown equivalent to clicking on the close icon? >> >> I'd like to externally manage the start/stop of a Pharo image, but >> because the image can be used during development, I'd like to provide >> the user with a confirmation dialog instead of simply killing the >> process. >> >> Regards! >> >> >> Esteban A. Maringolo >> > >

Feb. 10, 2015

Re: [Pharo-users] Spotter: Browse Impementors?

by Sean P. DeNigris

Juraj Kubelka wrote > Do you need to open it in Implementors/Senders Browser? Yes. I was fixing mouse wheel user code to handle horizontal wheel events. The Morphic hook is #mouseWheel:, so I wanted a browser on all implementors of #mouseWheel: so that I could view each one and update it if necessary. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Spotter-Browse-Impementors-tp4805013p4805028.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Feb. 10, 2015

Re: [Pharo-users] Spotter: Browse Impementors?

by Juraj Kubelka

You can dive-in using cmd+shift+right-arrow in Spotter and follow observation of those implementors. Preview is available by cmd+p. So basically you open in a browser only one specific method. Do you need to open it in Implementors/Senders Browser? If yes, can you describe your use case, please? Thanks. Cheers, Juraj > 10. 2. 2015 v 16:40, Sean P. DeNigris <sean(a)clipperadams.com>: > > Maybe I'm missing something obvious, but if I zero in on a message name in > spotter, can I open a browser on all implementors, or only browse one > specific method? > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Spotter-Browse-Impementors-tp4805013.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >

Feb. 10, 2015

Re: [Pharo-users] recover lost changes

by stepharo

Yes this should be fixed. Le 10/2/15 16:42, Martin BÃ¤hr a Ã©crit : > Excerpts from Hartmut's message of 2015-02-10 15:58:13 +0100: >> Working with Pharo 3.0 I noticed for a while that I could not recover >> class definitions (do it's) from the "Recent Changes". > i noticed this too. > methods worked fine, but i couldn't recover methods to new classes until i > recreated the class manually. > > greetings, martin. >

Feb. 10, 2015

Re: [Pharo-users] Nautilus groups

by stepharo

having a simpler way to express here is my project would be good. For now the way to add a group is too complex. I would like to click on package and add it to a favorite list that is on the top I would love to get a group containing the class that were loaded (or not in the system). because often I load a configuration and I have no clue what have been loaded. Stef > Hello, > > We would like to know if some of you use Nautilus groups functionality: > > * dynamic groups: 'Last modified packages', 'Most viewed classes', > 'Work' > * user defined groups : from the menu, you can flatten the content > of many packages and get all classes into the newly created group. > > We have the feeling that it is not used (or not a lot) and we think to > replace it with another mechanism (for example, let the user define > his/her 'favorites' classes / packages). > > Thanks for the feedback. >

Feb. 10, 2015

Spotter: Browse Impementors?

by Sean P. DeNigris

Maybe I'm missing something obvious, but if I zero in on a message name in spotter, can I open a browser on all implementors, or only browse one specific method? ----- Cheers, Sean -- View this message in context: http://forum.world.st/Spotter-Browse-Impementors-tp4805013.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Feb. 10, 2015

Re: [Pharo-users] Externally signalling pharo VM for shutdown

by Sebastian Sastre

You can do it with kill -15 PID And, this (requires OSProcess): makeStopHook "Answers the process that hooks to the OS signal that makes this worker to shutdown when the VM process receives a TERM signal from the OS." ^ [|semaphore| semaphore := OSProcess accessor forwardSigTerm. semaphore wait. self onTerminationSignal] forkAt: Processor systemBackgroundPriority named: 'Image TERMâ onTerminationSignal "The process for the VM of this image has received a TERM signal from the OS. React accordingly" self log: 'That''s all folks. This worker is shutting down. Bye bye...' level:#messages. OSProcess accessor restoreSigTerm. SmalltalkImage current snapshot: false andQuit: true. > On Feb 10, 2015, at 4:58 PM, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > > Is there a way I can externally signal a running pharo-vm in order to > request a shutdown equivalent to clicking on the close icon? > > I'd like to externally manage the start/stop of a Pharo image, but > because the image can be used during development, I'd like to provide > the user with a confirmation dialog instead of simply killing the > process. > > Regards! > > > Esteban A. Maringolo >

Feb. 10, 2015

Re: [Pharo-users] Externally signalling pharo VM for shutdown

by Paul DeBruicker

Depends on how you want the user to access the image. Using Seaside you could do something like whats described here: http://book.seaside.st/book/advanced/deployment/maintaining/requesthandler Esteban A. Maringolo wrote > Is there a way I can externally signal a running pharo-vm in order to > request a shutdown equivalent to clicking on the close icon? > > I'd like to externally manage the start/stop of a Pharo image, but > because the image can be used during development, I'd like to provide > the user with a confirmation dialog instead of simply killing the > process. > > Regards! > > > Esteban A. Maringolo -- View this message in context: http://forum.world.st/Externally-signalling-pharo-VM-for-shutdown-tp4804999… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Feb. 10, 2015