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

Fun with UI Avatars
by Sven Van Caekenberghe Oct. 7, 2017

Oct. 7, 2017

I came across https://ui-avatars.com, a web service that creates avatar images based on some parameters. >From Pharo, the shortest invocation would be something like ZnEasy getPng: 'https://ui-avatars.com/api?name=Albert+Einstein&size=128&background=0D8ABC&…'. Making use of the full builder interface of ZnClient that would look more like ZnClient new https; host: 'ui-avatars.com'; addPath: #api; queryAt: #name put: 'Albert Einstein'; queryAt: #size put: 128; queryAt: #color put: 'FFF'; queryAt: #background put: '0D8ABC'; queryAt: #rounded put: true; accept: ZnMimeType imagePng; enforceHttpSuccess: true; enforceAcceptContentType: true; contentReader: [ :entity | ImageReadWriter formFromStream: entity readStream ]; beOneShot; get. Anyway, it is cool to have an environment that makes this kind of experimentation so much fun. It is probably easy to implement this avatar image generation directly in Pharo ... Sven

1 0

[ANN] OSSubprocess Bugfix and enhancements release
by Mariano Martinez Peck Oct. 6, 2017

Oct. 6, 2017

Dear all, I have just released a new bugfix and enhancements release v0.2.5 for OSSubprocess as you can see in [1]. This new release is thanks to the awesome work of Guillermo Polito [2]. He found a problem (and a fix) that would hung/block the Pharo image in a wait state. This problem has been forever and I have faced it myself. It would only happen when using #waitForExit and under certain scenario. Because of that, I recommend everyone to move to this release. Aside from that serious bug, he has also done quite some improvements in the tests and in the Travis setup. Once this PR [3] has been merged and SmalltalkCI updated, our Travis build [4] should show all green builds for Linux/OSX and Pharo 5.0 and 6.1. I have also copied the configuration into Pharo 5.0 and 6.0 catalog so as of tomorrow, it should be there. Cheers, [1] https://github.com/marianopeck/OSSubprocess/releases/tag/v0.2.5 [2] https://github.com/marianopeck/OSSubprocess/pull/25 [3] https://github.com/hpi-swa/smalltalkCI/pull/320 [4] https://travis-ci.org/marianopeck/OSSubprocess -- Mariano http://marianopeck.wordpress.com

1 0

Organisation and workflows
by Steven R. Baker Oct. 6, 2017

Oct. 6, 2017

Heya folks, [Please jump on any of my statements that sound crazy: use of Spec, other assumptions, etc.] I'm starting an application in Pharo, using Spec. Basically, a GTD application in the spirit of nirvanahq, omnifocus, things, nozbe. The code is working just fine, but I'm left with a lot of questions about how to organize it. First, is there some trick to managing images? Are people using one-per-project, or one-per-computer? All of the above? Anyone using PharoLauncher these days? Other tools? I'm assuming that the current state of the art is Iceberg; where can I find a "This is how you should organize your project using Iceberg" document, blog, book, tutorial, video, or otherwise. Once the application is done, I assume I'll want to ship it in a minimal Pharo image. Is there documentation or prior art on this? Finally, is there a way to run and capture keybindings globally? I have one part of my application (a quick-entry window) which I want summoned from a global (OS-wide) hotkey. Has this been done before? Or is it not easy to break the fourth wall, so to speak, and register a global keybinding from inside the VM? Thanks! -Steven

6 7

Creating a new method
by Dirk Olmes Oct. 6, 2017

Oct. 6, 2017

Hi, I may be asking an absolute noob question but I was unable to find any useful hints on google ... I often find myself writing methods that do not yet exist when implementing other methods, e.g. when I'm writing the implementation of methodA I'm calling out to methodB. What's the easiest way to create the new method? I know I can jump aroung through hoops with a separate browser but that feels cumbersome. I understand that the editor/runtime/whatever cannot know 100% of the time where to put the new method but at least for messages to self it should be smart enough to offer some kind of help. -dirk

4 3

ZnClient in Pharo 6.1 not working for Https on Windows
by kmo Oct. 6, 2017

Oct. 6, 2017

I was trying to Soup on Windows 7 and found I could not access https sites On windows 7 and 10 the following code fails: ZnEasy get:'https://genius.com/Alice-nuvole-lyrics'. This works fine in Pharo 5 on Windows. Also works fine with Pharo 6.1 (32 bit) on Linux. The problem is Pharo 6.1 on Windows. The error is: "SSL/TLS plugin initialization failed (VM plugin missing ? OS libraries missing ?)" I know that his has been seen on Linux in the past - see http://forum.world.st/SSL-TLS-plugin-initailization-failed-VM-plugin-missin… I'm running the latest vm and 6.1 image. -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

3 3

Seaside Magritte tutorial
by Vitor Medina Cruz Oct. 6, 2017

Oct. 6, 2017

Hello! Is there any tutorial focused on Seaside and Magritte that creates an example app using Magritte in a job trivial way? I mean, something that mix or segregate descriptions from some object to generate pages on Seaside, that show a way to personalize more the generated page, if that is possible. Thanks in advance!

3 2

Deploying on Linux with LibC version < 2.15
by Cyril Ferlicot Oct. 6, 2017

Oct. 6, 2017

Hi, I am migrating some applications from Pharo 4 to Pharo 6. The new deployment of those applications needs to work on linux with LibC < 2.15. With Pharo 4 there was a special VM[1]. I do not see such VM for Pharo 6. How should we manage those distributions? Thank you in advance. [1] http://files.pharo.org/vm/pharo/linux/old-libc/Pharo-VM-linux-oldLibC.zip -- Cyril Ferlicot https://ferlicot.fr http://www.synectique.eu 2 rue Jacques PrÃ©vert 01, 59650 Villeneuve d'ascq France

