October 2017 - Pharo-users - lists.pharo.org

Re: [Pharo-users] What is code 137 / how to gracefully shut down via SIGTERM?

by Herby VojÄÃk

Esteban Lorenzano wrote: > Hi, > > I donât know if is useful in your case, but you made me remember I made > a small tool to trap unix signals within Pharo. I uploaded then to github. > > https://github.com/estebanlm/pharo-posix-signal Cannot load it. See attachment. Tried the on the current Pharo6.1-win. Herby

Oct. 31, 2017

Re: [Pharo-users] Microsoft COM

by tesonep＠gmail.com

Hi Ben, first sorry for answering late, I have seen your mail before, but the tons of mails of Pharo got over it. I will tell you the state of what I have and what maybe you will need. But, before my plan is to improve this, but as with everything it is easier to push it if I have some users. - I have implemented a way of expressing FFI calls to COM objects, I have solved all the problems of the Vtable and the different types. So it is possible to create a wrapper for any of the COM objects. I have done so for the objects used in the "reflective" API of COM. - My idea is to use the reflective API to generate automatically the Pharo Wrappers to the objects. This is nice, but if you need to use some known objects you don't need all this transparency as using known instances can be easily implemented. - I have some examples using the IE COM object as it is a nice thing to use, and also it uses many different things in the API (properties, variant, optional parameters, etc). However, the support in the Variant type is not full yet. You can receive and send variant type values, but reading the different contents is not implemented (it has like 30 different payloads in the type, I have only the basics). I have to check what I have know, because I have been working a little more, but I have to put it in Github and organize it a little. Now it is working in Pharo 6 32Bits. My plan is to first migrate it to Pharo7 also (I think it should be straight forward) and then implement it for 64 bits (this part is possible that requires a big rewritting, as the API has some changes from 32 to 64 bits). In the next days I will try to make a couple of examples to show how to map a known class. I remember that the reflective part now can query the interface and perform dynamic calls but the way of interacting with it should be improved. I really will love to have somebody using it, so I will try to help you if you (or other) has a use case. Usually having a use case is easy to move a project. Cheers, Pablo On Mon, Oct 30, 2017 at 6:11 PM, Ben Coman <btc(a)openinworld.com> wrote: > Hi Pablo, > > At work I managed to remote control Internet Explorer with Excel VBA like > this... > [1] http://www.automateexcel.com/vba/automate-internet-explorer > > and went looking for how similar might be achieved from Pharo. IIUC I > discovered this would be done via Microsoft's Component Object Model, and > then I bumped into your repo... > [2] https://github.com/tesonep/pharo-com > > Could you advise the status and your plans for this? Since I see its only > a few months old I've probably stumbled onto it prematurely, but I see no > documentation or tests to discover how to use it. So I'll curious whether > it makes something like [1] possible? And could you show how that would be > done? > > cheers -ben > > > P.S. For context, at work I automated IE since the intranet document > management system (OpenText) does authentication via a javascript function > in the browser, which doesn't compute with Microsoft's MSXML.DOMDocument > component. So I use IE to do the authentication and grab the raw XML from > IE to then stuff it into MSXML.DOMDocument from which I pull the data I > need. > > But I'd love to do it with Pharo instead (if I can get IT to white list it) > > cheers -ben > -- Pablo Tesone. tesonep(a)gmail.com

Oct. 31, 2017

Re: [Pharo-users] "sourcetrail" a code browser for C++/Java

by rainer.winkler＠poaceae.de

Hi Holger, thanks for mentioning the Software Exploration Tool Sourcetrail. I use it when I develop in C, it is now free for non commercial using. I already contactedÂ Eberhard GrÃ¤ther to discuss using Sourcetrail for other languages than C, C++ and Java. But this will probably at best take some time. So I am still using the Open Source Software Exploration Tool Moose2Model (www.moose2model.org) I developed. I use it for Smalltalk and SAP ABAP. It can be used in a similar way to Sourcetrail, but gives also the option to build commented and customized maps that can be stored and updated with new coding versions. Sourcetrail on the other hand gives much more details on the analyzed coding. I mentioned Sourcetrail in my talk at ESUG 2017 (https://www.slideshare.net/esug/do-visualizations-help-during-development-u… andÂ https://youtu.be/0ttLYM1tkek?list=PLJ5nSnWzQXi_THfKwhzxFwbXy00YTi0uv&t=1008 ) Cheers Rainer -----Original-Nachricht----- > Betreff: Pharo-users Digest, Vol 54, Issue 175 > Message: 5 > Date: Fri, 27 Oct 2017 13:11:26 +0800 > From: Holger Freyther <holger(a)freyther.de> > To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > Subject: [Pharo-users] "sourcetrail" a code browser for C++/Java > Message-ID: <30393F2B-BEC7-4FF4-AFDD-E467934D98B8(a)freyther.de> > Content-Type: text/plain; charset=us-ascii > > Hi, > > I was just watching some videos and stumbled across sourcetrail[1][2]. The visualizations look pretty neat. Maybe it can be used an inspiration? > > cheers > > Â Â Â Â Â holger > > > [1] https://www.youtube.com/watch?v=r8S6V6U5Vr4 > [2] https://www.sourcetrail.com

Oct. 31, 2017

Re: [Pharo-users] What is code 137 / how to gracefully shut down via SIGTERM?

by David T. Lewis

On Sat, Oct 28, 2017 at 01:39:56PM +0200, Herby Voj????k wrote: > 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 Try this: mySemaphore := OSProcess accessor forwardSigTerm. mySemaphore wait. "wait eg in a process until SIGTERM is detected" Typically you would use #forwardSigTerm to set up the signal handler, then start a Smalltalk process that waits on the semaphore and does whatever you want to do when the Unix signal is detected. You can do signal forwarding for any Unix signal, the #forwardSigTerm is just a convenience method. Dave

Oct. 31, 2017

Re: [Pharo-users] Pharo 6.1 - Apple signing

by Stephane Ducasse

We tried to get signing for the Pharo association but it did not work. So ZweiDenker proposed that we can use their key. Now esteban was busy with consulting for Pharo + iceberg + tonel. Stef On Tue, Oct 31, 2017 at 3:38 PM, Andrew Glynn <aglynn42(a)gmail.com> wrote: > If it would be a help, I can sign the apps. > > > > Cheers > > Andrew > > > > > > From: Todd Blanchard > Sent: Tuesday, October 31, 2017 10:36 AM > To: Any question about pharo is welcome > Subject: Re: [Pharo-users] Pharo 6.1 > > > > Actually, it is in Applications > > > > Sent from the road > > > >> On Oct 31, 2017, at 02:34, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > >> > >> > >> > >>> On 30 Oct 2017, at 20:30, Todd Blanchard <tblanchard(a)mac.com> wrote: > >>> > >>> I was just preparing a similar post. Just downloaded latest Pharo >>> 6.1-64 for Mac > >>> > >>> I was greeted with a walkback when it failed to create directory >>> /private/var/folders/ks/wg6l98bj64q6hgvs23wwqypr0000gn/T/AppTranslocation/DAA5EA3A-374D-4ADE-9E04-BBB7433BB6C8/d/Pharo6.1-64.app/Contents/Resources/pharo-local > >>> > >>> Definitely not the right directory to resolve pharo-local to. > >> > >> not related :) > >> this is because you didnât put Pharo under /Applications as indicated when >> you download Pharo. > >> at the same time, this is because we are still not signing Pharo, then >> apple moves it to a sandbox, which is bad. I have in my TODO signing the >> apps, but still no time to do it :/ > >> > >> Esteban > >> > >>> > >>> -Todd Blanchard > >>> > >>>> On Oct 30, 2017, at 12:27 PM, ÐÐ¸ÐºÐµÐ½ÑÐ¸Ð¹ ÐÐ¾ÑÐ°Ð¿Ð¾Ð² >>>> <vikenti.potapov(a)gmail.com> wrote: > >>>> > >>>> > >>>> 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 > >>>> > >>> > >>> > >> > >> > > > >

