November 2019 - 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

Test method auto-generation in Calypso
by HernÃ¡n Morales Durand Feb. 1, 2020

Feb. 1, 2020

Hi, I have this idea of typing a method in a Browser and have another code area in the same browser where the method test is "automagically generated". This is, divide the current method pane in two: One for the method being written itself, and another for its test, where at least the method selector could be autogenerated by writing testXXXX Of course being able to jump to the method test would be super nice! (and with a keyboard shortcut). This reminds myself to write the method now instead of forget it forever. Any hints to make this happen in Calypso? Cheers, HernÃ¡n

6 12

sqlite garage
by Jeff Gray Jan. 30, 2020

Jan. 30, 2020

anyone using Garage for accessing SQLite? I am using Garage for MySQL in Pharo 7 on windows and it all works seamlessly but I don't know what connection string to use to connect to a database file that I have in my pharo directory. -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

2 2

Pharo 6.0 and 6.1 64 bit freeze on MacMini
by Ted F.A.van Gaalen Jan. 27, 2020

Jan. 27, 2020

Hi, I reverted to 5.0 because Pharo 6.0 and 6.1 64 bit hangs on my Mac Mini with UDH 4K screen (may that has to do with?) with its maiden image (at first start after download when: I resize or go to full screen. Maybe VM problem? my mac Mini metrics: Hardware Overview: Model Name: Mac mini Model Identifier: Macmini6,2 Processor Name: Intel Core i7 Processor Speed: 2,6 GHz Number of Processors: 1 Total Number of Cores: 4 L2 Cache (per Core): 256 KB L3 Cache: 6 MB Memory: 4 GB Boot ROM Version: MM61.0106.B1F SMC Version (system): 2.8f0 maybe this problem was already reported, but could find it. Kind Regards TedvG

14 77

voyage mongo and transactionality
by Jonathan van Alteren Jan. 22, 2020

Jan. 22, 2020

Hello all, We are having some issues with using Voyage/Mongo for a customer project that I'd like to get your feedback on. The customer application is a form based business web application using Seaside with object persistence using Voyage with MongoDBÂ on Pharo 7.0. The application is deployed on a dedicated Linux production server running MongoDB version 4.2. The application is used to manage meeting agendas and minutes. After opening the agenda view of a future meeting, the user can add an item to the agenda by clicking a button. This calls an item editor component which answers when a Save or Cancel button is clicked. The agenda view component itself also has a Save button, which performs a Voyage save of the object aggregate (agenda + items). We've encountered an issue where a user makes changes to an agenda, but does not click the Save button. Instead, the user closes the browser or uses the navigation to go to a different part of the application. When navigating back to the original agenda, the changes made previously (e.g. items added) are still being displayed, even though they were never explicitly saved. It does not matter if we select the agenda aggregate object instance using Voyage or access it in a different way. Changes to the state of the object are retained, even though a Voyage save was never sent to the agenda instance. The cause seems to be that the Voyage repository caches the object instance and thus on select, it returns an object that is in a different state than how it was persisted. This all seems to come down to object transactionality. We have a need to 'cancel' changes made to an object instance. Before working with Pharo/Smalltalk in a non-image based environment, I was used to do this by retrieving the original object from persistence again. This also allowed for a convenient way to detect changes to an object's state, which we are missing at the moment too. We know that moving to GemStone can help us with these issues, but our current planning of customer projects does not allow us to do this within the next 3 months. And we really need to find a way to tackle these issues . Your feedback is greatly appreciated! Kind regards, Jonathan van Alteren Founding Member | Object Guild jvalteren(a)objectguild.com

9 25

[ANN] XMLParserHTML moved to GitHub
by Torsten Bergmann Jan. 8, 2020

Jan. 8, 2020

Hi, the STHub -> PharoExtras project "XMLParserHTML" was now moved from http://smalltalkhub.com/#!/~PharoExtras/XMLParserHTML to https://github.com/pharo-contributions/XML-XMLParserHTML including the FULL HISTORY The old STHub repo was marked as obsolete - but is linking to the new one. I've also setup an CI job: https://travis-ci.org/pharo-contributions/XML-XMLParserHTML which is green for Pharo 7. Some cleanups, class comments and docu was applied as you can see from commit history. The new version is tagged in git as version 1.6.0 (with a moveable tag 1.6.x in case further hotfixes are required). You can load using Metacello new baseline: 'XMLParserHTML'; repository: 'github://pharo-contributions/XML-XMLParserHTML/src'; load. or from catalog in Pharo 7 or 8. Attached is current dependency graph. More to come soon ... Bye T.

9 23

Namespaces (was Re: Behold Pharo: The Modern Smalltalk)
by Ben Coman Dec. 24, 2019

Dec. 24, 2019

On Thu, Oct 12, 2017 at 8:52 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > horrido wrote > > Having separate namespaces would be really good. > > VisualWorks has them. Why not Pharo? > > I can't remember ever hearing disagreement on this subject. It seems the > only questions have been: 1) how to do them *right*, The default position would be leveraging someone else's experience, so this begs the question, what is wrong in namespace implementations in VW, Gemstone, Squeak (as our immediate neighbours, then plus Dolphin, SmalltalkX, other languages) Are there been any research papers around comparing these? I found the "Pharo on Gemstone VM" talk impressive. The "develop on Pharo deploy on Gemstone" philosophy seems like a nice synergy for Pharo's commercial future. So a naive approach would be to do namespaces just like Gemstone. Maybe its not the best, but would it be "good enough" -- perfection being the enemy of done and all that jazz. cheers -ben > and 2) where they fall on the endless prioritized todo list >

13 24

Parsing in VW
by Steffen MÃ¤rcker Dec. 3, 2019

Dec. 3, 2019

Dear all, I have two questions regarding parsing frameworks. 1) Do you have any insights on the performance of SmaCC VS Xtreams Parsing VS PetitParser? 2) Has anybody started to port PetitParser 2 from Pharo to VW? Is it worth the effort? Sorry for cross-posting, I thought this might interest both communities. Cheers, Steffen

