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

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

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

OSProcess and CommandShell available on GitHub for Pharo users
by David T. Lewis Oct. 15, 2019

Oct. 15, 2019

Alistair Grant and I, with the support of Feenk, have made GitHub repositories for OSProcess and CommandShell at: https://github.com/dtlewis290/OSProcess-Tonel https://github.com/dtlewis290/CommandShell-Tonel Alistair did the conversions using Peter Uhn??k's migration tool, and I set up the repositories so that they can now be loading in Pharo as follows: Metacello new repository: 'github://dtlewis290/OSProcess-Tonel/src'; baseline: 'OSProcess'; load. Metacello new repository: 'github://dtlewis290/CommandShell-Tonel/src'; baseline: 'CommandShell'; load. Note, the two respositories are named *-Tonel because I also maintain a GitHub repository for OSProcess on Cuis, and will probably do repositories in Squot format in the future. @Thierry Goubier - If you have an account on GitHub I will add you as a collaborator (but my own development work remains on squeaksource so I prefer contributions there anyway). Enjoy, Dave and Alistair

2 5

Testing "Weekly Digest" for GitHub
by Marcus Denker Sept. 30, 2019

Sept. 30, 2019

Hi, There is a ProBot that creates an issue with a weekly summary. By installing it for testing, we got the first report: Weekly Digest (1 July, 2019 - 8 July, 2019) https://github.com/pharo-project/pharo/issues/381 I will do some fine-tuning (e.g. disable commits and star-gazers) later. We then can let it run for some weeks and see if it is useful or not. Marcus

1 7

Microsoft COM
by Ben Coman Sept. 27, 2019

Sept. 27, 2019

Hi Pablo, At work I managed to remote control Internet Explorer with Excel VBA like this... [1] http://www.automateexcel.com/vba/automate-internet-explorer and went looking for how similar might be achieved from Pharo. IIUC I discovered this would be done via Microsoft's Component Object Model, and then I bumped into your repo... [2] https://github.com/tesonep/pharo-com Could you advise the status and your plans for this? Since I see its only a few months old I've probably stumbled onto it prematurely, but I see no documentation or tests to discover how to use it. So I'll curious whether it makes something like [1] possible? And could you show how that would be done? cheers -ben P.S. For context, at work I automated IE since the intranet document management system (OpenText) does authentication via a javascript function in the browser, which doesn't compute with Microsoft's MSXML.DOMDocument component. So I use IE to do the authentication and grab the raw XML from IE to then stuff it into MSXML.DOMDocument from which I pull the data I need. But I'd love to do it with Pharo instead (if I can get IT to white list it) cheers -ben

7 10

Information on Spec development
by Cyril Ferlicot Aug. 13, 2019

Aug. 13, 2019

Hello everyone! This is an important update about the development of Spec. As you might have heard, we are working on Spec to release a new version in Pharo 8. One goal is to unify all Pharo interfaces behind one GUI framework and a second goal is to allow multiple back-ends (Morphic but also GTK, Bloc, ...). To reach those goals we have been updating the current version of Spec. We see now, however, that updating Spec directly creates troubles with migration. For example, we currently have a lot of deprecation warnings in Iceberg, because we can't update it without breaking Pharo 7 compatibility. After some discussions between the engineers working on Spec, here is our plan to improve the situation: We will copy all classes of Spec and rename them with the "Sp" prefix. (We will also ensure that every class of Spec started with the same prefix for consistency). For extensions methods, we will rename them to have a version different from Spec 1 (The spec from Pharo 7). Once done we will integrate this new version in Pharo 8. From there we will wait some weeks to let users who started to use the updated Spec change their projects to use this new Spec2. Finally, we will revert all changes that happened on Spec 1 and deprecate the packages. We hope this will make things easier for everyone. Have a nice day! -- Cyril Ferlicot https://ferlicot.fr

6 10