Oct. 31, 2017

Re: [Pharo-users] [Pharo-dev] [ANNOUNCE] ParrotTalk release/designchange considerations

by Andrew Glynn

Congrats :) Sent from Mail for Windows 10 From: henry Sent: Tuesday, October 31, 2017 1:56 PM To: henry Cc: Pharo-users list; Pharo Development List; Squeak-dev Subject: Re: [Pharo-users] [Pharo-dev] [ANNOUNCE] ParrotTalk release/designchange considerations I wanted to share my good news, though I have not yet gotten Pharo, Squeak and Java talking. What I was able to accomplish, after finishing the port of Cryptography's ASN1Types, Module and Streams is to get Java's rendezvous and key exchange working. After I got that connecting, I looked at the ciphers, ivSequences and MAC and got that working. In Java, I am now able to encrypt and decrypt "hello world". *Celebrates* - HH -------- Original Message -------- Subject: Re: [Pharo-users] [Pharo-dev] [ANNOUNCE] ParrotTalk release/design change considerations Local Time: October 25, 2017 12:00 PM UTC Time: October 25, 2017 4:00 PM From: henry(a)callistohouse.club To: Ben Coman <btc(a)openinworld.com>, Squeak-dev <squeak-dev(a)lists.squeakfoundation.org>, Pharo-users list <pharo-users(a)lists.pharo.org> Pharo Development List <pharo-dev(a)lists.pharo.org> I disabled vatId authorization in version 3, located in SessionOperations>>processIWant | SessionOperations>>processIAm:. I was asked to disseminate my news to Pharo Users, hello there. I was asked to describe ParrotTalk well, provide use cases and adopters of its use. Alright, I will give an attempt. ParrotTalk is an encrypted connection framework. Currently allowing anonymous 2048-bit key negotiation to establish user-provided encryption cipher and user-provided encoding and decoding, both through a provided SessionAgentMap to a starting SessionAgent server. Please look in the test case ThunkHelloWorldTest for building these maps and running a connection iwth data passing after encryption is established. There is a 4-way negotiation, from ProtocolOffered/Accepted to Go/GoToo. In using RSA 2048 signature validation and DH 2048 primes to establish the key used within the selected Cipher. The Cipher and Encoder are selected by name through the negotiation protocol. Currently three Ciphers are selectable, AESede, DESede, and DES. There are two encoders tested, asn1der, and Bytes. This protocol is described here, in this document. https://github.com/ZiroZimbarra/callistohouse/blob/master/docs/ParrotTalkFr… For as to use cases, this encrypted connection has no third party, man-in-the-middle situation by not using Certificates. As such, this is a tight implementation of NSA-proof encryption without explicit authorization beyond knowledge of a host:port. The use cases involve any communication desired to be encrypted with such high encryption. The support will last my lifetime, so we have a settled solution, here in the third version, provided here. It requires version 111 of Cryptography, as a prerequisite. Both run on Squeak and Pharo. http://www.squeaksource.com/Cryptography/Cryptography-zzz.111.mcz http://www.squeaksource.com/Cryptography/ParrotTalk-HenryHouse.3.mcz The current use is with my hubbub system, a promise-based distributed object implementation. I am working to bring ParrotTalk to Java and allow hubbub to operate interdependently between Squeak, Pharo, Java and any other languages which can support ParrotTalk and STON. My latest efforts with hubbub are to bring STON as the Layer 6 encoding. Hubbub depends on eLinda. http://www.squeaksource.com/Cryptography/elinda-HenryHouse.14.mcz http://www.squeaksource.com/Oceanside/hubbub-HenryHouse.38.mcz Hubbub currently fails to load correctly in Pharo. In Squeak the two ParrotRemoteTestCases: LookupTestCase and OperationalTestCase really screw everything up, do not save an image after running. I never run these tests until I get a better handle of serialization. Currently, do to a shift in progress to STON, the serialization tests fail, just the way we like it. Fix the tests then the system starts to work right. The shift away from vatId authorization should not adversely affect hubbub, we hope! When STON starts to work, and I think I need to turn off jsonMode, then traffic between vats can start to be analyzed and figure out how resolving is working with redirectors invoked remotely. - HH -------- Original Message -------- Subject: Re: [Pharo-dev] [ANNOUNCE] ParrotTalk release/design change considerations Local Time: October 25, 2017 12:43 AM UTC Time: October 25, 2017 4:43 AM From: btc(a)openinworld.com To: henry <henry(a)callistohouse.club>, Pharo Development List <pharo-dev(a)lists.pharo.org> Stephane Ducasse <stepharo.self(a)gmail.com> If I google... parrottalk protocol nothing seems related.Â So what is ParrotTalk?Â P.S... since this is not "part of" pharo, [pharo-users] would be a better place for discussion than [pharo-dev]. Could you re-announce there, with some description of use cases and who/where the protocol is used? cheers -ben On Wed, Oct 25, 2017 at 1:42 AM, henry <henry(a)callistohouse.club> wrote: Please excuse all the low-level detail, if inappropriate to the discussion. The protocol changes are here specified. - HH On Tue, Oct 24, 2017 at 13:40, henry <henry(a)callistohouse.club> wrote: In order to bring ParrotTalk-3.6 support, alongside historical 3.5 support, the frame header stays the same and the processing of the ProtocolOffered would select "ParrotTalk-3.6" to use the compact protocol ofÂ - ProtocolOffered { offered, preferred } - ProtocolAccepted { accepted } -Â IWant|GiveInfo|ReplyInfoÂ {Â vatId, domain, publicKey, cryptoProtocols, dataEncodersÂ } - IAm|ReplyInfoÂ { vatId, domain, publicKey, cryptoProtocol, dataEncoder, dhParamÂ } - Go {Â cryptoProtocol, dataEncoder, dhParam, signature } - GoToo { signature } Using eLinda : http://www.squeaksource.com/Cryptography/elinda-HenryHouse.14.mcz Above the FrameBuffer, below the SessionOperations for each version of the protocol, an ELindaSession could be inserted. This session think would have the stacks for each protocol version SessionOperation registered by protocol in a Tuple, for eventual callback. When the ProtocolOffered comes in we publish the tuple frame,Â with set selectedÂ version, to route to the correct SessionOperation to support each version of the protocol. With a non-specific vatId required, anonymous connections would be supported. - HH On Tue, Oct 24, 2017 at 12:52, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: Hi henry thanks for this announce. Can you tell where such protocols are used? Stef On Tue, Oct 24, 2017 at 6:33 PM, henry wrote: > Hi all, > > I am happy to announce the release of version 3.5 of ParrotTalk, for Squeak > and Pharo, found here: > > http://www.squeaksource.com/Cryptography/ParrotTalk-zzz.2.mcz > > It follows this specification: > https://github.com/ZiroZimbarra/callistohouse/blob/master/docs/ParrotTalkFr… > > One item of note, in version 3.5, the system connecting to a server, sending > the IWant msg, must know the vatId of the system being connected to. I am > considering changing this to version 3.6 by removing one round-trip in > messaging. Therefore, these messages would be combined: IWant/GiveInfo, > IAm/ReplyInfo. I will keep ProtocolOffered and ProtocolAccepted to allow > eLindaSession to support both versions: 3.5 and 3.6. > > Thoughts please? > > - HH

