- Pharo-users - lists.pharo.org

Sending email

by Jeff Gray

Hi all, I can use the ZdcSecureSMTPClient to send emails from a Gmail account but I have tried to do the same from a Microsoft live account without success. It times out on the connection. Do I just need to work out what's wrong or is there an easier, better way to send mails from a pharo application? -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Sept. 20, 2018

Sending emails

by Jeff Gray

Hi all, I can use the ZdcSecureSMTPClient to send emails from a Gmail account but I have tried to do the same from a Microsoft live account without success. It times out on the connection. Do I just need to work out what's wrong or is there an easier, better way to send mails from a pharo application? -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Sept. 20, 2018

Re: [Pharo-users] Pharo 6 snap package

by Offray Vladimir Luna CÃ¡rdenas

Hi, Another project that have save us from installation pains on several heterogeneous environments while giving workshops (including machines with several Linux flavors and Mac OS X, but not Windows) is Nix[1]. There is even a package for Pharo[2]. [1] https://nixos.org/nix/ [2] https://nixos.org/releases/tmp/release-nixos-unstable-small/nixos-18.09pre1… Cheers, Offray On 9/7/18 10:07 AM, Guillermo Polito wrote: > Hi all, > > Nope, I'm not maintaining my package. I was experimenting with it at > some point (2 years ago?) and then saw somebody else started with a > more complete solution so I've not continued working on it. > > Personally, I've experienced the same sandboxing problems stated by > Alistair, plus the fact that at that moment Snap was not working in > *nixes other than Ubuntu made me put my energy somewhere else. > > Three points more: > Â - for those that do not know exactly what we are talking about, snap > is "new" a packaging tool used in ubuntu. I strongly believe that we > could use some kind of tool like this for the VM, but not for image > (which are mutable). > Â - it could maybe make more sense to package the pharo launcher? ;) > Â - rather than snaps, I'd put my 2cents on a solution > likeÂ https://github.com/probonopd/appimagekit/. I've been following it > for two years and it has a lot of movement and getting mature. > > On Fri, Aug 24, 2018 at 6:18 PM Alistair Grant <akgrant0710(a)gmail.com > <mailto:akgrant0710@gmail.com>> wrote: > > Hi Hannes, > > On Fri, 24 Aug 2018 at 06:36, H. Hirzel <hannes.hirzel(a)gmail.com > <mailto:hannes.hirzel@gmail.com>> wrote: > > > > Hello Alistair > > > > Thank you for the detailed answer. I understand that at the moment > > going for a Pharo snap package does not seem to be useful. > > > > In particular as a Pharo installation may reside in a directory with > > everything included. > > So different Pharo installations may reside in different > directories. > > Yep.Â Especially if using the in-development version of Pharo > (currently 7), I find it useful to pair images and VMs. > > > > I think where snap still might come is for solutions which require > > more than a particular Pharo installation. > > > > For example I could think of combining a particular Pharo > version with > > a particular Jupyter notebook installation into a snap which could > > lead to aÂ web based 'Dynabook' solution. > > That was one of the things that attracted me to snaps originally, I > use sqlite in my daily environment, so included it in the Pharo snap. > > > > I am also looking forward to Guille's answer. > > +1. > > Cheers, > Alistair > > > > Regards > > Hannes > > > > On 8/23/18, Alistair Grant <akgrant0710(a)gmail.com > <mailto:akgrant0710@gmail.com>> wrote: > > > Hi Hannes, > > > > > > On Wed, 22 Aug 2018 at 17:20, H. Hirzel > <hannes.hirzel(a)gmail.com <mailto:hannes.hirzel@gmail.com>> wrote: > > >> > > >> Hello > > >> > > >> Are there plans to do a Pharo 6.1Â snap package in the upcoming > > >> months? (Ubuntu 18.04.1) > > > > > > I haven't been thinking about it really, because: > > > > > > - The big attraction for me was the ability to easily run 32 > bit Pharo > > > on a 64 bit OS without installing all the dependencies.Â But > now that > > > 64 bit Pharo is stable that driver has largely gone. > > > - The sandboxing is quite limiting for a development > environment, so > > > if you want to run commands on the localhost you end up doing > > > something like ssh'ing the command to localhost. > > > - The snap runtime environment is still quite immature - I've > had to > > > deal with bugs in snapd, the gtk desktop interface, loading 32 bit > > > executables, etc. > > > - The snapcraft build environment is still evolving, so I have > to keep > > > up with the changes. > > > - I was originally compiling the 32 and 64 bit VMs as part of the > > > build process, but that is problematic as the 32 and 64 bit > libraries > > > tend to interfere with each other making the build process > unstable. > > > - You can't run multiple versions of a snap on one system, e.g. we > > > can't have Pharo 6 and Pharo 7 installed simultaneously under > the one > > > snap name (pharo).Â I tried to register Pharo7 so pharo could > be the > > > GA version (6), but never got a response. > > > > > > I was listening to an Ubuntu podcast just this week where one > of the > > > hosts tried installing 4 packages via snaps and ended up going > back to > > > debian packages for 3 of the packages due to problems, so it > obviously > > > still isn't mature. > > > > > > I realise that every software package has its own issues, I'm sure > > > someone from the snap community could find parallel issues > with Pharo, > > > but it wasn't where I wanted to be spending all my time. > > > > > > If someone wants to take it over, I'm more than happy to pass > it on > > > (although it isn't building at the moment due to changes in > > > snapcraft). > > > > > > If there is enough interest I'll try and update it to run > Pharo 6.1. > > > > > > If Guille is actively maintaining his package, maybe we should > move to > > > that (I haven't looked at it). > > > > > > Cheers, > > > Alistair > > > > -- > > Â Â Â > > > > Guille Polito > > Research Engineer > > Centre de Recherche en Informatique, Signal et Automatique de Lille > > CRIStAL - UMR 9189 > > French National Center for Scientific Research - _http://www.cnrs.fr_ > > > *Web:* _http://guillep.github.io_ > > *Phone: *+33 06 52 70 66 13 >

