- Pharo-users - lists.pharo.org

Thoughts on mini Smalltalk exercises

by Tim Mackinnon

Hi - Iâm trying to help Sam kickstart Pharo working Ian the exercism platform. For those less familiar, exercism is a platform with a series of exercises that users/students âcheckoutâ and then run a test to guide them through completing the code to then progress to the next challenge. There is also the ability to comment on each otherâs progress and see examples of otherâs solutions. Most languages are more traditional file based examples, so it would be nice to have Smalltalk as something a bit different. Although we think Tonel 2 will be an excellent vehicle for participating alongside other languages as it helps us fit in a little easier (nice how all our initiatives are coming together to make this easy). As you can imagine, exercises start out very simple and then increase in complexity. My question however, is about the early exercise like HelloWorld, LeapYear etc. These tend to be single method problems of just a few lines, requiring no instance variables (this all comes later). Iâm wondering about peopleâs thoughts on whether we should introduce early Smalltalk examples as just class methods and later introduce instance methods and âclass constructor methods â? Or is this more confusing for students? Essentially we are battling with the familiarity of the C âmainâ method - and looking at python and ruby solutions, they initially start with no objects and just main style methods. E.g. hello world can be simply: HelloWorld sayHello. vs HelloWorld new sayHello. I can see proâs/conâs either way - but wondering what others think. Tim Sent from my iPhone

July 11, 2018

Re: [Pharo-users] Changing a BaselineOf... to include one more package

by Andrew P. Black