Oct. 31, 2017

Re: [Pharo-users] [Pharo-dev] [ANNOUNCE] ParrotTalk release/design change considerations

by henry

I wanted to share my good news, though I have not yet gotten Pharo, Squeak and Java talking. What I was able to accomplish, after finishing the port of Cryptography's ASN1Types, Module and Streams is to get Java's rendezvous and key exchange working. After I got that connecting, I looked at the ciphers, ivSequences and MAC and got that working. In Java, I am now able to encrypt and decrypt "hello world". *Celebrates* - HH > -------- Original Message -------- > Subject: Re: [Pharo-users] [Pharo-dev] [ANNOUNCE] ParrotTalk release/design change considerations > Local Time: October 25, 2017 12:00 PM > UTC Time: October 25, 2017 4:00 PM > From: henry(a)callistohouse.club > To: Ben Coman <btc(a)openinworld.com>, Squeak-dev <squeak-dev(a)lists.squeakfoundation.org>, Pharo-users list <pharo-users(a)lists.pharo.org> > Pharo Development List <pharo-dev(a)lists.pharo.org> > > I disabled vatId authorization in version 3, located in SessionOperations>>processIWant | SessionOperations>>processIAm:. > > I was asked to disseminate my news to Pharo Users, hello there. I was asked to describe ParrotTalk well, provide use cases and adopters of its use. Alright, I will give an attempt. > > ParrotTalk is an encrypted connection framework. Currently allowing anonymous 2048-bit key negotiation to establish user-provided encryption cipher and user-provided encoding and decoding, both through a provided SessionAgentMap to a starting SessionAgent server. Please look in the test case ThunkHelloWorldTest for building these maps and running a connection iwth data passing after encryption is established. There is a 4-way negotiation, from ProtocolOffered/Accepted to Go/GoToo. In using RSA 2048 signature validation and DH 2048 primes to establish the key used within the selected Cipher. The Cipher and Encoder are selected by name through the negotiation protocol. Currently three Ciphers are selectable, AESede, DESede, and DES. There are two encoders tested, asn1der, and Bytes. This protocol is described here, in this document. > > https://github.com/ZiroZimbarra/callistohouse/blob/master/docs/ParrotTalkFr… > > For as to use cases, this encrypted connection has no third party, man-in-the-middle situation by not using Certificates. As such, this is a tight implementation of NSA-proof encryption without explicit authorization beyond knowledge of a host:port. The use cases involve any communication desired to be encrypted with such high encryption. The support will last my lifetime, so we have a settled solution, here in the third version, provided here. It requires version 111 of Cryptography, as a prerequisite. Both run on Squeak and Pharo. > > http://www.squeaksource.com/Cryptography/Cryptography-zzz.111.mcz > http://www.squeaksource.com/Cryptography/ParrotTalk-HenryHouse.3.mcz > > The current use is with my hubbub system, a promise-based distributed object implementation. I am working to bring ParrotTalk to Java and allow hubbub to operate interdependently between Squeak, Pharo, Java and any other languages which can support ParrotTalk and STON. My latest efforts with hubbub are to bring STON as the Layer 6 encoding. Hubbub depends on eLinda. > > http://www.squeaksource.com/Cryptography/elinda-HenryHouse.14.mcz > http://www.squeaksource.com/Oceanside/hubbub-HenryHouse.38.mcz > > Hubbub currently fails to load correctly in Pharo. In Squeak the two ParrotRemoteTestCases: LookupTestCase and OperationalTestCase really screw everything up, do not save an image after running. I never run these tests until I get a better handle of serialization. Currently, do to a shift in progress to STON, the serialization tests fail, just the way we like it. Fix the tests then the system starts to work right. > > The shift away from vatId authorization should not adversely affect hubbub, we hope! When STON starts to work, and I think I need to turn off jsonMode, then traffic between vats can start to be analyzed and figure out how resolving is working with redirectors invoked remotely. > > - HH > >> -------- Original Message -------- >> Subject: Re: [Pharo-dev] [ANNOUNCE] ParrotTalk release/design change considerations >> Local Time: October 25, 2017 12:43 AM >> UTC Time: October 25, 2017 4:43 AM >> From: btc(a)openinworld.com >> To: henry <henry(a)callistohouse.club>, Pharo Development List <pharo-dev(a)lists.pharo.org> >> Stephane Ducasse <stepharo.self(a)gmail.com> >> >> If I google... parrottalk protocol >> nothing seems related. So what is ParrotTalk? >> >> P.S... since this is not "part of" pharo, [pharo-users] would be a better place for discussion than [pharo-dev]. >> Could you re-announce there, with some description of use cases and who/where the protocol is used? >> >> cheers -ben >> >> On Wed, Oct 25, 2017 at 1:42 AM, henry <henry(a)callistohouse.club> wrote: >> >>> Please excuse all the low-level detail, if inappropriate to the discussion. The protocol changes are here specified. >>> >>> - HH >>> >>> On Tue, Oct 24, 2017 at 13:40, henry <henry(a)callistohouse.club> wrote: >>> >>>> In order to bring ParrotTalk-3.6 support, alongside historical 3.5 support, the frame header stays the same and the processing of the ProtocolOffered would select "ParrotTalk-3.6" to use the compact protocol of >>>> >>>> - ProtocolOffered { offered, preferred } >>>> - ProtocolAccepted { accepted } >>>> - IWant|GiveInfo|ReplyInfo { vatId, domain, publicKey, cryptoProtocols, dataEncoders } >>>> - IAm|ReplyInfo { vatId, domain, publicKey, cryptoProtocol, dataEncoder, dhParam } >>>> - Go { cryptoProtocol, dataEncoder, dhParam, signature } >>>> - GoToo { signature } >>>> >>>> Using eLinda : >>>> >>>> http://www.squeaksource.com/Cryptography/elinda-HenryHouse.14.mcz >>>> >>>> Above the FrameBuffer, below the SessionOperations for each version of the protocol, an ELindaSession could be inserted. This session think would have the stacks for each protocol version SessionOperation registered by protocol in a Tuple, for eventual callback. When the ProtocolOffered comes in we publish the tuple frame, with set selected version, to route to the correct SessionOperation to support each version of the protocol. >>>> >>>> With a non-specific vatId required, anonymous connections would be supported. >>>> >>>> - HH >>>> >>>> On Tue, Oct 24, 2017 at 12:52, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: >>>> >>>>> Hi henry thanks for this announce. Can you tell where such protocols are used? Stef On Tue, Oct 24, 2017 at 6:33 PM, henry wrote: > Hi all, > > I am happy to announce the release of version 3.5 of ParrotTalk, for Squeak > and Pharo, found here: > > http://www.squeaksource.com/Cryptography/ParrotTalk-zzz.2.mcz > > It follows this specification: > https://github.com/ZiroZimbarra/callistohouse/blob/master/docs/ParrotTalkFr… > > One item of note, in version 3.5, the system connecting to a server, sending > the IWant msg, must know the vatId of the system being connected to. I am > considering changing this to version 3.6 by removing one round-trip in > messaging. Therefore, these messages would be combined: IWant/GiveInfo, > IAm/ReplyInfo. I will keep ProtocolOffered and ProtocolAccepted to allow > eLindaSession to support both versions: 3.5 and 3.6. > > Thoughts please? > > - HH