8 26

[ANN] Next Pharo Sprint: Nov 29
by Marcus Denker Nov. 25, 2019

Nov. 25, 2019

We will organize a Pharo sprint / Moose dojo Nov 29, starting at 10:00am. (Local Time Paris). Goals of this sprint: - Pharo 8: Fix issues from tracker https://github.com/pharo-project/pharo/issues <https://github.com/pharo-project/pharo/issues> Remote Sprint: Remotely, you can join us on Discord. During the sprint, we synchronize local and remote Pharo sprinters: http://pharo.org/contribute-events <http://pharo.org/contribute-events> We have added a Board to coordinate the work: https://github.com/orgs/pharo-project/projects/9 <https://github.com/orgs/pharo-project/projects/9> Known Local Sprint meetings - Lille/France: It will be at the Inria Lille, Building B, third floor (RMoD offices). As the building is not open to the public, please contact us before if you plan to come A list of all Pharo Event of the year an be found here: https://association.pharo.org/events <https://association.pharo.org/events>

1 0

open spec window to handle exception and pause execution
by PAUL DEBRUICKER Nov. 23, 2019

Nov. 23, 2019

Hi - I have a subclass of ComposablePresenter (lets call it MyPresenter) that seems to work how I want. When doing some processing I'd like to open MyPresenter when an exception occurs and pass it the exception e.g. [ [self testCondition] whileTrue:[ self doSomeStuff] ] on: MyNotification do:[:ex | self openMyPresenterWith: ex] But that just results in lots of MyPresenter windows opening while the execution of the #whileTrue: loop runs its course. How do I pause the loop so I can use the MyPresenter window to modify and fix the condition that raised the MyNotification? The MyPresenter window just edits the contents of a couple Dictionaries so isn't too tricky but it isn't really as easy to do in a debugger as it is clicking a radio button and a "do it" button. Thanks

3 2

Re: [Pharo-users] Glorp + P3 + SQLite
by Pavel Krivanek Nov. 21, 2019

Nov. 21, 2019

Hi Todd, we want to do some more testing before merging it into the upstream repository. -- Pavel Ät 21. 11. 2019 v 14:34 odesÃlatel Todd Blanchard via Pharo-users < pharo-users(a)lists.pharo.org> napsal: > Hi Pavel, > > I've just gotten around to figuring out BaslineOf and packages. I see > this work is in a branch on your own repository. > > Do you plan to do a pull request back to the original repository? I feel > like we have database code all over the place and no clear "official" > versions. > > Stll trying to figure out what is current and what is obsolete (Garage?) > > On Oct 19, 2019, at 5:18 AM, Pavel Krivanek <pavel.krivanek(a)gmail.com> > wrote: > > Btw. there exists an updated version of Glorp: > github://pavel-krivanek/glorp:8.3.1-23-baseline > But the compatibility of it with SQLite was never tested > > -- Pavel > > so 19. 10. 2019 v 10:27 odesÃlatel Todd Blanchard via Pharo-users < > pharo-users(a)lists.pharo.org> napsal: > >> I loaded GLORP+P3 without issue. >> >> Trying to load SQLite3 - it also wants to load GLORP which complains of >> conflict. >> >> For P3 I used: >> >> Metacello new >> baseline: 'P3'; >> repository: 'github://svenvc/P3'; >> load: 'glorp'. >> >> >> >> For SQLite: >> >> Metacello new >> repository: 'github://PierceNg/glorp-sqlite3:pharo7'; >> baseline: 'GlorpSQLite'; >> load. >> >> >> but this fails with a conflict. I suspect the conflict is it wants to >> load in glorp again. >> >> I would also like to have mysql driver at some point. >> >> Any tips for getting these to play nice together would be great. >> > >