Sept. 20, 2018

Re: [Pharo-users] Query on Pharo syntax

by Offray Vladimir Luna CÃ¡rdenas

I learned something for sure from this exchange. Thanks Peter and Ben for this public conversation. Cheers, Offray On 9/10/18 7:56 PM, Ben Coman wrote: > Its a very interesting and elegant aspect of PharoÂ > and I'm sure there are others at different parts of their journey > learning Pharo > who learnt something new from your question.Â > > cheers -ben > > On Tue, 11 Sep 2018 at 03:13, PBKResearch <peter(a)pbkresearch.co.uk > <mailto:peter@pbkresearch.co.uk>> wrote: > > Thanks Ben â itâs all clear now. Thanks also to Esteban, who > spared my blushes by answering direct! > > Peter Kenny > > Â > > *From:*Pharo-users <pharo-users-bounces(a)lists.pharo.org > <mailto:pharo-users-bounces@lists.pharo.org>> *On Behalf Of *Ben Coman > *Sent:* 10 September 2018 19:56 > *To:* Any question about pharo is welcome > <pharo-users(a)lists.pharo.org <mailto:pharo-users@lists.pharo.org>> > *Subject:* Re: [Pharo-users] Query on Pharo syntax > > Â > > Â > > On Tue, 11 Sep 2018 at 02:44, PBKResearch <peter(a)pbkresearch.co.uk > <mailto:peter@pbkresearch.co.uk>> wrote: > > Hi All > > Â > > This is an idiot question, I should know the answer, but I > have looked around and canât find relevant documentation. Iâm > not asking for a full answer, just a pointer as to where to > start looking. > > Â > > I have seen from examples in this forum that an expression > like the following: > > Â > > paras collect: [para| para prettyPrinted] > > Â > > can be written more concisely as: > > Â > > paras collect: #prettyPrinted > > Â > > which obviously works when I try it. It doesnât seem to fit in > with the definition of #collect:, which requires a block as > argument. Where can I find the relevant definition, either in > method comments or in some general manual? Can the notation be > extended, > > Â > > Its not special notation.Â Just a normal object (a Symbol) passed > via a normal message. > > Â > > for example to #select: - obviously with an argument which > returns a Boolean? Can it be used with a method which requires > an argument, e.g. as myArray collect: (#myMethod: arg)? Are > there any other extensions? > > Â > > Any help gratefully received. > > Â > > Peter Kenny > > Â > > Full answer ;) > > Its a combination of the following two methods... > > Â > > Collection >> collect: aBlockÂ > > Â Â Â Â Â Â Â Â Â Â Â Â Â Â | newCollection | > > Â Â Â Â Â Â Â Â Â Â Â Â Â Â newCollection := self species new. > > Â Â Â Â Â Â Â Â Â Â Â Â Â Â self do: [:each | newCollection add: (aBlock value: > each)]. > > Â Â Â Â Â Â Â Â Â Â Â Â Â Â ^ newCollectionÂ > > Â > > Symbol value: anObjectÂ > > Â Â Â Â Â Â Â Â Â Â Â Â Â Â ^anObject perform: self. > > Â > > When /aBlock/ is a symbol, that symbol is performed on /each/ element. > > And looking atÂ #select:Â , yes it works the same...Â > > Â > > Collection >> select: aBlockÂ > > Â Â Â Â Â Â Â Â Â Â Â Â Â Â | newCollection | > > Â Â Â Â Â Â Â Â Â Â Â Â Â Â newCollection := self copyEmpty. > > Â Â Â Â Â Â Â Â Â Â Â Â Â Â self do: [ :each |Â > > Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â (aBlock value: each)Â > > Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â ifTrue: [ > newCollection add: each ]]. > > Â Â Â Â Â Â Â Â Â Â Â Â Â Â ^newCollection > > Â > > cheers -ben >