Oct. 31, 2017

Re: [Pharo-users] What is code 137 / how to gracefully shut down via SIGTERM?

by Herby VojÄÃk

Bruce O'Neel wrote: > 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? I was think of SIGUSR1, can be used to useful things (IIRC nginx or apache reload when sent), but that one is not common. :-( Of course, SIGTERM/SIGINT/SIGHUP are, so, yes, these are most important. Herby > 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() */ > > #if (defined(_POSIX_C_SOURCE) && !defined(_DARWIN_C_SOURCE)) > > #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 */ > > #define SIGTTOU 22 /* like TTIN for output if (tp->t_local&LTOSTOP) */ > > #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 */ > > > /31 October 2017 14:56 Herby VojÄÃk <herby(a)mailbox.sk> wrote:/ > > 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. > ] > > >

Oct. 31, 2017

Failure with ZdcPluginSSLSession on latest Pharo 32 bit/Win

by Raffaello Giulietti

Hi Pharo 32 bit/Win users, I'm on the latest stock Pharo 32 bit/Win downloaded from http://files.pharo.org/platform/Pharo6.1-win.zip which contains the latest 60518 image. When evaluating Metacello new smalltalkhubUser: 'Moose' project: 'GToolkit'; configuration: 'GToolkit'; version: #development; load. I get an exception roughly stating: PrimitiveFailed: primitive #primitiveSSLCreate in ZdcPluginSSLSession failed I cross-checked the presence of all the .dlls in the Pharo6.1 folder, they are all there, including SqueakSSL and ssleay32. Anybody experiencing similar problems? Any idea on how to overcome it or on how to dive deeper? Greetings Raffaello