4 4

SVG Icons
by Steven R. Baker Oct. 6, 2017

Oct. 6, 2017

Heya folks! I need to load SVG images (for icons) in my application. I've searched my 6.1 image for SVG, but haven't found anything. Is there a library for loading SVGs? I'd really like to get them directly into instances of Form if possible, but I'm flexible. :) Thanks! -Steven

3 2

Brea wiki software
by H. Hirzel Oct. 5, 2017

Oct. 5, 2017

On 8/23/17, Offray <offray.luna(a)mutabit.com> wrote: > Hi, > > On the Teapot + Mustache integration, Hannes, you may want to see my early > prototype: > > http://smalltalkhub.com/#!/~Offray/Brea > > At some point, it will contain distributed wiki, backed by Fossil, now that > we're thinking in empower community driven wiki like documentation. > > Offray Hi Offray I found Name: Brea-OffrayLuna.8 Author: OffrayLuna Time: 1 June 2017, 4:18:20.860411 pm There is no test to show me how to use it and I none of the class comments of the 4 classes gives enough clues. Interesting method so far routes "I define how the website behaves accordingly to particular routes." self server serveStatic: 'demo' from: '/opt/gig/'; GET: 'members/test' -> [ :req | BreaMember new renderTestUserAsHtml ]; GET: 'members/add' -> [ :req | BreaMember new htmlInput ]; POST: 'members/summit' -> [ :req | self processNewMember: req ] May I ask you to give a few hints how to start it? Is it possible to use it without Fossil, just with image persistence? Regards Hannes

3 12

SystemVersion cleanup (or the return of the explicit build number) in latest Pharo 7
by Torsten Bergmann Oct. 5, 2017

Oct. 5, 2017

Hi, as you all know Pharo 7 is built using sources from github and a new bootstrap process. The first Pharo 7 images [1] unfortunately were hard to distinguish - the initial problem was described in [2] Guille tried to address this by adding a build number again [3] but unfortunately he mixed it into the existing suffix of the class SystemVersion. There was also some other trouble afterwards: - the highestUpdate was still not set by the bootstrap process, which made some code unloadable (like Artefact who's config is checking if it is above a certain update number) - with Guilles fix the build number had to be parsed from the suffix string - one was still not able to distinguish 32/64 bit images - the SystemVersion class and the according tests were still ugly So I reviewed all this more deeply and cleaned SystemVersion as well as the tests while trying to stay as compatible as possible. Thanks a lot to Pavel and Esteban who helped me sorting things out, especially in git and the bootstrap process. How does it look now ==================== 1. Our system type is still called "Pharo" ;) SystemVersion current type -> 'Pharo' 2. we still continue with major and minor versioning (leaving out patch versions), so currently work is done for Pharo 7.0 SystemVersion current major -> 7 SystemVersion current minor -> 0 SystemVersion current majorMinorVersion -> 'Pharo7.0' 3. the identification string now has a "+" sign inside to separate the build meta informations following the given rule 10 from http://semver.org So the full image version now looks like this: SystemVersion current imageVersionString -> 'Pharo-7.0+alpha.build.168.sha.30fc9bbe79922877706ecd842f8aef6822cdcdd9 (32 Bit)' 4. the suffix is currently "alpha" and may be changed depending on release status SystemVersion current suffix -> 'alpha' 5. the build number is stored as an explicit ivar in SystemVersion now SystemVersion current build -> 168 Note that the build number is explicitly set during the bootstrap process from the outside and increased over time with each new build. It represents the CI build number of #development branch now, see [4] on CI server 6. the github SHA commit hash is accessible too: SystemVersion current commitHash -> '30fc9bbe79922877706ecd842f8aef6822cdcdd9' which corresponds in this case to the last commit in #development branch https://github.com/pharo-project/pharo/commit/30fc9bbe79922877706ecd842f8ae… 7. the version includes now also the 32/64 bit distinction: Pharo-7.0+alpha.build.168.sha.30fc9bbe79922877706ecd842f8aef6822cdcdd9 (32 Bit) or Pharo-7.0+alpha.build.168.sha.30fc9bbe79922877706ecd842f8aef6822cdcdd9 (64 Bit) Additionally ============ - the version is displayed in SystemReporter and the AboutBox (Screenshot attached), please use this to identify the image easily - the #highestUpdate is calculated dynamically with code in the image (but it is there only for compatibility reasons). SystemVersion current highestUpdate -> "70168" We might easily catch the 999 build mark now and then run into 71000 which might still be Pharo 7.0 instead of 7.1. (which means first two digits of update number will then NOT correspond to major/minor version anymore). So better avoid #highestUpdate as a meaningful number for loading code or other. - also note if you contribute with an own PR (in your own fork on github) the build number is the build number of you PR specific CI build. Once your PR is reviewed and merged it is the regular Pharo image build number again. - you can reuse SystemVersion for you own apps built on top of Pharo: "MyKillerApp-1.0+beta (64 Bit)" can be easily created with: (SystemVersion major: 1 minor: 0 suffix: 'beta') type: 'MyKillerApp'; yourself - if you report a bug on bugs.pharo.org it would be good to note down the full version of the image you used as found in the About box. This allows to better reproduce wrong behavior that only happens in a specific image Thanks T. [1] http://files.pharo.org/image/70/ [2] http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/2017-August/1309… [3] http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/2017-August/1310… [4] https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0