April 2020 - Pharo-users - lists.pharo.org

EXIF / JPEG metadata
by Alistair Grant Nov. 30, 2025

Nov. 30, 2025

Hi Everyone, As far as I can tell, JPEGReadWriter in Pharo 7 doesn't read (or write) the image metadata, e.g. title, keywords, exposure time, etc. Is anyone aware of a package that does? Thanks! Alistair

2 1

Re: [Pharo-users] Personal wiki / information manager
by Evan Donahue Sept. 25, 2023

Sept. 25, 2023

Seems that Pharo is a magnet for this kind of project. I've been writing one as well and using it to organize my research notes. Does anyone working on personal info mgmt tools want to talk offline? I expect we're running into some of the same issues, both conceptual and technical. Evan

18 33

WebDav and CalDav in Pharo ?
by CÃ©drick BÃ©ler April 13, 2022

April 13, 2022

Hi all, I do some experiments with iCal. For now I serve a full calendar over HTTP. Not bad, but it is read only. Iâd like to try CalDAV. I was looking for it, and also webDAV. Gofer it smalltalkhubUser: 'UdoSchneider' project: 'FileSystemNetwork'; configuration; load. #ConfigurationOfFileSystemNetwork asClass project stableVersion load: 'Webdav' Iâve found the project of Udo, but it doesnât load on P8. I think this is due to the stream refactoring. Right now the image hung. Iâll try maybe to load it manually. But I was wondering oof there were other alternatives ? TIA, CÃ©drick

4 4

[ANN] Pharo Launcher 2.0 released!
by Christophe Demarey July 20, 2020

July 20, 2020

Hi all, Pharo Launcher 2.0 has just been released! It is available from http://pharo.org/download <http://pharo.org/download>. This new version introduces major changes: The UI has been fully rewritten using the new Spec2 framework <https://github.com/pharo-spec/Spec> and the Commander2 library <https://github.com/pharo-spec/Commander2>. UI has been revamped to increase usability, especially for newcomers. The main window is now composed of a toolbar and the list of images. The template list is now available when clicking on the new image button. Documentation web site : All Pharo Launcher features are now explained in the new documentation available at https://pharo-project.github.io/pharo-launcher. You can contribute easily by clicking the *edit on GitHub* button. You can now have many launch configurations for an image (VM to use, vm and image arguments). It means you can use headless Pharo VM from Pharo Launcher. When creating a new image, you can specify an initialisation script that will be run once at the first image launch. It is useful to load your project code in a stock Pharo image for example. See https://pharo-project.github.io/pharo-launcher/create-images/#image-initial… You can now define your own template sources in addition to official sources (see https://pharo-project.github.io/pharo-launcher/templates/#create-your-own-l…) including authenticated sources. Improved image metadata. Pharo Launcher now manages all image metadata in a single STON file (including description, Pharo version). Big thanks to all contributors, including issue reports. It is also the opportunity to thanks Damien Cassou, the original author of Pharo Launcher. Here is the changelog: Pharo Launcher v2.0 <https://github.com/pharo-project/pharo-launcher/releases/tag/2.0> The list of closed issue is too long (68) to be listed but you can browse it here: https://github.com/pharo-project/pharo-launcher/issues?q=is%3Aissue+is%3Acl… Here are some highlights: New features: Documentation web site Image initialisation script Launch configurations, headless VM support User template file in addition to the official template file Jenkins server template now support pipeline projects Support of private Jenkins server Support of authenticated HTTP server Improvements: Monitoring of image launch failures to give back the error message (if any) Newly created image is automatically selected in the image list Allow to set image description at creation time Better error management (you will have the choice to ignore them or debug them) Add a poor version column in image list Speedup (especially when image repository has a lot of images) Bug fixes: Fix use of system unzip on Windows Regards, The Pharo team.

7 15

running Pharo8 in Digitalocean
by Sanjay Minni May 20, 2020

May 20, 2020