Oct. 31, 2017

potentially useful diagrams

by Stephane Ducasse

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

Oct. 31, 2017

Re: [Pharo-users] Pharo 6.1

by Marcus Denker

What actually happens is that moving (with the finder) a file to /Applications removes the com.apple.quarantine flag. you could try: xattr -d com.apple.quarantine <file> (this is related to signing, too, but not the signing of the app, but the container the files are downloaded. We need to use .dmg files and sign them on the build server). Marcus > On 31 Oct 2017, at 15:35, Todd Blanchard <tblanchard(a)mac.com> wrote: > > Actually, it is in Applications > > Sent from the road > >> On Oct 31, 2017, at 02:34, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> >> >> >>> On 30 Oct 2017, at 20:30, Todd Blanchard <tblanchard(a)mac.com> wrote: >>> >>> I was just preparing a similar post. Just downloaded latest Pharo 6.1-64 for Mac >>> >>> I was greeted with a walkback when it failed to create directory /private/var/folders/ks/wg6l98bj64q6hgvs23wwqypr0000gn/T/AppTranslocation/DAA5EA3A-374D-4ADE-9E04-BBB7433BB6C8/d/Pharo6.1-64.app/Contents/Resources/pharo-local >>> >>> Definitely not the right directory to resolve pharo-local to. >> >> not related :) >> this is because you didnât put Pharo under /Applications as indicated when you download Pharo. >> at the same time, this is because we are still not signing Pharo, then apple moves it to a sandbox, which is bad. I have in my TODO signing the apps, but still no time to do it :/ >> >> Esteban >> >>> >>> -Todd Blanchard >>> >>>> On Oct 30, 2017, at 12:27 PM, ÐÐ¸ÐºÐµÐ½ÑÐ¸Ð¹ ÐÐ¾ÑÐ°Ð¿Ð¾Ð² <vikenti.potapov(a)gmail.com> wrote: >>>> >>>> >>>> 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 >>>> >>> >>> >> >> >

Oct. 31, 2017

Re: [Pharo-users] Pharo 6.1 - Apple signing

by Andrew Glynn

If it would be a help, I can sign the apps. Cheers Andrew From: Todd Blanchard Sent: Tuesday, October 31, 2017 10:36 AM To: Any question about pharo is welcome Subject: Re: [Pharo-users] Pharo 6.1 Actually, it is in Applications Sent from the road > On Oct 31, 2017, at 02:34, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > > >> On 30 Oct 2017, at 20:30, Todd Blanchard <tblanchard(a)mac.com> wrote: >> >> I was just preparing a similar post. Just downloaded latest Pharo 6.1-64 for Mac >> >> I was greeted with a walkback when it failed to create directory /private/var/folders/ks/wg6l98bj64q6hgvs23wwqypr0000gn/T/AppTranslocation/DAA5EA3A-374D-4ADE-9E04-BBB7433BB6C8/d/Pharo6.1-64.app/Contents/Resources/pharo-local >> >> Definitely not the right directory to resolve pharo-local to. > > not related :) > this is because you didnât put Pharo under /Applications as indicated when you download Pharo. > at the same time, this is because we are still not signing Pharo, then apple moves it to a sandbox, which is bad. I have in my TODO signing the apps, but still no time to do it :/ > > Esteban > >> >> -Todd Blanchard >> >>> On Oct 30, 2017, at 12:27 PM, ÐÐ¸ÐºÐµÐ½ÑÐ¸Ð¹ ÐÐ¾ÑÐ°Ð¿Ð¾Ð² <vikenti.potapov(a)gmail.com> wrote: >>> >>> >>> 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 >>> >> >> > >

Oct. 31, 2017

Re: [Pharo-users] What is code 137 / how to gracefully shut down via SIGTERM?

by Bruce O'Neel

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. > ]

Oct. 31, 2017

Re: [Pharo-users] Pharo 6.1

by Todd Blanchard

Actually, it is in Applications Sent from the road > On Oct 31, 2017, at 02:34, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > > >> On 30 Oct 2017, at 20:30, Todd Blanchard <tblanchard(a)mac.com> wrote: >> >> I was just preparing a similar post. Just downloaded latest Pharo 6.1-64 for Mac >> >> I was greeted with a walkback when it failed to create directory /private/var/folders/ks/wg6l98bj64q6hgvs23wwqypr0000gn/T/AppTranslocation/DAA5EA3A-374D-4ADE-9E04-BBB7433BB6C8/d/Pharo6.1-64.app/Contents/Resources/pharo-local >> >> Definitely not the right directory to resolve pharo-local to. > > not related :) > this is because you didnât put Pharo under /Applications as indicated when you download Pharo. > at the same time, this is because we are still not signing Pharo, then apple moves it to a sandbox, which is bad. I have in my TODO signing the apps, but still no time to do it :/ > > Esteban > >> >> -Todd Blanchard >> >>> On Oct 30, 2017, at 12:27 PM, ÐÐ¸ÐºÐµÐ½ÑÐ¸Ð¹ ÐÐ¾ÑÐ°Ð¿Ð¾Ð² <vikenti.potapov(a)gmail.com> wrote: >>> >>> >>> 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 >>> >> >> > >

