December 2021 - Pharo-users

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

grants Master Internship / offres de stage Master
by Pierre Bommel Feb. 10, 2022

Feb. 10, 2022

(sorry for redundancies) Hello, Bonjour, Hola, We are looking for a Master internship to work on Cormas, a simulation platform (https://github.com/cormas/cormas , or see here for our presentation at ESUG: https://hackmd.iscpif.fr/GGwvzBFqRASE5zCzlRwArQ?view) Nous recherchons un stagiaire de Master pour travailler sur Cormas, une plateforme de simulation (https://github.com/cormas/cormas , cf. notre prÃ©sentation Ã ESUG: https://hackmd.iscpif.fr/GGwvzBFqRASE5zCzlRwArQ?view) Estamos buscando un estudiante de MaestrÃa para trabajar en Cormas. Voici l'annonce en franÃ§ais (in English below) : https://www.hdigitag.fr/fr/les-offres-de-stage-digitag/ *Simulation participative de la gestion des ressources renouvelables dans des environnements hybrides* *Mots-clÃ©*: Simulation participative, Computer Vision , Smalltalk, Cormas * *DurÃ©e souhaitÃ©e du stageÂ (nombre de mois):*8 * *Date de dÃ©but du stage*: 1/02/2021 * *UnitÃ© de recherche*: Green, Cirad * *Contact*: Bommel Pierre : bommel(a)cirad.fr * *#DigitAg*: Axe 2 : Innovations en agriculture numÃ©rique, Axe 6 : ModÃ©lisation et simulation (systÃ¨mes de production agricole) / Challenge 1 :Â Le challenge agroÃ©cologique, Challenge 2 :Â Le phÃ©notypage rapide, Challenge 6 :Â La gestion des territoires agricoles, Challenge 7 :Â IntÃ©gration de lâagriculture dans les chaÃ®nes de valeur, Challenge 8 : DÃ©veloppement agricole au Sud Lâambition dâÃ©liminer les interfaces physiques qui permettent lâinteraction avec les machines est une idÃ©e ancienne dans le monde de lâinformatique qui a pris plusieurs directions. La plus emblÃ©matique pour le grand public a Ã©mergÃ© en 2005 sous le nom de âprojet Natalâ repris et dÃ©mocratisÃ© par Microsoft dans sa derniÃ¨re version baptisÃ©e âAzure Kinectâ (2019). Ce capteur dÃ©tecte les mouvements et les objets dans le champ de vision de lâutilisateur pour produire des rÃ©sultats dans un logiciel. Il a Ã©tÃ© abondamment dÃ©tournÃ© et enrichi depuis ses dÃ©buts grand public pour permettre de nouvelles maniÃ¨res dâinteragir avec les machines. Par ailleurs, le groupe de chercheurs Ã lâorigine de la crÃ©ation dâune plateforme de modÃ©lisation Ã base dâagents baptisÃ©e Cormas [1] fait actuellement face Ã des besoins accrus dâinteractivitÃ©s dans les simulations participatives. BasÃ©e sur le langage Smalltalk, Cormas est dÃ©veloppÃ©e depuis la fin des annÃ©es 1990 par une Ã©quipe fortement interdisciplinaire. Au-delÃ des usages traditionnels de la modÃ©lisation agents, Cormas se dÃ©marque des autres plateformes par des processus originaux de modÃ©lisation : lâapproche ComMod (pour Companion Modeling : modÃ©lisation dâaccompagnement [2]), qui vise Ã proposer des outils permettant de participer activement Ã la conception dâun modÃ¨le, mais aussi de sâimmerger dans des situations de jeux interactifs. Le jeu (de plateau ou informatisÃ©) sert alors de support pour Ã©changer sur une situation vÃ©cue. En 2012, pour la premiÃ¨re fois, lâÃ©quipe utilisait un video-projecteur Ã ultra-courte focale pour projeter sur une table un plateau de jeu. Ce simple changement a induit des comportements radicalement diffÃ©rents leur permettant une interaction beaucoup plus naturelle avec les simulations informatisÃ©es. En outre, la configuration spatiale des acteurs favorise les interactions sociales. Mais jusquâÃ aujourdâhui, la saisie manuelle par lâanimateur des dÃ©cisions prises par les joueurs reste nÃ©cessaire ce qui rÃ©duit la fluiditÃ© et la spontanÃ©itÃ© des interactions. LâÃ©quipe en charge du dÃ©veloppement de Cormas souhaite investiguer les possibilitÃ©s offertes par les nouvelles applications liÃ©es Ã la dÃ©tection dâobjets et de mouvements en portant un prototype de simulation participative dans le champ de la simulation hybride entre modÃ¨le informatique et jeu physique. Ce travail de preuve de concept appliquÃ© au modÃ¨le ReHab (modÃ¨le Ã©cole de ComMod) nÃ©cessitera de mettre au point des mÃ©thodes de dÃ©tection fiables dâobjets physiques pour Ãªtre intÃ©grÃ©es dans le calcul du nouvel Ã©tat simulÃ©. Aujourdâhui, Cormas sâappuie sur Pharo (Smalltalk open-source). Cette solution est dÃ©veloppÃ©e par lâINRIA et par un consortium de chercheurs et dâindustriels. La communautÃ© dynamique propose un ensemble de packages permettant de mutualiser le dÃ©veloppement de fonctionnalitÃ©s qui pourraient Ãªtre mobilisÃ©es pour proposer un prototype pour des simulation participative et la dÃ©tection dâobjets *English* : https://www.hdigitag.fr/en/digitag-master2-internship-offers/ *Participatory simulation of renewable resource management in hybrid environments* * *Keywords*: Participatory simulation, Computer Vision , Smalltalk, Cormas * *Duration*: 8 months * *Desired start date*: 1/02/2021 * *Research Unit*: Green, Cirad * *Contact*: Bommel Pierre â bommel(a)cirad.fr * *#DigitAg*: Axe 2,Axe 6 â Challenge 1,Challenge 2 ,Challenge 6 ,Challenge 7, Challenge 8 The ambition to remove the physical interfaces that allow interactions with computers is an old idea in the IT world that took several directions. The most emblematic one for the general public emerged in 2005 under the name of âProject Natalâ taken up and democratized by Microsoft in its latest version called âAzure Kinectâ (2019). This sensor detects movements and objects in the userâs field of vision to produce results in softwares.Â It has been abundantly diverted and enriched since its beginnings for the general public to allow new ways of interacting with computers. In addition, the group of researchers behind the development of an agent-based modeling platform called Cormas [1] is currently facing increased needs for interactivity in participatory simulations. Based on the Smalltalk language, Cormas has been developed since the late 1990s by a highly interdisciplinary team. Beyond the traditional uses of agent modeling, Cormas differs from other platforms by innovative modeling processes: the ComMod approach (Companion Modeling [2]), which aims to provide tools to actively participate in the design of a model, but also to immerse oneself in interactive game situations.Â The game (board or computer game) is then used as a support to exchange on a real-life situation. In 2012, for the first time, the team used an ultra-short focal projector to project a game board on a table. This simple change induced radically different behaviors of the actors allowing them to interact more naturally with computer simulations. In addition, the spatial configuration of the actors favors social interactions.Â But until today, manual input by the facilitator of the decisions taken by the players remains necessary, which reduces the fluidity and spontaneity of interactions. The team in charge of Cormasâ development wishes to investigate the possibilities offered by new opportunities related to the detection of objects and movements by bringing a prototype of participatory simulation in the field of hybrid simulation between computer model and physical game.This proof of concept work applied to the ReHab model (ComModâs school model) will require the development of reliable detection methods for physical objects to be integrated into the calculation of the new simulated state. Today, Cormas relies on Pharo (an open-source Smalltalk).Â This solution is implemented by INRIA and a consortium of researchers and industrialists. The dynamic community proposes a set of packages allowing to mutualize the development of functionalities that could be mobilized to propose a prototype for participative simulation and object detection

1 1

Pharo-WebView
by TomaÅ¾ Turk Jan. 5, 2022

Jan. 5, 2022

Dear all, Pharo-WebView package is now available on GitHub at https://github.com/eftomi/Pharo-Webview. Pharo-WebView is a package which implements a binding to webview dll library available at https://github.com/webview/webview in Pharo. Webview allows you to show HTML user interfaces in a native window, inject JavaScript code and HTML content into the window. It renders HTML originating via web requests or as a direct input. I tested it on Windows 64 bit in Pharo 64, I plan to do that on Pharo 32 and Linux, however I don't have access to Mac, so if anybody is interested, I'd be grateful :-) Best wishes, Tomaz

7 13

[ANN] Stargate v7.0.0 [v7.0.0] released!
by Buenos Aires Smalltalk Dec. 29, 2021

Dec. 29, 2021

1 0

Pharo 9 arbitrarily changes temporary variable names
by Robert Briggs Dec. 28, 2021

Dec. 28, 2021

Hi I define temporary variables in a method, e.g. |e r |, e.g. in a unit test, but when I run the test Pharo automatically replaces these with | tmp1 tmp2 |. A similar thing happens with method arguments.Â For example methodName: aString at: anInteger will become methodName: arg1 at: arg2. This has happened through my entire model, not just as described above.Â What is going on.Â Is it a bug, or is there a setting that needs to be changed? Many thanks for any feedback on this. Regards Robert Briggs

3 3

Re: Necessity / Location / Credentials for Repositories listed in iceberg
by in_pharo_users＠nym.hush.com Dec. 27, 2021

Dec. 27, 2021

How can I explore and learn about this? On 26.12.2021 at 3:25 PM, stephane.ducasse(a)free.fr wrote: > >The problem is that sometimes building pharo is not just as simple >as loading the latest version of the dependencies. >After it also depends how the subcomponents are managed if they >are copied within the pharo repo or not. > >S > >> On 26 Dec 2021, at 12:47, in_pharo_users--- via Pharo-users ><pharo-users(a)lists.pharo.org> wrote: >> >> Thanks, Stephane. >> >> I am aware of this now most comfortable possibility to gain >access to the newest image. >> >> I want to prepare to be able to offer feedback when making >changes while working with it; >> esp. reporting on glitches, and, possibly, code contributions. >> >> As of my understanding, up-to-date local repositories in sync >with the image are neccessary to do that. >> >> Am I wrong? >> >> On 22.12.2021 at 11:02 PM, stephane.ducasse(a)free.fr wrote: >>> >>> Hi >>> >>> What I suggest is to load the latest version of Pharo 10 with >the >>> launcher. >>> >>> S >>> >>>> On 20 Dec 2021, at 11:51, in_pharo_users--- via Pharo-users >>> <pharo-users(a)lists.pharo.org> wrote: >>>> >>>> Dear all, >>>> >>>> I would like to load a complete dev image with all >repositories >>> affected for pharo 10 under development. >>>> Is there a documentation I can follow?. >>>> >>>> Where can I find >>>> >>>> pharo-spec2 >>>> pharo-newtools >>>> libgit2-pharo-bindings ? >>>> >>>> Can I acess these? >>>> >>>> Kind regards, >>>> >>>> Friedl

1 0

Pharo9: Lessons in "Learn Pharo" are now black and unreadable
by hedley.finger＠gmail.com Dec. 27, 2021

Dec. 27, 2021

Ubuntu 20.04.3 Pharo-9.0.0+build.1573 I am a noob just getting started with Pharo. After tuning some System preferences (e.g. switching to Pharo Light theme, etc.) the lessons in âLearn Pharoâ available from the âWelcomeâ window are near black and unreadable. When I click on âLearn Pharoâ the initial page is okay (black or blue type on a black background) but doing â`ProfStef go.`â messages opens the next lesson where all text has such a black background it is unreadable. Doing â`ProfStef next.`â or â`ProfStef previous.`â on subsequent pages opens a new page similarly illegible. Iâve searched through all the System prefs but canât figure out which one affects the lesson pages. Regards, Hedley

1 0

Pharo won't start on Ubuntu
by hedley.finger＠gmail.com Dec. 27, 2021

Dec. 27, 2021

Pharo 9 (amd64) Ubuntu 20.04.3 LTS (Focal Fossa) I installed Pharo 9 by following the instructions for Xubuntu 20.04 at [OpenSuse Builder](https://bityl.co/ABlH "OpenSuse Builder"). Next I checked for a starter script: `hedster:~$ which pharo` `/usr/bin/pharo` Then I executed the script â¦ `hedster:~$ pharo` â¦ which did not start the Pharo GUI but produced a pile of error messages I donât understand. Iâm sorry to inflict this on you because it is rather long. See the CLI output below. Regards, Hedster --- `hedley-PC:~$ pharo` `Module not found.` `LGitLibrary(Object)>>error:` `LGitLibrary>>unixModuleName` `LGitLibrary(FFILibrary)>>unixLibraryName` `LGitLibrary(FFILibrary)>>unix64LibraryName` `Unix64Platform>>ffiLibraryName:` `LGitLibrary(FFILibrary)>>libraryName` `FFICalloutMethodBuilder>>libraryName` `FFICalloutMethodBuilder>>createFFICalloutLiteralFromSpec:` `FFICalloutMethodBuilder>>generateFFICallout:spec:` `[ :builder | self generateFFICallout: builder spec: functionSpec ] in FFICalloutMethodBuilder>>generateMethodFromSpec: in Block: [ :builder | self generateFFICallout: builder spec...etc...` `IRBuilder class>>buildIR:` `FFICalloutMethodBuilder>>generateMethodFromSpec:` `FFICalloutMethodBuilder>>generate` `FFICalloutMethodBuilder>>build:` `FFICalloutAPI>>function:library:` `LGitLibrary(Object)>>ffiCall:library:options:` `LGitLibrary(Object)>>ffiCall:library:` `LGitLibrary(Object)>>ffiCall:` `LGitLibrary>>libgit2_init` `[ self libgit2_init.` `self recordInitializationSuccess ] in LGitLibrary>>initializeLibGit2 in Block: [ self libgit2_init....` `BlockClosure>>on:do:` `LGitLibrary>>initializeLibGit2` `LGitLibrary class>>startUp:` `ClassSessionHandler>>startup:` `[ :each | each startup: isImageStarting ] in WorkingSession>>runStartup: in Block: [ :each | each startup: isImageStarting ]` `[ aBlock value: each ] in [ :each | ` `[ aBlock value: each ]` ` on: Exception` ` do: [ :error | self errorHandler handleError: error ] ] in WorkingSession>>runList:do: in Block: [ aBlock value: each ]` `BlockClosure>>on:do:` `[ :each | ` `[ aBlock value: each ]` ` on: Exception` ` do: [ :error | self errorHandler handleError: error ] ] in WorkingSession>>runList:do: in Block: [ :each | ...` `Array(SequenceableCollection)>>do:` `WorkingSession>>runList:do:` `Failed to find SDL2 library.` `SDL2 class(Object)>>error:` `SDL2 class>>findSDL2` `SDL2 class>>moduleName` `SDL2 class>>ffiLibraryName` `SDL2 class(Object)>>ffiLibrary` `SDL2 class(Object)>>ffiCall:` `SDL2 class>>setHint:value:` `SDL2 class>>initLibrary` `SDL2 class>>initEverything` `OSSDL2Driver>>initialize` `OSSDL2Driver class(Behavior)>>new` `OSWindowDriver class>>current` `OSWorldRenderer>>pickMostSuitableWindowDriver` `OSWorldRenderer>>doActivate` `OSWorldRenderer(AbstractWorldRenderer)>>activate` `WorldState>>worldRenderer:` `MorphicUIManager>>activate` `UIManager class>>default:` `UIManagerSessionHandler>>startup:` `[ :each | each startup: isImageStarting ] in WorkingSession>>runStartup: in Block: [ :each | each startup: isImageStarting ]` `[ aBlock value: each ] in [ :each | ` `[ aBlock value: each ]` ` on: Exception` ` do: [ :error | self errorHandler handleError: error ] ] in WorkingSession>>runList:do: in Block: [ aBlock value: each ]` `BlockClosure>>on:do:` `[ :each | ` `[ aBlock value: each ]` ` on: Exception` ` do: [ :error | self errorHandler handleError: error ] ] in WorkingSession>>runList:do: in Block: [ :each | ...` `Array(SequenceableCollection)>>do:` `WorkingSession>>runList:do:` `WorkingSession>>runStartup:` `WorkingSession>>start:` `SessionManager>>launchSnapshot:andQuit:` `[ isImageStarting := self launchSnapshot: save andQuit: quit.` `wait signal ] in SessionManager>>snapshot:andQuit: in Block: [ isImageStarting := self launchSnapshot: save and...etc...` `[ self value.` `Processor terminateActive ] in BlockClosure>>newProcess in Block: [ self value....` `Error: Failed to find SDL2 library.` `SDL2 class(Object)>>error:` `SDL2 class>>findSDL2` `SDL2 class>>moduleName` `SDL2 class>>ffiLibraryName` `SDL2 class(Object)>>ffiLibrary` `SDL2 class(Object)>>ffiCall:` `SDL2 class>>setHint:value:` `SDL2 class>>initLibrary` `SDL2 class>>initEverything` `OSSDL2Driver>>initialize` `OSSDL2Driver class(Behavior)>>new` `OSWindowDriver class>>current` `OSWorldRenderer>>pickMostSuitableWindowDriver` `OSWorldRenderer>>doActivate` `OSWorldRenderer(AbstractWorldRenderer)>>activate` `WorldState>>worldRenderer:` `MorphicUIManager>>activate` `UIManager class>>default:` `UIManagerSessionHandler>>startup:` `[ :each | each startup: isImageStarting ] in WorkingSession>>runStartup: in Block: [ :each | each startup: isImageStarting ]` `[ aBlock value: each ] in [ :each | ` `[ aBlock value: each ]` ` on: Exception` ` do: [ :error | self errorHandler handleError: error ] ] in WorkingSession>>runList:do: in Block: [ aBlock value: each ]` `BlockClosure>>on:do:` `[ :each | ` `[ aBlock value: each ]` ` on: Exception` ` do: [ :error | self errorHandler handleError: error ] ] in WorkingSession>>runList:do: in Block: [ :each | ...` `Array(SequenceableCollection)>>do:` `WorkingSession>>runList:do:` `WorkingSession>>runStartup:` `WorkingSession>>start:` `SessionManager>>launchSnapshot:andQuit:` `[ isImageStarting := self launchSnapshot: save andQuit: quit.` `wait signal ] in SessionManager>>snapshot:andQuit: in Block: [ isImageStarting := self launchSnapshot: save and...etc...` `[ self value.` `Processor terminateActive ] in BlockClosure>>newProcess in Block: [ self value....` `#renderer was sent to nil` `UndefinedObject(Object)>>doesNotUnderstand: #renderer` `UndefinedObject>>doesNotUnderstand: #renderer` `OSWorldRenderer>>osWindowRenderer` `OSWorldRenderer>>checkForNewScreenSize` `WorldState>>doOneCycleNowFor:` `WorldState>>doOneCycleFor:` `WorldMorph>>doOneCycle` `WorldMorph class>>doOneCycle` `[ [ WorldMorph doOneCycle.` `Processor yield.` `false ] whileFalse: [ ] ] in MorphicUIManager>>spawnNewProcess in Block: [ [ WorldMorph doOneCycle....` `[ self value.` `Processor terminateActive ] in BlockClosure>>newProcess in Block: [ self value....`

1 2