1 0

Re: [Pharo-users] Glorp + P3 + SQLite
by Pavel Krivanek Nov. 21, 2019

Nov. 21, 2019

Btw. there exists an updated version of Glorp: github://pavel-krivanek/glorp:8.3.1-23-baseline But the compatibility of it with SQLite was never tested -- Pavel so 19. 10. 2019 v 10:27 odesÃlatel Todd Blanchard via Pharo-users < pharo-users(a)lists.pharo.org> napsal: > I loaded GLORP+P3 without issue. > > Trying to load SQLite3 - it also wants to load GLORP which complains of > conflict. > > For P3 I used: > > Metacello new > baseline: 'P3'; > repository: 'github://svenvc/P3'; > load: 'glorp'. > > > > For SQLite: > > Metacello new > repository: 'github://PierceNg/glorp-sqlite3:pharo7'; > baseline: 'GlorpSQLite'; > load. > > > but this fails with a conflict. I suspect the conflict is it wants to > load in glorp again. > > I would also like to have mysql driver at some point. > > Any tips for getting these to play nice together would be great. >

2 1

Pharo Techtalk Nov 21
by Marcus Denker Nov. 19, 2019

Nov. 19, 2019

Hi, Next techtalk will be *this* week (Nov 21): Topic: Discussion around Contributing to Pharo8 The idea is to discuss on Discord and may do some examples liveâ¦ Calendar entry: https://association.pharo.org/event-3419546 (sorry for the late announceâ¦ )

1 0

[ANN] XMLParser moved to GitHub
by Torsten Bergmann Nov. 19, 2019

Nov. 19, 2019

Hi, the STHub -> PharoExtras project "XMLParser" was now moved from http://smalltalkhub.com/#!/~PharoExtras/XMLParser to https://github.com/pharo-contributions/XML-XMLParser including the FULL HISTORY The old STHub repo was marked as obsolete - but is linking to the new one. I've also setup an CI job: https://travis-ci.org/pharo-contributions/XML-XMLParser which is green for Pharo 7. Some cleanups, class comments and docu was applied as you can see from commit history. The new version is tagged in git as version 3.5.0 (with a moveable tag 3.5.x in case further hotfixes are required). If you want to load use Metacello new baseline: 'XMLParser'; repository: 'github://pharo-contributions/XML-XMLParser/src'; load. or try to load from catalog in Pharo 7 and 8. For referencing in own baselines I would suggest to use the 3.5.x tag line: ---------------------------------------------------------------------------------------------------- xmlParserOn: spec spec baseline: 'XMLParser' with: [ spec loads: #('Core'); repository: 'github://pharo-contributions/XML-XMLParser:3.5.x/src' ]. spec project: 'XMLParser Tests' copyFrom: 'XMLParser' with: [ spec loads: #('Tests') ]; project: 'XMLParser Tools' copyFrom: 'XMLParser' with: [ spec loads: #('Tools') ] ---------------------------------------------------------------------------------------------------- Currently there is a dependency on OrderPreservingDictionary project which will be thrown out in a later iteration (see attached graph and [1] for more details). More to come soon ... Have fun T. [1] https://lists.pharo.org/pipermail/pharo-users_lists.pharo.org/2019-November…

4 5

[ANN] Pastell moved to GitHub
by Torsten Bergmann Nov. 19, 2019

Nov. 19, 2019