Sept. 20, 2018

TextEditor

by Hilaire

Hello, How can I get a text editor window? I can't make sense of the TextEditor class, and its comment is not helpful. What is the logic behind? Thanks Hilaire -- Dr. Geo http://drgeo.eu

Sept. 20, 2018

A mentoring course ComplexCondition implementation

by Vitor Medina Cruz

Hello, In A Mentoring Course in Smalltalk, Andr es Valloud explains a really good implementation of and API to deal with complex conditions, is there any implementation of this (or similar) on Pharo? Regards, Vitor

Sept. 20, 2018

Re: [Pharo-users] Distinguishing between dynamic vs. static HTTP requests

by Sven Van Caekenberghe

Hmm, not really, in Seaside it is typically /files and /static is something that I have used as well, but really it should be flexible as there are too many different scenarios, including all kinds of prefixes. > On 20 Sep 2018, at 09:49, James Foster <Smalltalk(a)JGFoster.net> wrote: > > When serving web pages from a web server in front of Smalltalk (e.g., Apache, Nginx, etc.), is there a convention for designating which pages are to be sent on to Smalltalk and which are to be served directly (or sent somewhere else)? Is there a prefix or suffix for one or the other? That is, do you treat everything that begins with â/static/â as static (easy enough) and everything else gets forwarded to Smalltalk? Or do you have a similar prefix for â/dynamic/â content? Or do you have a suffix (â.stâ or â.seasideâ) that designates requests that are sent on to Smalltalk? I can make any of these work, and I can come up with my own rules, but if there is a convention Iâd like to follow it. > > Thanks, > James

Sept. 20, 2018

Distinguishing between dynamic vs. static HTTP requests

by James Foster

When serving web pages from a web server in front of Smalltalk (e.g., Apache, Nginx, etc.), is there a convention for designating which pages are to be sent on to Smalltalk and which are to be served directly (or sent somewhere else)? Is there a prefix or suffix for one or the other? That is, do you treat everything that begins with â/static/â as static (easy enough) and everything else gets forwarded to Smalltalk? Or do you have a similar prefix for â/dynamic/â content? Or do you have a suffix (â.stâ or â.seasideâ) that designates requests that are sent on to Smalltalk? I can make any of these work, and I can come up with my own rules, but if there is a convention Iâd like to follow it. Thanks, James

Sept. 20, 2018

Re: [Pharo-users] Retina support in Pharo

by Alexandre Bergel

Hi Andy, I have not idea. But this would be a very valuable effort. Cheers, Alexandre > On Sep 18, 2018, at 5:12 AM, andyl <andylarder(a)hotmail.com> wrote: > > Hi, > > Has any work been done of this? If not, could someone point me in the right > direction to start it, perhaps with a list of what is already known about > the issue? I'd be willing to look at both MacOS and Windows HiDPI rendering > at the same time. > > Presumably the 64 bit MacOS build is Cocoa based, so that would be the right > starting point? > > Although I have decades of experience of the above platforms, I'm a relative > novice with the Smalltalk libraries - so any hints as to how the rendering > process currently hangs together (and how much is Smalltalk vs native > rendering) would be really helpful. > > Regards, > Andy. > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >

Sept. 20, 2018

Re: [Pharo-users] Calypso and critiques (Pharo7)

by Arturo Zambrano

Oh! I found this ... sorry for asking a reported problem ClyCriticBrowserPlugin disable.ClyCriticEnvironmentPlugin disable.ClyNavigationEnvironment reset. On Wed, Sep 19, 2018 at 1:26 PM Arturo Zambrano <arturo.zambrano(a)gmail.com> wrote: > Hi all, > is there any way to switch off the critiques pane in the bottom of > calypso? > > Thanks ! >

Sept. 19, 2018