September 2018 - Pharo-users

Sending emails
by Jeff Gray Sept. 21, 2018

Sept. 21, 2018

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

1 1

Sending email
by Jeff Gray Sept. 20, 2018

Sept. 20, 2018

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

1 0

Pharo 6 snap package
by Alistair Grant Sept. 20, 2018

Sept. 20, 2018

Hi Everyone, I've updated the Pharo 6 snap package for Ubuntu. The major advantages of using the snap package are: - No need to install all the 32 bit dependencies on a 64 bit system, they're all contained and isolated within the snap package. - Automagically distinguish between 32 bit and 64 bit images and run the appropriate VM (as with the ZeroConf package, the 64 bit VM still needs more testing). To get Pharo up and running on Ubuntu 16.04 or later: # Install Pharo $ sudo snap install --candidate pharo --classic # If your system isn't configured for threaded heartbeat: $ sudo pharo.config # Download the latest Pharo 6 image $ pharo.getimage # Go... $ pharo.ui Pharo.image # or: $ pharo Pharo.image eval 4+3 To get a list of available commands: $ snap info pharo If you're on Debian or Ubuntu 14.04 you'll need to install snapd, see https://snapcraft.io/docs/core/install The VM is the threaded heartbeat, dated 201705310241. The installation flags are: --candidate - The edge and beta channels are for development versions. It progresses to candidate and then stable. --classic - Snap packages are normally sandboxed for security reasons. Since Pharo is a development environment in which we want to be able to run any executable, or load any library, it is installed with access to the entire system (as the running user). Why use snap packages? - They include all dependencies. In particular, for the 32 bit versions, this means that it isn't necessary to install all the 32 bit architecture and associated dependencies. - Including dependencies means that there shouldn't be any problems with incompatible library versions when upgrading. Why not use snap packages? - It's a relatively new technology, with a number of rough edges. - There may still be issues with its sandboxing that I haven't discovered yet. - Because the package uses classic confinement, it isn't cross-distribution in practice (unfortunately). Please let me know of any other advantages or disadvantages you think should be listed here. If you don't trust me to configure your system correctly (which requires sudo): - All the scripts that make up the sub-commands are visible, e.g. pharo.config can be viewed at /snap/pharo/current/usr/bin/CONFIG The packaging code is at: https://github.com/akgrant43/pharo-snap Cheers, Alistair

7 12

Query on Pharo syntax
by PBKResearch Sept. 20, 2018

Sept. 20, 2018

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, 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

3 4

Distinguishing between dynamic vs. static HTTP requests
by James Foster Sept. 20, 2018

Sept. 20, 2018

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

2 1

Retina support in Pharo
by markm Sept. 20, 2018

Sept. 20, 2018

Hi Is it possible to get Pharo (4 or 5) to run with retina support on OS X? I have tried searching for some answers, but alas could only find a handful of posts from a few years back. Any help much appreciated! Mark -- View this message in context: http://forum.world.st/Retina-support-in-Pharo-tp4895245.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

10 14

Calypso and critiques (Pharo7)
by Arturo Zambrano Sept. 19, 2018

Sept. 19, 2018

Hi all, is there any way to switch off the critiques pane in the bottom of calypso? Thanks !

1 1

Yet another Pharo in docker
by Herby VojÄÃk Sept. 18, 2018

Sept. 18, 2018

https://hub.docker.com/r/herbysk/pharo/

8 16

To get started with Gtoolkit and bloc
by Hilaire Sept. 17, 2018

Sept. 17, 2018

Hi, Is there any document to get start with bloc and gtoolkit? Thanks Hilaire -- Dr. Geo http://drgeo.eu

4 9

Re: [Pharo-users] [ANN] New Pharo 6.1 stable VM
by Esteban Lorenzano Sept. 17, 2018

Sept. 17, 2018

> On 17 Sep 2018, at 16:45, Petr Fischer via Pharo-users <pharo-users(a)lists.pharo.org> wrote: > > > From: Petr Fischer <petr.fischer(a)me.com> > Subject: Re: [Pharo-users] [ANN] New Pharo 6.1 stable VM > Date: 17 September 2018 at 16:45:16 CEST > To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > > > Is new VM here? > > https://files.pharo.org/vm/pharo-spur64/linux/ <https://files.pharo.org/vm/pharo-spur64/linux/> The now stable VM for Pharo 6.1 was always there. What âpromote to stableâ means is that I put a link in the official place to download the VM: https://files.pharo.org/get-files/61 <https://files.pharo.org/get-files/61>, and now is what you get with zeroconf. Esteban > > Thanks, pf > > >> Hi, >> >> Following what I had in my todo list for when coming back from ESUG, I promoted a new stable VM for Pharo 6.1. >> This is the VM that has been tested during almost two months for Pharo 7.0, so it should be fine, but let me know if there is any problem. >> >> Esteban > > >

1 0