- Pharo-users - lists.pharo.org

Extending Calypso
by Juraj Kubelka Nov. 2, 2017

Nov. 2, 2017

Hi, Are there any examples (documentation) how to extend Calipso? I have tried to create a simple (demo) method group, but I miss something, because it is not called. I have created three subclasses of: ClyMethodGroup (with #name and #includesMethod:), ClySingleMethodGroupProvider (with #methodGroupClass), and ClyEnvironmentPlugin (with #collectMethodGroupProvidersFor:). What do I miss? Letâs say that I want a new method group that displays all methods of a selected class that include substring âfooâ. Thanks! Juraj

2 4

Permancy of booklet links
by Ben Coman Nov. 2, 2017

Nov. 2, 2017

This link turned up in a google search on... Web Scraping Pharo, which is great, http://files.pharo.org/books-pdfs/booklet-Scraping/2017-09-29-scrapingbook.… but with the date I'm wondering how permanent the link is, for if I use it the respond to someone's question in a forum? Will you be keeping years of pdfs? For now I'll just use the directory url, but future missing files will frustrate user searches. Perhaps a sitemap is needed (though I'm not familiar with the details)... https://support.google.com/webmasters/answer/183668?hl=en cheers -ben

3 2

Fwd: GitHub
by hamdi gabsi Nov. 2, 2017

Nov. 2, 2017

---------- Forwarded message ---------- From: hamdi gabsi <gabsi.hamdi(a)gmail.com> Date: 2017-11-02 14:30 GMT+01:00 Subject: Re: GitHub To: pharo-users(a)lists.pharo.org For resolving my problem. I knew that it was when pushing my code, that's mean that the commit was well done. So I pushed it from my Terminal. I went to my Pharo local repository and I tapped git status then git push. After that in iceberg ,setting I introduced my user name and password. so that he remembered me. And it work from my VM no need to go to the Terminal. We can find answers in https://github.com/pharo-vcs/iceberg Thank you. 2017-11-02 14:06 GMT+01:00 hamdi gabsi <gabsi.hamdi(a)gmail.com>: > I am working with Pharo 6.0 > > 2017-11-02 14:05 GMT+01:00 hamdi gabsi <gabsi.hamdi(a)gmail.com>: > >> Hello, >> >> I'am Hamdi, I am doing an internship with Rmod Team. I have a problem >> with pushing my code in Github, In fact, when I wont to push my code my VM >> bug and I will be obliged to kill it, so I loose my code. >> >> Thank you for helping me. >> >> >

2 2

Fwd: GitHub
by hamdi gabsi Nov. 2, 2017

Nov. 2, 2017

---------- Forwarded message ---------- From: hamdi gabsi <gabsi.hamdi(a)gmail.com> Date: 2017-11-02 14:05 GMT+01:00 Subject: GitHub To: pharo-users(a)lists.pharo.org Hello, I'am Hamdi, I am doing an internship with Rmod Team. I have a problem with pushing my code in Github, In fact, Iam using Pharo 6 when I wont to push my code my VM plante and I will be obliged to kill it, so I loose my code. Thank you for helping me.

2 2

Re: [Pharo-users] Exchanging information between 2 pharo applications (2 images running on two different computers)
by Paulo R. Dellani Nov. 2, 2017

Nov. 2, 2017

Dear all, I would like to give ZeroMQ a try in Smalltalk, but am unable to load it on a new image successfully. In Pharo 5, I loaded the package ConfigurationOfZeroMQ from therepository in smalltalkhub <http://smalltalkhub.com/#%21/%7Epanuw/zeromq> and evaluated the following to load the code: ConfigurationOfZeroMQ loadBleedingEdge It seems to load everything well, but when I try to look at the source code of the methods that call the C routines from libzmq using the system browser, the system exhibits the following error message: UndefinedObject(Object)>>doesNotUnderstand: #keywords RBFFICallPragma(RBPragmaNode)>>selectorParts RubSHTextStylerST80(SHRBTextStyler)>>visitPragmaNode: RBFFICallPragma(RBPragmaNode)>>acceptVisitor: RubSHTextStylerST80(SHRBTextStyler)>>visitNode: [ :each | self visitNode: each ] in RubSHTextStylerST80>>visitMethodNode: in Block: [ :each | self visitNode: each ] OrderedCollection>>do: (its a long stack, cutting here) When loading ZeroMQ on Pharo 6, a window pops-up with the title 'Syntax Error: Literal constant expected' showing the source code of a method defining a call to a routine from a C library: apiDeleteDC: aHDC Â Â Â <apicall: Literal constant expected -> bool 'DeleteDC' (Win32HDC) module:'gdi32.dll'> Â Â Â ^self externalCallFailed If I update the syntax, re-writing the code above as apiDeleteDC: aHDC Â Â Â ^self ffiCall: #( bool DeleteDC (Win32HDC aHDC) ) module:'gdi32.dll' the compiler accepts it and the process can go on, but eventually the system will become unstable... Any ideas on how to solve this problems? Is this syntax still supported in Pharo5 & 6? Cheers, Paulo On 10/25/2017 03:47 PM, Sebastian Heidbrink via Pharo-users wrote: > ForwardedMessage.eml > > Subject: > Re: [Pharo-users] Exchanging information between 2 pharo applications > (2 images running on two different computers) > From: > Sebastian Heidbrink <sheidev(a)yahoo.de> > Date: > 10/25/2017 03:47 PM > > To: > pharo-users(a)lists.pharo.org > > > Hi Cederik, > > you should have a look at http://smalltalkhub.com/#!/~panuw/zeromq > ZeroMQ is a networking library. Nice thing about it is that all the > networking related workload is dealt with in a second process. That > can save you some resources within Smalltalk.

2 2

Pharo: Reinventing Smalltalk
by horrido Nov. 2, 2017

Nov. 2, 2017

FYI, reader comments to my interview with Stef: https://www.reddit.com/r/programming/comments/7a30vx/pharo_reinventing_smal… If you can respond, that would be great. -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

4 6

What is code 137 / how to gracefully shut down via SIGTERM?
by Herby VojÄÃk Nov. 1, 2017

Nov. 1, 2017

Hi, I had to find out how to automatically deploy the backend written in Pharo, and so far it uses docker-compose stop to stop the instance (and later docker-compose up -d to get everything up again). I noticed the stop phase takes a while and ends with status code 137. I presume it ended forcefully and not gracefully. What is the idiomatic way to wait on SIGTERM and close the process gracefully? Thanks, Herby

4 9

potentially useful diagrams
by Stephane Ducasse Nov. 1, 2017

Nov. 1, 2017

Hi during the last sprint we were brainstorming how we can help people to understand the git hub setup. I produced these two diagrams with christophe. Are they useful for you? Stef

4 4

Pharo 6.1
by ÐÐ¸ÐºÐµÐ½ÑÐ¸Ð¹ ÐÐ¾ÑÐ°Ð¿Ð¾Ð² Oct. 31, 2017

Oct. 31, 2017

I've just downloaded Pharo 6.1 from pharo.org, unzipped it and started. And i've got an error: "UTF8InvalidText: Invalid utf8 input detected" Whether i save image or not, every time i start it i get the same error. System: win 7 professional x64 on 6-core Athlon Phenom. Locale: russian (cyrillic). Can i fix it by myself or i should forget about 6.1 until global bugfix? Vikenti Potapov

7 7

Re: [Pharo-users] What is code 137 / how to gracefully shut down via SIGTERM?
by Bruce O'Neel Oct. 31, 2017

Oct. 31, 2017

Hi, Well, not so scary. Â That's the mac list. Â From a not so recent mac with Xcode 7 installed it looks like the below. The good news here is that the common signals have the same numbers. Â And how often do you get an SIGXCPU? cheers bruce #define SIGHUPÂ 1 Â Â Â /* hangup */ #define SIGINTÂ 2 Â Â Â /* interrupt */ #define SIGQUIT 3 Â Â Â /* quit */ #define SIGILLÂ 4 Â Â Â /* illegal instruction (not reset when caught) */ #define SIGTRAP 5 Â Â Â /* trace trap (not reset when caught) */ #define SIGABRT 6 Â Â Â /* abort() */ #define SIGPOLL 7 Â Â Â /* pollable event ([XSR] generated, not supported) */ #else Â /* (!_POSIX_C_SOURCE || _DARWIN_C_SOURCE) */ #define SIGIOTÂ SIGABRT /* compatibility */ #define SIGEMTÂ 7 Â Â Â /* EMT instruction */ #endifÂ /* (!_POSIX_C_SOURCE || _DARWIN_C_SOURCE) */ #define SIGFPEÂ 8 Â Â Â /* floating point exception */ #define SIGKILL 9 Â Â Â /* kill (cannot be caught or ignored) */ #define SIGBUSÂ 10Â Â Â /* bus error */ #define SIGSEGV 11Â Â Â /* segmentation violation */ #define SIGSYSÂ 12Â Â Â /* bad argument to system call */ #define SIGPIPE 13Â Â Â /* write on a pipe with no one to read it */ #define SIGALRM 14Â Â Â /* alarm clock */ #define SIGTERM 15Â Â Â /* software termination signal from kill */ #define SIGURGÂ 16Â Â Â /* urgent condition on IO channel */ #define SIGSTOP 17Â Â Â /* sendable stop signal not from tty */ #define SIGTSTP 18Â Â Â /* stop signal from tty */ #define SIGCONT 19Â Â Â /* continue a stopped process */ #define SIGCHLD 20Â Â Â /* to parent on child stop or exit */ #define SIGTTIN 21Â Â Â /* to readers pgrp upon background tty read */ #ifÂ (!defined(_POSIX_C_SOURCE) || defined(_DARWIN_C_SOURCE)) #define SIGIO Â 23Â Â Â /* input/output possible signal */ #endif #define SIGXCPU 24Â Â Â /* exceeded CPU time limit */ #define SIGXFSZ 25Â Â Â /* exceeded file size limit */ #define SIGVTALRM 26Â Â /* virtual time alarm */ #define SIGPROF 27Â Â Â /* profiling time alarm */ #ifÂ (!defined(_POSIX_C_SOURCE) || defined(_DARWIN_C_SOURCE)) #define SIGWINCH 28 Â Â /* window size changes */ #define SIGINFO 29Â Â Â /* information request */ #endif #define SIGUSR1 30Â Â Â /* user defined signal 1 */ #define SIGUSR2 31Â Â Â /* user defined signal 2 */ > Bruce O'Neel wrote: > > Hi, > > > > Posix requires that if the process is killed the return status is > > greater than 128. > > > > What is convention on linux systems is that if the process is sent a > > signal then the signal number is added to 128. Therefore 137 is SIGKILL > > (kill -9). SIGTERM is 143, SIGABRT is 134, SIGSEGV is 139, and so on. > > I've not seen an exception to this but there could be. > > > > Signals off of my closest linux system look like: > > > > #define SIGHUP 1 > > #define SIGINT 2 > > #define SIGQUIT 3 > > #define SIGILL 4 > > #define SIGTRAP 5 > > #define SIGABRT 6 > > #define SIGIOT 6 > > #define SIGBUS 7 > > #define SIGFPE 8 > > #define SIGKILL 9 > > #define SIGUSR1 10 > > #define SIGSEGV 11 > > #define SIGUSR2 12 > > #define SIGPIPE 13 > > #define SIGALRM 14 > > #define SIGTERM 15 > > Scary, because Esteban's sigtrapping package has them defined a bit > differently: > > { #category : #'class initialization' } > POSIXSignal class >> initialize [ > SIGHUP := 1. > SIGINT := 2. > SIGQUIT := 3. > SIGILL := 4. > SIGTRAP := 5. > SIGABRT := 6. > SIGPOLL := 7. > SIGIOT := SIGABRT. > SIGEMT := 7. > SIGFPE := 8. > SIGKILL := 9. > SIGBUS := 10. > SIGSEGV := 11. > SIGSYS := 12. > SIGPIPE := 13. > SIGALRM := 14. > SIGTERM := 15. > SIGURG := 16. > SIGSTOP := 17. > SIGTSTP := 18. > SIGCONT := 19. > SIGCHLD := 20. > SIGTTIN := 21. > SIGTTOU := 22. > SIGIO := 23. > SIGXCPU := 24. > SIGXFSZ := 25. > SIGVTALRM := 26. > SIGPROF := 27. > SIGWINCH := 28. > SIGINFO := 29. > SIGUSR1 := 30. > SIGUSR2 := 31. > ]

2 1