Hi, I am using a Windows 10 local machine and digitalocean ubuntu server droplet - how can I run pharo 8 remotedly in the windows 10 inbuilt powershell ssh terminal - or any other method (I have successfully executed # ./pharo Pharo.image eval --no-quit 'ZnServer startDefaultOn: 8080' and connected from my local machine) ----- cheers, Sanjay -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

5 11

Re: [Pharo-users] mentor question 4
by Richard O'Keefe May 2, 2020

May 2, 2020

This sounds very much like the Luhn test task at RosettaCode. https://rosettacode.org/wiki/Luhn_test_of_credit_card_numbers except that there it is described as working on the digits of an integer. (1) There are two approaches to traversing a sequence in reverse. (A) Reverse the sequence, then traverse the copy forward. aString reverse do: [:each | ...] (B) Just traverse the sequence in reverse aString reverseDo: [:each | ...] My taste is for the second. (2) There are two approaches to deleting spaces. (A) Make a copy of the string without spaces. x := aString reject: [:each | each = Character space]. x do: ... (B) Ignore spaces as you go: (i) aString do: [:each | each = Character space ifFalse: [...]] (ii) aString select: [:each | each ~= Character space] thenDo: [:each | ...] Combining (1A) and (2A) you get very obvious code: (aString reject: [:each | each = Character space]) reverse do: [:digit } ...] Combining (1B) and (2Bi) you get more efficient code: aString reverseDo: [:digit | digit = Character space ifFalse: [ ...]] By the way, let's start by checking that the character in the string *are* digits or spaces: (aString allSatisfy: [:each | each isDigit or: [each = Character s[ace]]) ifFalse: [^false], (3) There are two approaches to doubling the even digits. (A) Make a new string that starts as a copy and change every second digit from the right. (B) Simply *act* as if this has been done; keep track of whether the current digit position is even or odd and multiply by 1 or 2 as appropriate. nextIsOdd := true. aString reverseDo: [:digit | digit = Character space ifFalse: [ nextIsOdd ifTrue: [oddSum := ...] ifFalse: [evenSum := ...]. nextIsOdd := nextIsOdd not]]. I *like* code that traverses a data structure exactly once and allocates no intermediate garbage, so I'd be making (B) choices. But I am not at all sure that it is right for *you* at this stage. Your goal is to get practice in making code that is obviously correct and lends itself to testing. I think in your case it makes more sense to make the (A) choices. You can write some code that reverses a string (using the built-in method) and test that it does what you expect. You can write some code that checks whether a string contains only digits and spaces, and test that. You can write some code that returns a space-less copy, and test that. You can write some code that returns the even (odd) elements of a sequence, and test those. SequenceableCollection>> withIndexSelect: aBlock |index| index := 0. ^self select: [:each | aBlock value: each value: (index := index + 1)] evenElements ^self withIndexSelect: [:each :index | index even] oddElements ^self withIndexSelect: [:each :index | index odd] The easiest way to convert a string to numbers and add up the numbers is to use #detectSum, as in aString oddElements detectSum: [:char | char digitValue] How do you find #digitValue? By looking in Character. #detectSum:? Collection enumeration methods. Using the (A) approach will give you lots of little methods, which you can comment and above all TEST, so that each mistake will be in just one small method. This is a typical functional programming "lots of little functions" approach. On Thu, 30 Apr 2020 at 18:33, Roelof Wobben via Pharo-users <pharo-users(a)lists.pharo.org> wrote: > > Hello, > > I hope I can discuss my approch to this problem : > > Given a number determine whether or not it is valid per the Luhn formula. > > The Luhn algorithm is a simple checksum formula used to validate a variety of identification numbers, such as credit card numbers and Canadian Social Insurance Numbers. > > The task is to check if a given string is valid. > > Validating a Number > > Strings of length 1 or less are not valid. Spaces are allowed in the input, but they should be stripped before checking. All other non-digit characters are disallowed. > > Example 1: valid credit card number > > 4539 1488 0343 6467 > > The first step of the Luhn algorithm is to double every second digit, starting from the right. We will be doubling > > 4_3_ 1_8_ 0_4_ 6_6_ > > If doubling the number results in a number greater than 9 then subtract 9 from the product. The results of our doubling: > > 8569 2478 0383 3437 > > Then sum all of the digits: > > 8+5+6+9+2+4+7+8+0+3+8+3+3+4+3+7 = 80 > > If the sum is evenly divisible by 10, then the number is valid. This number is valid! > > > my idea was to do these steps > > 1) reverse the input. > > 2) use this to double every second digit and calculate the sum of all the numbers : > > checkNumber := (collection reverse selectwith index: [:item :index | (index % 2 == 0) . IfTrue: [item *2]] ) sumNumbers > > 3) check if its a valid number by doing this : > > > ^ (checkNumber % 10 == 0) > > > is this a good game plan or has it flaws or can I do it better ? > > Regards, > > > Roelof > >

2 6

Package Browser (AKA 6-paned Browser) and Pharo package organization
by stephen＠heaveneverywhere.com May 1, 2020

May 1, 2020

Hello friends, Iâm getting started with Pharo after decades using VisualWorks and Squeak; itâs pretty wonderful what you all have assembled! My question is related to what we used to teach as the first law of software reuse: âYou canât reuse it if you canât find it,â and the related software engineering "principle of least astonishment." When I fire up Pharo, the system browser presents me with a list of several hundred categories (from AST to Zodiac) in a system with over 8000 classes. The system categorization makes no sense since I donât know the naming conventions and so many packages have cute but quite non-descriptive names (Zinc? Metacello? Calypso?). In Smalltalk-80, the class category names were organized as a 2-level hierarchy where the top-level were items such as Magnitudes, Collections, Streams, Graphics, Text, System, Tools, Files, etc. This made it easy to find (e.g.,) the browser source code by looking in the Tools package for the class category Tools-Browser. Even packages with cute names (like my own âSirenâ), were categorized for ease of finding; e.g., the Siren classes were in class categories like Music-Events and Music-Magnitudes. Parsing the class category names on the first instance of $- made it possible to build 6-paned Browsers (called package pane browser in Squeak). (We acknowledged that this violates the âzero/one/infinity" rule.) Is something like this available for Pharo? I looked through the Calypso browser code and itâs so over-engineered (IMHO) that itâd take me several days to figure out how to implement this (it was about 1.5 pages of code in Smalltalk-80). If Pharo had a browser that scaled better and a reorganization/simplification of the class categories to use names that were more self-explanatory, it would be *much* easier for new users (in fact, for all users) to find their way around. I apologize for the stepping on toes... Stephen Pope -- Stephen Travis Pope Santa Barbara, California, USA http://HeavenEverywhere.com <http://heaveneverywhere.com/> http://FASTLabInc.com <http://fastlabinc.com/> https://vimeo.com/user19434036/videos <https://vimeo.com/user19434036/videos> http://heaveneverywhere.com/Reflections --

6 5

Automating release announcements
by Gabriel Cotelli May 1, 2020

May 1, 2020

Hi!, Anyone here is moderator in the Pharo Users list? I want to automate the release announcement of projects in github/ba-st org. I'm using sendgrid to send the e-mails and I'm getting a returning mail saying: "Your message to Pharo-users awaits moderator approval". I subscribed previously to the list the e-mail account used as mail sender. Thank you for your help! Gabriel

3 3

[ANN] Willow v13.0.0 [v13.0.0] released!
by Buenos Aires Smalltalk April 30, 2020

April 30, 2020

1 0

Re: [Pharo-users] mentor question 4
by Richard Sargent April 30, 2020

April 30, 2020

See below. On Thu, Apr 30, 2020 at 10:58 AM Roelof Wobben via Pharo-users < pharo-users(a)lists.pharo.org> wrote: > and also not with this one : > > cardNumber := '4539 1488 0343 6467'. > oddSum := 0. > evenSum := 0. > nextIsOdd := false. > cardNumber reverseDo: [:digit | > digit = Character space ifFalse: [ > nextIsOdd > ifFalse: [oddSum := oddSum + (digit asString asInteger ) ] > ifTrue: [(((digit asString asInteger) * 2) > 9) > ifTrue: [evenSum := evenSum + ((digit asString asInteger) * 2) - 9 ] > ifFalse: [ evenSum := evenSum + (digit asString asInteger) * 2 ]]. > nextIsOdd := nextIsOdd not]]. > ^ evenSum > > > > > Op 30-4-2020 om 18:30 schreef Roelof Wobben: > > Op 30-4-2020 om 16:16 schreef Roelof Wobben: > >> nextIsOdd := true. > >> aString reverseDo: [:digit | > >> digit = Character space ifFalse: [ > >> nextIsOdd > >> ifTrue: [oddSum := ...] > >> ifFalse: [evenSum := ...]. > >> nextIsOdd := nextIsOdd not]]. > > > > hmm, > > > > Still no luck with this code : > > > > cardNumber := '4539 1488 0343 6467'. > > oddSum := 0. > > evenSum := 0. > > nextIsOdd := true. > > cardNumber reverseDo: [:digit | > > digit = Character space ifFalse: [ > > nextIsOdd > > ifTrue: [oddSum := oddSum + digit asInteger ] > > ifFalse: [evenSum := ((digit asInteger * 2) > 9) > > ifTrue: [evenSum + ((digit asInteger * 2) - 9) ] > > ifFalse: [ evenSum + (digit asInteger * 2) ]]. > > nextIsOdd := nextIsOdd not]]. > > ^ oddSum + evenSum > With the one change to use #digitValue instead of #asInteger (which answers the code point), the above example works. | evenSum oddSum | cardNumber := '4539 1488 0343 6467'. oddSum := evenSum := 0. nextIsOdd := true. cardNumber reverseDo: [:digit | digit = Character space ifFalse: [ nextIsOdd ifTrue: [oddSum := oddSum + digit digitValue ] ifFalse: [evenSum := ((digit digitValue * 2) > 9) ifTrue: [evenSum + ((digit digitValue * 2) - 9) ] ifFalse: [ evenSum + (digit digitValue * 2) ]]. nextIsOdd := nextIsOdd not]]. ^ oddSum + evenSum gives me 80 for the answer. A few (mostly) minor points: - I don't see why "reverse" is necessary. Of course if you use #do:, nextIsOdd needs to start with true. - repeating the "digit digitValue" or other variations adds clutter and reduces clarity - ((digit digitValue * 2) - 9) is not unreasonable, but could be simplified. What is the largest integer X such that 2xX<=9? > > > the answer schould be 57 where I get 1157 > > > > So some debugging to do > > > > >

2 1