Oct. 31, 2017

Re: [Pharo-users] What is code 137 / how to gracefully shut down via SIGTERM?

by Herby VojÄÃk

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. ]

Oct. 31, 2017

Re: [Pharo-users] What is code 137 / how to gracefully shut down via SIGTERM?

by Bruce O'Neel

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 SIGHUP is the phone hung up. Â SIGINT is interrupt (^C) SIGILL is you tried to execute an illegal instruction, SIGBUS is Bus error, normally you tried to read a 32 bit value on a non-32 bit boundary and uncommon on x86, SIGFPE is a floating point error, SIGKILL is too bad, you're dead, SIGSEGV is you tried to read/write memory that was not allowed, and SIGTERM is the normal "please exit" signal. cheers bruce > werner kassens wrote: > > Hi Herby, > > eventually you might want to look at > > https://github.com/moby/moby/issues/1063 > > but then i dont know anything about these things. > > Hopefully they have this solved already... but I learned 137 means > "killed". generally; did not know. :-) > > > werner > > Herby Hi,

Oct. 31, 2017

Re: [Pharo-users] Smalltalk Argument

by Hans

Hi all, an argument for Smalltalk, an discussion coming up many times in my history. It is also something I'm asking myself from time to time. It is very actual in the moment. Many good arguments were mentioned this discussion. I want to provide you my 2 cents on this. First, I'm taking the view of an hobby enthusiast. That's were I started. All the time I was excited by the Smalltalk concept. Live debugging, VM system, the possibility to look at and understand every code from systems completely new to me was so great. No installation, and nice people in the community. Conclusion: I want to do all in Smalltalk. Elegance is what rules only. Now, I'm in the perspective of an employed software developer. Everywhere that crazy C++, sometimes Fortran or C. Delphi. The people told "that's old, that was the beginning years ago, that is given, we have nothing else". And we have no time to redesign or port to something better, so fate catched us and we have to continue on the road to hell..... Most of my life colleagues were physicists who learned C++ for its thesis, or engineers of the embedded domain. No or only a few computer scientists. The rule now on these days: get ready, it should work somehow, costs. Elegance or sound design is no value. Not at this time. SW is just a part of my component as any screw and nail too. Continuing as a team leader. My goal is to fit budget. I have some time, and I have some people in the team. And I have to report and sell to my manager above me. I'm looking for get the job done, but I have also some strategic view. I've read some articles about this new .Net, with big potential, many libraries. Easy Web. Web is the future. I ask my team how to solve the task. Ony guy talks about Pearl. I hat Pearl. Another colleagues tells something about Smalltalk. Never heared of it, I ask if this is compatible to .Net.... My rules of success are in what I belief - and what can I sell to my big boss. And I belief only what I see... I could continue this. My point is: the Smalltalk Argument is depending on the perspective. And therefore, to communicate and argue about Smalltalk is what the receiver of the argument needs. Superiour technique can be an argument, but not always. Missing developer can be an argument, but not in every company and every project. My personal conclusion and look to Smalltalk is this: - for my soul which want to bring science and technology to the future, I look at the elegance and power of Smalltalk. That's why I'm looking at TeaTime and OpenCroquet again in the age of AR. - if I want to learn from top coders, the way of developing in Smalltalk (live debugging) - if I want to get a job done (for example a web site), I'm looking what the world offers me. And it may not be Smalltalk. In my current work, Game Engines matter. So coding a Game Engine in Smalltalk ? May be, but there are a lot of good products already... Having said that, the Smalltalk Argument has to sides, and they have both their value: - Smalltalk as an technique, as a matter of research and getting things better, an philosophy - Smalltalk as a product for people who want things get done. My personal opinion is that sometimes the point Smalltalk (or better now: Pharo) as a product is not so much in concern as it could. Pharo evolved wonderfully, the consortium and the organisation and the community have the right direction, yes. But as an industrial user of software I only can hope: keep the Smalltalk as a Product in the same focus as Smalltalk as the better technology. And product means: look at the needs the product is indented for, look at the "market". What are the problems out there ? If you can fit the needs, and provide a productive and integrable technology, you need no argument for Smalltalk. Off topic: thanks for the big effort of the community, it is really really fun today to work on and with Pharo. Much happend, and much is possible ;) Cheers Hans -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Oct. 31, 2017

Re: [Pharo-users] Smalltalk Argument

by Hans