Hi, the STHub -> PharoExtras project "Pastell" (XPath-like DSL that makes navigation in XML DOM trees easier) was now moved from http://smalltalkhub.com/#!/~PharoExtras/Pastell to https://github.com/pharo-contributions/XML-Pastell including the FULL HISTORY The old STHub repo was marked as obsolete - but is linking to the new one. I've also setup an CI job: https://travis-ci.org/pharo-contributions/XML-Pastell which is green for Pharo 7. Some cleanups, class comments and docu was applied as you can see from commit history. The new version is tagged in git as version 1.6.0 (with a moveable tag 1.6.x in case further hotfixes are required). You can load using Metacello new baseline: 'Pastell'; repository: 'github://pharo-contributions/XML-Pastell/src'; load. or from catalog in Pharo 7 or 8. Attached is current dependency graph. SIDE NOTE: ========== If you want to load Pastell and XPath [1] into the same image you will see in Iceberg they have colliding methods. Currently one can not share them since either XPath or Pastell tests are green depending on which one are used. This already was the case in the STHub project versions. I would suggest to only use Pastell or XPath until this could possibly be sorted out in the future. Bye T. [1] https://lists.pharo.org/pipermail/pharo-users_lists.pharo.org/2019-November…

1 0

[ANN] XPath moved to GitHub
by Torsten Bergmann Nov. 19, 2019

Nov. 19, 2019

Hi, the STHub -> PharoExtras project "XPath" was now moved from http://smalltalkhub.com/#!/~PharoExtras/XPath to https://github.com/pharo-contributions/XML-XPath including the FULL HISTORY The old STHub repo was marked as obsolete - but is linking to the new one. I've also setup an CI job: https://travis-ci.org/pharo-contributions/XML-XPath which is green for Pharo 7. Some cleanups, class comments and docu was applied as you can see from commit history. The new version is tagged in git as version 2.2.0 (with a moveable tag 2.2.x in case further hotfixes are required). You can load using Metacello new baseline: 'XPath'; repository: 'github://pharo-contributions/XML-XPath/src'; load. or from catalog in Pharo 7 or 8. Attached is current dependency graph. More to come soon ... Bye T.

1 0

XMLParserStAX moved to GitHub
by Torsten Bergmann Nov. 19, 2019

Nov. 19, 2019

Hi, the STHub -> PharoExtras project "XMLParserStAX" was now moved from http://smalltalkhub.com/#!/~PharoExtras/XMLParserStAX to https://github.com/pharo-contributions/XML-XMLParserStAX including the FULL HISTORY The old STHub repo was marked as obsolete - but is linking to the new one. I've also setup an CI job: https://travis-ci.org/pharo-contributions/XML-XMLParserStAX which is green for Pharo 7. Some cleanups, class comments and docu was applied as you can see from commit history. The new version is tagged in git as version 1.4.0 (with a moveable tag 1.4.x in case further hotfixes are required). You can load using Metacello new baseline: 'XMLParserStAX'; repository: 'github://pharo-contributions/XML-XMLParserStAX/src'; load. or from catalog in Pharo 7 or 8. Attached is current dependency graph. More to come soon ... Bye T.

1 0

[ANN] OrderPreservingDictionary version 1.5.0
by Torsten Bergmann Nov. 19, 2019

Nov. 19, 2019

After - BitmapCharacterSet [1] - XMLWriter [2] were moved to "pharo-contributions" GitHub I also did a pass on OrderPreservingDictionary: https://github.com/pharo-contributions/OrderPreservingDictionary which is now available as 1.5.0 version (and also as moving tag 1.5.x in case we provide further hotfixes). Basically cleanups were applied: - add missing comments - cleanup packaging - fixing typos - adding tools group for GT extensions - align CI definitions with projects like Seaside - CI green again (throwing out non-working Gemstone, volunteers welcomed) - fix catalog entry - deprecating http://smalltalkhub.com/#!/~PharoExtras/OrderPreservingDictionary and http://smalltalkhub.com/#!/~Pharo/OrderPreservingDictionary You can load it using Metacello new baseline: 'OrderPreservingDictionary'; repository: 'github://pharo-contributions/OrderPreservingDictionary/src'; load or via catalog in Pharo 7 and 8. SIDE NOTE: ========== As of today XMLWriter still requires the "OrderPreservingDictionary" project as a dependency. OrderPreservingDictionary could be replaced by OrderedDictionary (same code, in the standard image) - I will do a pass on that later on. For now I focus on moving the XML stuff to GitHub first. [1] https://lists.pharo.org/pipermail/pharo-users_lists.pharo.org/2019-October/… [2] https://lists.pharo.org/pipermail/pharo-users_lists.pharo.org/2019-October/…

1 0

transactional saving of images
by Siemen Baader Nov. 18, 2019

Nov. 18, 2019

Hi, I have had a few occasions where I broke an image because I either ran out of disk space or had an endless loop that grew my image endlessly (I think). But why does Pharo not save the image & .changes file in hidden files named eg ~Pharo.image while it saves? Then it can rename them when saving was successful. Many unix programs do this. (I'm using pharo 6.1 so don't know if newer versions do this) -- Siemen