Hi Guillermo, Thanks for the explanation. I guess that I really don't have much idea how this baseline stuff is supposed to work, so when it fails, I don't know where to look. My initial question was about why iceberg (or Metacello?) was looking in the wrong directory, but that seems to have been the wrong question. So, you are right; the BaselineOfSmaCC has not been updated to include the SmaCC-Reification package, which is new (and experimental). So it seems that I have to add it. Here is the current baseline: > BaselineOfSmaCC >> baseline: spec > <baseline> > spec > for: #common > do: [ spec blessing: #baseline. > spec > package: 'SmaCC-Source-Editing'; > package: 'SmaCC-Runtime'; > package: 'SmaCC-GLR-Runtime' > with: [ spec requires: 'SmaCC-Runtime' ]; > package: 'SmaCC-Debugging-Support' > with: [ spec requires: 'SmaCC-Development' ]. > spec > package: 'SmaCC-Development' > with: [ spec requires: 'SmaCC-GLR-Runtime' ]. > spec > for: #Alt > do: [ spec > package: 'SmaCC-Alt' with: [ spec requires: 'SmaCC-Runtime' ]; > package: 'SmaCC-Development-UI' > with: [ spec > requires: #('SmaCC-Development' 'SmaCC-Alt' 'SmaCC-Debugging-Support') ] ]. > spec > for: #NoAlt > do: [ spec > package: 'SmaCC-Development-UI' > with: [ spec requires: #('SmaCC-Development' 'SmaCC-Debugging-Support') ] ]. > spec > package: 'SmaCC-Tests' > with: [ spec requires: 'SmaCC-Development' ]; > package: 'SmaCC-Browser' with: [ spec requires: 'SmaCC-Runtime' ]; > package: 'SmaCC-Parse-Tree-Comparison' > with: [ spec requires: 'SmaCC-Runtime' ]; > package: 'SmaCC-Rewrite-Engine' > with: [ spec > requires: #('SmaCC-GLR-Runtime' 'SmaCC-Source-Editing' 'SmaCC-CSV-Parser') ]; > package: 'SmaCC-Rewrite-Engine-Tests' > with: [ spec requires: 'SmaCC-Rewrite-Engine' ]; > package: 'SmaCC-Rewrite-Engine-Command-Line' > with: [ spec requires: 'SmaCC-Rewrite-Engine' ]; > package: 'SmaCC-Rewrite-Server'; > package: 'SmaCC-Rewrite-Server-Worker' > with: [ spec requires: 'SmaCC-Rewrite-Engine' ]; > package: 'SmaCC-Swift' > with: [ spec requires: 'SmaCC-GLR-Runtime' ]; > package: 'SmaCC-Smalltalk-Parser' > with: [ spec requires: 'SmaCC-Runtime' ]; > package: 'SmaCC-Generic-Smalltalk-Parser' > with: [ spec requires: 'SmaCC-GLR-Runtime' ]; > package: 'SmaCC-C-Parser' > with: [ spec requires: 'SmaCC-Runtime' ]; > package: 'SmaCC-CSV-Parser' > with: [ spec requires: 'SmaCC-Runtime' ]; > package: 'SmaCC-CSharp' > with: [ spec requires: 'SmaCC-GLR-Runtime' ]; > package: 'SmaCC-Cucumber' > with: [ spec requires: 'SmaCC-GLR-Runtime' ]; > package: 'SmaCC-Javascript-Parser' > with: [ spec requires: 'SmaCC-GLR-Runtime' ]; > package: 'SmaCC-Java' > with: [ spec requires: 'SmaCC-GLR-Runtime' ]; > package: 'SmaCC-Python' with: [ spec requires: 'SmaCC-Runtime' ]; > package: 'SmaCC-Python-Tests' > with: [ spec requires: 'SmaCC-Python' ]; > package: 'SmaCC-Line-Parser' > with: [ spec requires: 'SmaCC-Runtime' ]; > package: 'SmaCC-Delphi' > with: [ spec requires: 'SmaCC-GLR-Runtime' ]; > package: 'SmaCC-DelphiForms' > with: [ spec requires: 'SmaCC-GLR-Runtime' ]; > package: 'SmaCC-IDL' with: [ spec requires: 'SmaCC-Runtime' ]. > spec > group: 'default' with: #('Tools'); > group: 'Runtime' with: #('SmaCC-GLR-Runtime'); > group: 'Rewrite' with: #('SmaCC-Rewrite-Engine'); > group: 'Rewrite-Server' > with: > #('SmaCC-Rewrite-Server-Worker' 'SmaCC-Rewrite-Server' 'Rewrite' 'SmaCC-Rewrite-Engine-Command-Line'); > group: 'Tools' > with: > #('SmaCC-Development-UI' 'Examples' 'Rewrite' 'SmaCC-Parse-Tree-Comparison'); > group: 'Debugging' with: #('SmaCC-Debugging-Support'); > group: 'Examples' > with: > #('SmaCC-Smalltalk-Parser' 'SmaCC-C-Parser' 'SmaCC-Java' 'SmaCC-CSV-Parser' 'SmaCC-Line-Parser'); > group: 'Examples-Extra' > with: > #('SmaCC-IDL' 'SmaCC-CSharp' 'SmaCC-Cucumber' 'SmaCC-Swift' 'SmaCC-Delphi' 'SmaCC-DelphiForms' 'SmaCC-Python' 'SmaCC-Javascript-Parser'); > group: 'Tests' > with: #('SmaCC-Tests' 'SmaCC-Rewrite-Engine-Tests' 'SmaCC-Python-Tests') ] Should I add a new group, something like > spec group: 'Reification' > with: #('SmaCC-Reification') But then I must also specify the dependencies of the SmaCC-Reification package, so I need to add > spec package: 'SmaCC-Reification' with: [ spec requires: #('SmaCC-Smalltalk-Parser' 'SmaCC-Runtime' 'SmaCC-Java') ] (I assumed that this would go earlier in the method, with the other package specs. So I put it right after package: 'SmaCC-IDL') Once I've done that, I tried to load the BaselineOfSmaCC again, and I find that I've broken it. I get a walkback with the message "Could not resolve: SmaCC-Reification [SmaCC-Reification] in /Users/black/Development/Pharo/images/Pharo 7.0 SmallGrace 0.34/pharo-local/package-cache git@github.com:apblack/SmaCC.git[fglr]" Why is it trying to load SmaCC-Reficiation? Did my changes to the baseline somehow change the default configuration too? Moreover, my original problem is still there â it's looking in a nonexistent package cache, rather than on github, or in my ~/iceberg/apblack/SmaCC clone of github. > - If SmaCC-Reification is in a non-default group, you probably want to add > > spec > baseline: 'SmaCC-Reification' > with: [ spec repository: 'github://apblack/SmaCC:working'; loads: #( 'NAME-OF-YOUR-REIFICATION-GROUP' ) <> ]. > This would go in the BaselineOfGrace package, right? Not in BaselineOfSmaCC > And then your packages can depend on it. > > - IF SmaCC-Reification is not in the SmaCC baseline, then, there is nothing you can do, but to add it :) > Thanks for the help so far Andrew