Hi all, an argument for Smalltalk, an discussion coming up many times in my history. It is also something I'm asking myself from time to time. It is very actual in the moment. Many good arguments were mentioned this discussion. I want to provide you my 2 cents on this. First, I'm taking the view of an hobby enthusiast. That's were I started. All the time I was excited by the Smalltalk concept. Live debugging, VM system, the possibility to look at and understand every code from systems completely new to me was so great. No installation, and nice people in the community. Conclusion: I want to do all in Smalltalk. Elegance is what rules only. Now, I'm in the perspective of an employed software developer. Everywhere that crazy C++, sometimes Fortran or C. Delphi. The people told "that's old, that was the beginning years ago, that is given, we have nothing else". And we have no time to redesign or port to something better, so fate catched us and we have to continue on the road to hell..... Most of my life colleagues were physicists who learned C++ for its thesis, or engineers of the embedded domain. No or only a few computer scientists. The rule now on these days: get ready, it should work somehow, costs. Elegance or sound design is no value. Not at this time. SW is just a part of my component as any screw and nail too. Continuing as a team leader. My goal is to fit budget. I have some time, and I have some people in the team. And I have to report and sell to my manager above me. I'm looking for get the job done, but I have also some strategic view. I've read some articles about this new .Net, with big potential, many libraries. Easy Web. Web is the future. I ask my team how to solve the task. Ony guy talks about Pearl. I hat Pearl. Another colleagues tells something about Smalltalk. Never heared of it, I ask if this is compatible to .Net.... My rules of success are in what I belief - and what can I sell to my big boss. And I belief only what I see... I could continue this. My point is: the Smalltalk Argument is depending on the perspective. And therefore, to communicate and argue about Smalltalk is what the receiver of the argument needs. Superiour technique can be an argument, but not always. Missing developer can be an argument, but not in every company and every project. My personal conclusion and look to Smalltalk is this: - for my soul which want to bring science and technology to the future, I look at the elegance and power of Smalltalk. That's why I'm looking at TeaTime and OpenCroquet again in the age of AR. - if I want to learn from top coders, the way of developing in Smalltalk (live debugging) - if I want to get a job done (for example a web site), I'm looking what the world offers me. And it may not be Smalltalk. In my current work, Game Engines matter. So coding a Game Engine in Smalltalk ? May be, but there are a lot of good products already... Having said that, the Smalltalk Argument has to sides, and they have both their value: - Smalltalk as an technique, as a matter of research and getting things better, an philosophy - Smalltalk as a product for people who want things get done. My personal opinion is that sometimes the point Smalltalk (or better now: Pharo) as a product is not so much in concern as it could. Pharo evolved wonderfully, the consortium and the organisation and the community have the right direction, yes. But as an industrial user of software I only can hope: keep the Smalltalk as a Product in the same focus as Smalltalk as the better technology. And product means: look at the needs the product is indented for, look at the "market". What are the problems out there ? If you can fit the needs, and provide a productive and integrable technology, you need no argument for Smalltalk. Off topic: thanks for the big effort of the community, it is really really fun today to work on and with Pharo. Much happend, and much is possible ;) Cheers Hans -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Oct. 31, 2017

Re: [Pharo-users] Pharo 6.1

by Esteban Lorenzano

> On 30 Oct 2017, at 20:30, Todd Blanchard <tblanchard(a)mac.com> wrote: > > I was just preparing a similar post. Just downloaded latest Pharo 6.1-64 for Mac > > I was greeted with a walkback when it failed to create directory /private/var/folders/ks/wg6l98bj64q6hgvs23wwqypr0000gn/T/AppTranslocation/DAA5EA3A-374D-4ADE-9E04-BBB7433BB6C8/d/Pharo6.1-64.app/Contents/Resources/pharo-local > > Definitely not the right directory to resolve pharo-local to. not related :) this is because you didnât put Pharo under /Applications as indicated when you download Pharo. at the same time, this is because we are still not signing Pharo, then apple moves it to a sandbox, which is bad. I have in my TODO signing the apps, but still no time to do it :/ Esteban > > -Todd Blanchard > >> On Oct 30, 2017, at 12:27 PM, ÐÐ¸ÐºÐµÐ½ÑÐ¸Ð¹ ÐÐ¾ÑÐ°Ð¿Ð¾Ð² <vikenti.potapov(a)gmail.com> wrote: >> >> >> 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 >> > >

Oct. 31, 2017

Re: [Pharo-users] QCMagritte on Github

by laurent

Hi Diego, we used this process to migrate: https://github.com/peteruhnak/git-migration. So we have all history of QCMagritte (including ConfigurationOf). We created the BaselineOf but it only loads latest packages (see https://github.com/Afibre/QCMagritte/blob/master/src/BaselineOfQCMagritte.p… ). So there should be made branches for the different Pharo versions. If you give me your github I can give you write access to the github repository. Laurent Le dim. 29 oct. 2017 Ã 13:42, Diego Lont <diego.lont(a)delware.nl> a Ã©crit : > Hi, > > It was somewhere on my todo list to migrate to Github, but not very > highâ¦ > > but I guess if someone else does this for me, I should be happy about > this. > > So thank you, I will look up my gut hub account and also change the > job. I hope to do this somewhere next week. > > I know there a different configurations for different versions of > pharo, so did you import only one version, or should there be made > branches for the different pharo version? > > Regards, > Diego > >> On 27 Oct 2017, at 16:50, laurent laffont >> <laurent.laffont(a)gmail.com> wrote: >> >> I've added loading instructions in README: >> >> Metacello new >> githubUser: 'Afibre' project: 'QCMagritte' commitish: 'master' >> path: 'src'; >> baseline: 'QCMagritte'; >> load. >> >> >> For the QCMagritte version, there's actually one branch master. If >> you >> need a previous version, I suppose the right way is to create a >> github >> branch from the desired commit in git history and adapt the >> BaselineOf... >> >> Laurent >> >> On Fri, Oct 27, 2017 at 2:12 PM, HernÃ¡n Morales Durand >> <hernan.morales(a)gmail.com> wrote: >>> Nice to know Laurent, >>> >>> Could you please comment or share how to install this version >>> uploaded >>> to GitHub? >>> Any way to check the installed or current QCMagritte version? >>> >>> Cheers, >>> >>> HernÃ¡n >>> >>> >>> >>> >>> 2017-10-27 7:39 GMT-03:00 laurent laffont >>> <laurent.laffont(a)gmail.com>: >>>> Hi, >>>> >>>> my team starts to use QCMagritte. For our needs we have imported >>>> SmalltalkHub repository to Github here: >>>> https://github.com/Afibre/QCMagritte >>>> >>>> I don't know if you (Diego, Stephan, Tobias) plan to use Github >>>> instead of SmalltalkHub. At least Github allows branches & pull >>>> request. >>>> >>>> Regards, >>>> >>>> Laurent Laffont >>>> >>> >> > >

Oct. 31, 2017

Re: [Pharo-users] UK Smalltalk User Group Meeting - Monday, October 30th - PharoLambda: Smalltalk running serverless on AWS

by Tim Mackinnon