3 2

Tech talk & demo of Pharo in SoCal this Wednesday
by tbrunz Nov. 18, 2019

Nov. 18, 2019

For those who will be in Southern California this week, I will be giving a talk & demo of Pharo this Wednesday night in Pasadena. Details here: https://www.meetup.com/SGVTech/events/266517925/ -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

1 0

Re: [Pharo-users] Where did all the Comments Go?
by Andrew Black Nov. 15, 2019

Nov. 15, 2019

To try and make some progress, I copied a working image from another machine. On startup (on MacOS 10.14.6) I get this walkback: File class(ProtoObject)>>primitiveFailed: File class(ProtoObject)>>primitiveFailed File class>>fileDescriptorType: File class>>fileDescriptorIsAvailable: Stdio class>>standardIOStreamNamed:forWrite: Stdio class>>stdout VTermOutputDriver class>>stdout BasicCommandLineHandler(CommandLineHandler)>>initializeStdout BasicCommandLineHandler(CommandLineHandler)>>initialize BasicCommandLineHandler>>initialize BasicCommandLineHandler class(Behavior)>>new [ self new activate ] in BasicCommandLineHandler class>>startUp: in Block: [ self new activate ] BlockClosure>>cull: WorkingSession>>executeDeferredStartupActions: 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.... > On 19 Sep 2019, at 17:43 , Andrew Black <apblack(a)pdx.edu> wrote: > > Iâm coming back to Pharo after not having used it for several months. Iâm pleased to see that Pharo 7 is now stable and that work has started on Pharo 8. > > I downloaded a new Pharo Launcher (the old one could no longer figure out which version of the VM to use), used the Launcher to create a Pharo 7.0 stable image, and started loading my packages into it from github. > > My attempt to install the baseline of my code failed when some initialization code could not get the definitionComment for my parser (which is written using SmaCC). Normally, SmaCC stores oneâs whole grammar _as a method comment_ in a method called definitionComment. Oddly, this method was empty, even though the version on disk (in the file Grace-Parser.package/GraceParser.class/class/definitionComment.st) contained the comment, as I expected. > > Hoping to at least complete the installation of my code, I manually copied the comment from this file into Calypso and saved the method. It looked fine, but as soon as I moved Calypso to another method, and then back again, the comment had disappeared. I experimented with adding comments to other methods: they looked fine, and I could save the method, but if I moved to another method and then back, the comment had disappeared. > > Class comments have also disappeared. > > I donât think that this is a Calypso problem, because the loading of code from git would not involve Calypso. Rather it is a code storage problem. I saw a File System primitive failure when I launched my new image, but ignored it; Iâm guessing that the comments disappear because they are only in the file system, whereas the code is in memory. And for some reason I canât access the sources file? The changes file ahs been created as expected. > > I just tried downloading the VM manually, and running the âstableâ image that I created, and this time got a different file system primitive failure on startup: #createDirectory in MacStore. > > Whatâs going on? Whatâs the right way to get a working Pharo in the New World Order? > > Andrew > ____________________________ Prof. Andrew P. Black Department of Computer Science Portland State University Oregon, USA http://www.cs.pdx.edu/~black Telephone: +1 503 725 2411

4 4

Zinc & IdentityServer4
by Siemen Baader Nov. 15, 2019

Nov. 15, 2019

Hi, Iâm trying to log a registered user into a webshop (https://mad.coop.dk) using Zinc, but it uses IdentityServer4 ( https://github.com/IdentityServer/IdentityServer4) for authentication (at https://accounts.cl.coop.dk/) So there are more steps involved than just submitting credentials. Usually I just inspect how things work in the Firefox console, then replicate the interactions in Pharo, but this system is a bit too complex, with many unrelated requests happening. Can anyone guide me towards the correct steps to sign in? thanks Siemen

4 5

[Ann] TF-Login for Seaside 3.3 for Pharo 7
by Pierce Ng Nov. 15, 2019

Nov. 15, 2019

Hi all, Apologies for the x-posting. As per subject, I've ported TF-Login to Seaside 3.3 for Pharo 7. To load, start with fresh Pharo 7 image: Metacello new baseline: 'Seaside3'; repository: 'github://SeasideSt/Seaside:v3.3.3/repository'; load. Metacello new baseline: 'TFLogin'; repository: 'github://PierceNg/TF-Login:pharo7/src'; load. The baseline doesn't load Seaside, in case you want to load it into an image that already has Seaside. Start Test Runner and run the TF-Login tests. All 62 tests should pass. Pierce

1 0