July 11, 2018

Re: [Pharo-users] Request for Windows test

by webwarrior

Windows finds DrGeo.exe suspicious. I guess the problem will disappear when enough users have launched it. But it's usable anyway, you just have to click through the annoying dialog. -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

July 11, 2018

Re: [Pharo-users] Which command-line handlers do you use most?

by Herbert VojÄÃk

Herbert VojÄÃk wrote on 11. 7. 2018 14:48: > > > Damien Pollet wrote on 9. 7. 2018 17:38: >> Hi all, >> >> I'm starting to port / reimplement existing command line handlers >> using Clap. There's a dozen, but I wonder which ones are the most >> relied upon, because it's a good opportunity for refactoring the >> command line API as a whole and simplifying it or at least making it >> more orthogonal. >> >> For instance I discovered there is a "perform" command, which is sort >> of redundant with the "eval" one. Similarly there are both a >> "configuration" and a "metacello" handlers which seem to have the same >> exact purposeâ¦ > > The default (.st file), save, update, geÂ£ > > Herby > >> Since Clap can exist besides the current command-line handlers, we can >> have a deprecation period to minimize breakage and leave time for >> people to adapt before we kill old command line handlers for real. >> >> -- >> Damien Pollet >> type less, do more [ | ] http://people.untyped.org/damien.pollet > > P.S.: What I would like regarding of the command-line, is if > linux/osx/windows did the same regarding save/no-save/quit/no-quit then > running .st file. I have to include #save:andQuit: send in my .st files "when running" > b/c in Win it keeps running. But I understand this is actually VMs > having different options on different platforms. Anyway, would be > _really_ nice. >

July 11, 2018

Re: [Pharo-users] Which command-line handlers do you use most?

by Herbert VojÄÃk

Damien Pollet wrote on 9. 7. 2018 17:38: > Hi all, > > I'm starting to port / reimplement existing command line handlers using > Clap. There's a dozen, but I wonder which ones are the most relied upon, > because it's a good opportunity for refactoring the command line API as > a whole and simplifying it or at least making it more orthogonal. > > For instance I discovered there is a "perform" command, which is sort of > redundant with the "eval" one. Similarly there are both a > "configuration" and a "metacello" handlers which seem to have the same > exact purposeâ¦ The default (.st file), save, update, geÂ£ Herby > Since Clap can exist besides the current command-line handlers, we can > have a deprecation period to minimize breakage and leave time for > people to adapt before we kill old command line handlers for real. > > -- > Damien Pollet > type less, do more [ | ] http://people.untyped.org/damien.pollet P.S.: What I would like regarding of the command-line, is if linux/osx/windows did the same regarding save/no-save/quit/no-quit then running .st file. I have to include #save:andQuit: send in my .st files b/c in Win it keeps running. But I understand this is actually VMs having different options on different platforms. Anyway, would be _really_ nice.

July 11, 2018

Re: [Pharo-users] Zinc + HTTPS does not check for self signed certificates.

by Sven Van Caekenberghe

Hi JuliÃ¡n, Although we have TLS/SSL support (in the form of Zodiac, Zinc is just a user offering HTTP(S) on top), it is currently all dependent on a plugin that is different on all platforms and mostly lacks support for certificates. It is what it is. I know that some developers are working on these issues, but I won't / can't say more as this is all very early days. Sven > On 11 Jul 2018, at 01:28, JuliÃ¡n Maestri <serpi90(a)gmail.com> wrote: > > tl;dr > Querying an HTTPS site with a self signed certificate does not fail / raise an exception (and it should). > > Long: > I'm trying to use client and server HTTPS validation with Zinc on Pharo. > > I prepared: a self signed CA certificate, and server and client certificates signed by the same CA. > I set up an Apache server with a site over HTTPS requiring client authentication. This worked (had to install the client certificate on my browser to access the site). > > After some failed attempts, i found this link which was very helpful and successfully managed to authenticate a ZnClient with the Apache Server. > > This is the small snippet, only configuring the full path to the client certificate is enough (getting the right format for the pem file is another thing, it must have both certificate and key inside). > > | result | > Transcript clear. > result := ZnClient new > certificate: 'certs/client.pem' asFileReference asAbsolute pathString; > logToTranscript; > url: 'https://my-secure-site'; > get. > Transcript crShow: result. > > That worked on linux, windows still fails i don't know why. > > Trying to make it work on linux, i started checking without client authentication, and realized that Zinc was not complaining about the server certificate not known by a trusted CA. > I changed the server certificate with a new one, self signed to make the case simpler, and Zing still did not complain. > > This is a problem, it should either fail, or let me configure it to fail when the server is not trustworthy. > I'm not sure if it's Zinc, Zodiac or the SqueakSSL plugin. > > Am i doing anything wrong? Is there a configuration option which i can not find? If necessary, i can (temporarily) set up a public server with a self-signed certificate to help reproduce the case (the server i'm currently using is on a local network). > > > > PD: Sadly for this particular project (reverse proxy) this would be a no go, i can not use Pharo :( >