I promised to give a little summary of the meetup. After some initial âsmalltalkâ (in the talking sense - where we covered chrome books, cloud development, squeakjs and how you might develop in smalltalk on a Chromebook in a web worldâ¦. I did say smalltalk right)â¦. I did a quick intro to the components of writing a traditional Alexa Skill and Lambda functions on AWS using Node JSâ¦ this wasnât Smalltalk related but it set the context of what the environment is like and was quite interesting to the group to give some some background. We had some interesting side conversations on the social aspects of having a device like an Echo Dot in your living room (is it like the revolution weâve had with phones? Does it feel natural etc). Some interesting debate on this. Then we covered how the recentâish advancement with an OpenSmalltalk 64bit vm have given the ability to easily run Smalltalk no Lambda where you donât have a lot of control on what is installed on your target instance (essentially you upload a zip file of your environment) We then walked through the GitLab CI/build system I used to automatically create a zip file to upload (the minimal image work done here was the power behind this - and GitLab ci is quite a nice build system that is fast/efficient and simple to use). Then the real eye-opener was looking at the small amount of code needed to create a service (not so amazing actually) - but the kicker being the implications of how you can easily debug a failed service. This got the conversation flowing. The 2 interesting points that came out: - restarting a failed service (and being able to keep restarting it in a debugger) is neat - but services often have other elements like a database or other service that also need rewinding. Given the tiny amount of code that I showed that serialises the context to S3 (again, sponsored by this community - thanks) its not unimaginable to snapshot a database and be able to restore it when you dematerialise your execution context (and also do it again if you decide to restart again). These are things developers in other communities donât even dream of doing it seems. (As a side point - how hard would it be for our debugger to truly let you rewind memory when you step back in the stack?) - AWS feels like a new operating system. And just like we handle restoring windows and other resources on an OS like windows - should we be viewing AWS as a similar thing we should run on (albeit in a slightly different way). But can our tooling/environment make for a more pleasant and cohesive view on top of a cloud OS? It feels like it could somehow. - Another side point - I recall early demos of IBM distributed smalltalk where you could literally highlight nodes of execution that were slow because they were far apart and just drag them near to each other so that message calls didnât have the same network latency. This feels like the new cloud world might benefit from some of these old ideasâ¦ not sure if there are any video of this in action to inspire people. Anyway - not sure if any of this is useful to anyone reading, but it may be a reminder to me of things to follow up on. Tim > On 27 Oct 2017, at 17:58, Tim Mackinnon <tim(a)testit.works> wrote: > > Thanks Sean - hoping to do a bit of deeper dive into the Screencast I posted a while back - but Iâm also hoping we can get some discussion around the kinds of things we can do with serverless that match the strengths of Smalltalk. > > Iâve got a few ideas - but wondering what others think - and weâll share the results here. > > Tim > > NOTE for anyone that is coming and is reading this: Weâve had to change the venue to the pub around the corner - The Crown Tavern. > >> On 27 Oct 2017, at 16:31, Sean P. DeNigris <sean(a)clipperadams.com> wrote: >> >> Tim Mackinnon wrote >>> Tim Mackinnon will showâ¦ >> >> So jealous! That sounds like an awesome presentation :) >> >> >> >> ----- >> Cheers, >> Sean >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >> > >

Oct. 31, 2017

Re: [Pharo-users] Pharo 6.1

by Ben Coman

On Tue, Oct 31, 2017 at 3:27 AM, ÐÐ¸ÐºÐµÐ½ÑÐ¸Ð¹ ÐÐ¾ÑÐ°Ð¿Ð¾Ð² <vikenti.potapov(a)gmail.com > wrote: > > 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 > > I downloaded yesterday and again just now and no problem unzipping and running. URL: http://files.pharo.org/platform/Pharo6.1-win.zip System: Win 10 Professional x64 What folder do you unzip into? Does it contain any non-ASCII characters? Double check copy-pasting into somewhere like http://asciivalue.com/ Could you create folder C:\Pharo ensuring all ASCII characters, and try unzipping into there? cheers -ben

Oct. 31, 2017

Re: [Pharo-users] Pharo 6.1

by Todd Blanchard

I was just preparing a similar post. Just downloaded latest Pharo 6.1-64 for Mac I was greeted with a walkback when it failed to create directory /private/var/folders/ks/wg6l98bj64q6hgvs23wwqypr0000gn/T/AppTranslocation/DAA5EA3A-374D-4ADE-9E04-BBB7433BB6C8/d/Pharo6.1-64.app/Contents/Resources/pharo-local Definitely not the right directory to resolve pharo-local to. -Todd Blanchard > On Oct 30, 2017, at 12:27 PM, ÐÐ¸ÐºÐµÐ½ÑÐ¸Ð¹ ÐÐ¾ÑÐ°Ð¿Ð¾Ð² <vikenti.potapov(a)gmail.com> wrote: > > > 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 >

Oct. 30, 2017

Pharo 6.1

by ÐÐ¸ÐºÐµÐ½ÑÐ¸Ð¹ ÐÐ¾ÑÐ°Ð¿Ð¾Ð²

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

Oct. 30, 2017

Microsoft COM

by Ben Coman

Hi Pablo, At work I managed to remote control Internet Explorer with Excel VBA like this... [1] http://www.automateexcel.com/vba/automate-internet-explorer and went looking for how similar might be achieved from Pharo. IIUC I discovered this would be done via Microsoft's Component Object Model, and then I bumped into your repo... [2] https://github.com/tesonep/pharo-com Could you advise the status and your plans for this? Since I see its only a few months old I've probably stumbled onto it prematurely, but I see no documentation or tests to discover how to use it. So I'll curious whether it makes something like [1] possible? And could you show how that would be done? cheers -ben P.S. For context, at work I automated IE since the intranet document management system (OpenText) does authentication via a javascript function in the browser, which doesn't compute with Microsoft's MSXML.DOMDocument component. So I use IE to do the authentication and grab the raw XML from IE to then stuff it into MSXML.DOMDocument from which I pull the data I need. But I'd love to do it with Pharo instead (if I can get IT to white list it) cheers -ben

Oct. 30, 2017