July 11, 2018

Request for Windows test

by Hilaire

Hi, A Windows user reported to me difficulty to start Dr. Geo. Although I had success to run it in a Windows system, I will be glad if some of you would mind testing it on their windows system, and report to me success or failure along the used Windows system. -> http://www.drgeo.eu/download Thanks a lot Hilaire -- Dr. Geo http://drgeo.eu

July 11, 2018

Re: [Pharo-users] XML support for pharo

by monty

This is the latest version of the XML/XPath Scraping Booklet: <https://files.pharo.org/books-pdfs/booklet-Scraping/2018-01-07-scrapingbook…> ___ montyos.wordpress.com

July 11, 2018

Tonel class comments

by Guillermo Polito

Hi all, Since people have been asking how to use Tonel, I've took a look at it and have written down two class comments for both the reader and the writer. I'll push them to Tonel and schedule soon a patch release with it. Here are the class comments so people can see them/discusses them. Please, report any enhancements as pull requests in git@github.com:pharo-vcs/tonel.git ! TonelReader I'm a monticello reader for tonel format repositories. I read - a package per directory - a class per file - a set of extensions to a single class per file (for example, all extensions of a package to String will be in a single file) I'm created on a file reference to a directory where the package will be read and the name of the package to read. [[[ TonelReader on: 'someDirectoryWithTonelPackages' asFileReference filename: 'MyPackageName' ]]] My main method is - ==#definitions== reads and parses the tonel file, returns a list of monticello definitions. - ==#snapshot== returns a monticello snapshot with the read definitions. - ==#version== returns a monticello version with the read snapshot. !! Implementation details The monticello versions I return do have artificial information. Since I'm just meant to read versions from a directory, this directory has no information such as commit message, commit time, author, or ancestors. Check the method ==#loadVersionInfo== for more information. ! TonelWriter I'm a monticello writer for tonel format, writing - a package per directory - a class per file - a set of extensions to a single class per file (for example, all extensions of a package to String will be in a single file) I'm created on a file reference to a directory where the package will be written. [[[ TonelWriter on: ('someDirectory' asFileReference ensureCreateDirectory) ]]] My main methods are - ==#writeVersion:== that receives as argument a monticello version to write, from where I'll extract the corresponding monticello snapshot. - ==#writeSnapshot:== that receives as argument a monticello snapshot to write, from where I'll write all the contained definitions. !! Implementation details Notice that while writing, if the written package/snapshot already exists in the directory I'll overwrite it (i.e., remove it and recreate it). -- 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 <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

July 11, 2018

Re: [Pharo-users] Email Google API for pharo

by Peter UhnÃ¡k

+1. I've used it last year or so and it was very nice to use. On Wed, Jul 11, 2018 at 2:59 AM, Ben Coman <btc(a)openinworld.com> wrote: > On 11 July 2018 at 05:53, oswall arguedas <oswallcr(a)hotmail.com> wrote: > > Greetings community of pharo > > > > I am working with the google API to process gmail emails, read, modify, > > archive, send. > > > > Is there any way with pharo ?. > > > > Thank you very much in advance > > > > Oswall > > I remember seeing this... > http://forum.world.st/Using-Google-service-discovery-API- > s-with-Pharo-Smalltalk-by-Richard-J-Prinz-td4814538.html > > cheers -ben > >

July 11, 2018