January 2024 - Pharo-users - lists.pharo.org

Re: Backing up data

by sergio ruiz

Let me check it out. Itâs not too late. This is a fun âscratch my own itchâ project. So there are no deadlines looming or anything.. > On Jan 31, 2024, at 9:20â¯AM, Tim Mackinnon <tim(a)testit.works> wrote: > > Sergio - might be too late now, but I haven't seen anyone mention Sean's solution - https://github.com/seandenigris/Simple-Persistence (I think it uses Fuel under the hood, but its a nice simple solution) > ---- peace, sergio photographer, journalist, visionary Public Key: https://pgp.key-server.io/pks/lookup?op=get&search=0x69B08F58923AB3A2 #BitMessage BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV @sergio_101@mastodon.social https://sergio101.com http://www.codeandmusic.com http://www.twitter.com/sergio_101 http://www.facebook.com/sergio101

Jan. 31, 2024

Re: Backing up data

by Tim Mackinnon

Sergio - might be too late now, but I haven't seen anyone mention Sean's solution - https://github.com/seandenigris/Simple-Persistence (I think it uses Fuel under the hood, but its a nice simple solution) Tim On Thu, 18 Jan 2024, at 4:48 AM, sergio ruiz wrote: > I have been in the relational database world for decades. One of the things that is super simple is backing up and restoring data. > > Sometimes, it makes it makes sense to pull the production data into development. In the case of a catastrophe, itâs super simple to restore data from a backup. > > I am thinking of backup strategies for my data once again, and am wondering if things have changed since I was last using smalltalk. > > I am thinking of the following: > > STON > I could dump all of my data into STON, but there is one slight twist. In this project, itâs just making a list of movie listings. There are three basic classes: Theater, Movie, Event. Each of these classes stores an OrderedCollection of items of that type on a class variable, as Iâll need to access each on their own.. so, if an event has a theater, Iâll need to access Theaters on their own, and Movies on their own. > > So, I would have to rebuild the list of Theaters from the Theaters in each event. Otherwise, I would lose the link between the Theaters on the Theater class variable and the Theater in the Event instance. > > Am I thinking about this incorrectly? > > Gemstones > I am totally into the idea of using gemstones. Is there a backup and restore for objects here? do the relationships remain? > > Voyage > This seems like a good solution, but I would rather stay in the smalltalk object store. > > Ideas? > > Thanks! > > ---- > peace, > sergio > photographer, journalist, visionary > > Public Key: https://pgp.key-server.io/pks/lookup?op=get&search=0x69B08F58923AB3A2 > #BitMessage BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV > @sergio_101@mastodon.social > https://sergio101.com > http://www.codeandmusic.com > http://www.twitter.com/sergio_101 > http://www.facebook.com/sergio101

Jan. 31, 2024

This week (04/2024) on the Pharo Issue Tracker

by Marcus Denker

This week (04/2024) on the Pharo Issue Tracker # Pharo 11 - [Backport] Improve the way to know if a class includes a trait #15987 https://github.com/pharo-project/pharo/pull/15987 # Fixes - Fix: #16011 adding the lost return #16012 https://github.com/pharo-project/pharo/pull/16012 - Improve the way to know if a class includes a trait #15986 https://github.com/pharo-project/pharo/pull/15986 - Fix for Wrong text selection: selection selects an extra character #16010 https://github.com/pharo-project/pharo/pull/16010 - Fix #15997: Enhancement: Add printOn: on PragmaAndShortCutRegistrationItem #15998 https://github.com/pharo-project/pharo/pull/15998 - Fix #15994: morphicUIManager is missing #15995 https://github.com/pharo-project/pharo/pull/15995 - Add missing caret in #textToDisplay method. #15992 https://github.com/pharo-project/pharo/pull/15992 # Refactoring Engine - Refactorings: second pass on preconditions #16017 https://github.com/pharo-project/pharo/pull/16017 - Fix ReDoNotSendSuperInitializeInClassSideRule in Calypso #16007 https://github.com/pharo-project/pharo/pull/16007 - Enh/drivers #16004 https://github.com/pharo-project/pharo/pull/16004 # Cleanup - Remove gofer references #16008 https://github.com/pharo-project/pharo/pull/16008 - Categorize methods in Metacello #16005 https://github.com/pharo-project/pharo/pull/16005

Jan. 29, 2024

UKSTUG Meeting - Pierre Misse-Chanabier: Polyphemus Take 2 - 31 January 2024

by Giovanni Corriga

Pierre Misse-Chanabier will talk to us about Polyphemus ( https://github.com/hogoww/Polyphemus ) for the Pharo Virtual Machine. The presentation will focus on how to create Tooling on the Pharo Virtual Machine. (This does not require Virtual machine level knowledge). We will start by taking a look at a few existing tools. We will create one or two small tools, and see how they differ from tooling on the image side. Pierre Misse Chanabier is a recently graduated PhD with a focused interest on Virtual Machines, Code Generation, and Meta Programming. He worked on and contributed to many different levels and parts of the Pharo ecosystem. He is now working on how to leverage images for more than what they do now. He's currently working at Microdoc ( https://www.microdoc.com ) on the Graal VM. Born in south of France, he currently lives in Lille. This will be an online meeting from home. This is a repeat of last November's presentation that could not go ahead due to issues with our Zoom account. If you'd like to join us, please sign up in advance on the meeting's Meetup page ( https://www.meetup.com/ukstug/events/298169915/ ) to receive the meeting details. Donât forget to bring your laptop and drinks!

Jan. 26, 2024

Books about Pharo

by Richard O'Keefe

This is a new thread because it's not limited to any specific topic. If you have questions about Pharo, especially "how do I do <this> in Pharo", you can always ask in this mailing list. You can, if you like playing Russian Roulette, ask a Large Language Model "AI". But there is an amazing resource you should really trye. books.pharo.org Did you ever wonder where the manual for Pharo was? That's where. The site lists a bunch of Pharo books and booklets, all of which have free PDFs except for two of the books. In particular, you'll always want the most recent edition of "Pharo by Example" handy. These books are really useful. They are written by people know know their material thoroughly and do a good job of explaining it. If you want to make any serious use of Pharo, or even to have more happiness than headaches just playing with it, you owe it to yourself to get the free PDFs What do we owe the authors? Well, if you're not trying to make one pension support four people, you owe them the purchase of some of the books. Me, I'm giving them thanks, praise, and a heartfelt recommendation. Seriously, these books represent a HUGE amount of work and "you are a fool to yourself and a burden to others" if you don't take advantage of this great resource.

Jan. 24, 2024

Re: How to run multiple images?

by Davide Varvello

+1 Cheers On Wednesday, January 24, 2024 at 10:17:31 AM GMT+1, Marcus Denker <marcus.denker(a)inria.fr> wrote: Yes, I would like to have drag-n-drop support, too. Or more specifically: double click of the imagein the Finder opens that image. (I am on the mac)

Jan. 24, 2024

Re: Iterating over a Dictionary

by Richard O'Keefe

This has not changed since Smalltalk-80. Running Smalltalk-80 and looking in the browser, I see Dictionary>> do: aBlock super do: [:assoc | aBlock value: assoc value]. 'super' here is Set, a Dictionary being implemented as a Set of Associations (which was always a bad idea). Dictionary>>do: has ALWAYS iterated over the elements of a dictionary, NOT the associatons. I have Squeak, Pharo, Smalltalk-80, VisuaWorks, VisualAe, Smalltalk/X, and GNU Smalltalk (plus several others including my own). They all follow the ANSI standard in this respect., The distinction between #do: and #associationsDo: goes back to Smalltalk-80, as does #keysDo:. On Wed, 24 Jan 2024 at 05:33, Joachim Tuchel <jtuchel(a)objektfabrik.de> wrote: > > So there we already have dialect differences â¦ > > Am 23.01.2024 um 17:32 schrieb James Foster via Pharo-users <pharo-users(a)lists.pharo.org>: > > ï»¿myDict associationsDo: [: anAssociation | ]. > myDict keysDo: [:aKey | ]. > myDict valuesDo: [:aValue | ]. > myDict do: [:aValue | ]. âAn alias for #valuesDo:â > > James Foster > > On Jan 23, 2024, at 8:27â¯AM, Joachim Tuchel <jtuchel(a)objektfabrik.de> wrote: > > AI knows little about Smalltalk ;-) > > You can use do: with each Association as a parameter or you can use keysAndValuesDo: > > myDic do: [:assoc| | key value| key := assoc key. value := assoc value. ...]. > > myDic keysAndValuesDo: [:key :value| ...] > > > Joachim > > > > Am 23.01.24 um 17:24 schrieb sergio ruiz: > > I need to iterate over a dictionary. > > I asked the AI buddy for a little help, and he says: > > | myDictionary | > > "Create a dictionary" > myDictionary := Dictionary new. > myDictionary at: 'one' put: 1. > myDictionary at: 'two' put: 2. > myDictionary at: 'three' put: 3. > > "Iterate over the dictionary" > myDictionary do: [ :key :value | > Transcript show: key , ' -> ', value printString ; nl. > ]. > > but when i try this, I get: > > ArgumentsCountMismatch: This block accepts 2 arguments, but was called with 1 argument. > > Is the AI using a different dialect of smalltalk? > > how would I go about acting on each pair? > > Thanks! > > ---- > peace, > sergio > photographer, journalist, visionary > > Public Key: https://pgp.key-server.io/pks/lookup?op=get&search=0x69B08F58923AB3A2 > #BitMessage BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV > @sergio_101@mastodon.social > https://sergio101.com > http://www.codeandmusic.com > http://www.twitter.com/sergio_101 > http://www.facebook.com/sergio101 > > -- > > ----------------------------------------------------------------------- > Objektfabrik Joachim Tuchel mailto:jtuchel@objektfabrik.de > Fliederweg 1 http://www.objektfabrik.de > D-71640 Ludwigsburg http://joachimtuchel.wordpress.com > Telefon: +49 7141 56 10 86 0 Fax: +49 7141 56 10 86 1 > >

Jan. 24, 2024

Re: Iterating over a Dictionary

by Richard O'Keefe

Wrong. If you want to iterate of the associations of a dictionary, you need #associationsDo:. #do: passes the *values* to the block, *NOT* the associations. On Wed, 24 Jan 2024 at 05:28, Joachim Tuchel <jtuchel(a)objektfabrik.de> wrote: > > AI knows little about Smalltalk ;-) > > You can use do: with each Association as a parameter or you can use keysAndValuesDo: > > myDic do: [:assoc| | key value| key := assoc key. value := assoc value. ...]. > > myDic keysAndValuesDo: [:key :value| ...] > > > Joachim > > > > Am 23.01.24 um 17:24 schrieb sergio ruiz: > > I need to iterate over a dictionary. > > I asked the AI buddy for a little help, and he says: > > | myDictionary | > > "Create a dictionary" > myDictionary := Dictionary new. > myDictionary at: 'one' put: 1. > myDictionary at: 'two' put: 2. > myDictionary at: 'three' put: 3. > > "Iterate over the dictionary" > myDictionary do: [ :key :value | > Transcript show: key , ' -> ', value printString ; nl. > ]. > > but when i try this, I get: > > ArgumentsCountMismatch: This block accepts 2 arguments, but was called with 1 argument. > > Is the AI using a different dialect of smalltalk? > > how would I go about acting on each pair? > > Thanks! > > ---- > peace, > sergio > photographer, journalist, visionary > > Public Key: https://pgp.key-server.io/pks/lookup?op=get&search=0x69B08F58923AB3A2 > #BitMessage BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV > @sergio_101@mastodon.social > https://sergio101.com > http://www.codeandmusic.com > http://www.twitter.com/sergio_101 > http://www.facebook.com/sergio101 > > -- > > ----------------------------------------------------------------------- > Objektfabrik Joachim Tuchel mailto:jtuchel@objektfabrik.de > Fliederweg 1 http://www.objektfabrik.de > D-71640 Ludwigsburg http://joachimtuchel.wordpress.com > Telefon: +49 7141 56 10 86 0 Fax: +49 7141 56 10 86 1 >

Jan. 24, 2024

Re: Iterating over a Dictionary

by Richard O'Keefe

There are many books about Smalltalk. Stephane Ducasse has made many of them available as FREE pdfs. Of course Pharo by Example would be a good start. The latest edition of Pharo by Example I have ready to hand is 8.0, 2020, where what you want is chapter 13, Collections. aCollection do: [:element | ...] aKeyedCollection keysAndValuesDo: [:key :element | ...] dictionaries are keyed and so are sequences. You can iterate over the elements of any collection using #do: with a one-argument block. The elements will be passed to the block and the keys will NOT. If you want the keys, must use #keysAndValuesDo: with a two-argument block. The keys and corresponding elements will be passed to the block. You "AI buddy" is a treacherous lying ignorant bastard. Such is the start of AI. 1. Open a browser on Dictionary. 2. Select "enumerating" the the method category panel (top row, third from left). 3. In the method panel (top row, rightmost) you will see do: keysAndValuesDo: keysDo: valuesDo: 4. Selecting them one at a time you will see do: aBlock ^self valuesDo: aBlock keysAndValuesDo: aBlock ^self associationsDo: [:assoc | aBlock value: assoc key value: assoc value] keysDo: aBlock ^self associationsDo:: [:association | aBlock value: associatoin key] valuesDo: aBlock tally = 0 ifTrue: [^self]. 1 to: array size do: [:eachIndex | |eachAssociation| eachAssociation := array at: eachIndex. nil == eachAssociation ifFalse: [ aBlock value: eachAssociation value]]. Now to fully make sense of this, you'd have to understand how a Dictionary is implemented in Pharo. (An Array whose elements are reach either nil or an Association holding a key and a value. This is a traditional Smalltalk implementation of dictionaries, but others except and some are better.) But you CAN see quite easily from this code that #do:, #keysDo:, and #valuesDo: pass just one value to their block argument, while #keysAndValuesDo: passes TWO values. And this is typicalk of trying to glean understanding by looking at the system source code: it is easy, you won't undersand everything, but you'll learn *something*. On Wed, 24 Jan 2024 at 05:24, sergio ruiz <sergio.rrd(a)gmail.com> wrote: > > I need to iterate over a dictionary. > > I asked the AI buddy for a little help, and he says: > > | myDictionary | > > "Create a dictionary" > myDictionary := Dictionary new. > myDictionary at: 'one' put: 1. > myDictionary at: 'two' put: 2. > myDictionary at: 'three' put: 3. > > "Iterate over the dictionary" > myDictionary do: [ :key :value | > Transcript show: key , ' -> ', value printString ; nl. > ]. > > but when i try this, I get: > > ArgumentsCountMismatch: This block accepts 2 arguments, but was called with 1 argument. > > Is the AI using a different dialect of smalltalk? > > how would I go about acting on each pair? > > Thanks! > > ---- > peace, > sergio > photographer, journalist, visionary > > Public Key: https://pgp.key-server.io/pks/lookup?op=get&search=0x69B08F58923AB3A2 > #BitMessage BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV > @sergio_101@mastodon.social > https://sergio101.com > http://www.codeandmusic.com > http://www.twitter.com/sergio_101 > http://www.facebook.com/sergio101 >

Jan. 24, 2024

Re: How to run multiple images?

by Marcus Denker

Yes, I would like to have drag-n-drop support, too. Or more specifically: double click of the image in the Finder opens that image. (I am on the mac) I did use it a lot when it worked, but talking to people it seemed that it was not used a lot bu others. I think the reason was that was quite cumbersome, as it only worked for real if you had just *one* VM associated with the .image extension in the Finder. As soon as you need different vms, this stops to be practical, and the Finder even gets confused which vm to use and it is a mess. A real solution would be to have the Launcher be in charge and start the image with the correct VM, this is something I have on my endless TODO to look at to see how hard this would be to support. Marcus > On 23 Jan 2024, at 18:06, sergio ruiz <sergio.rrd(a)gmail.com> wrote: > > I am in the same boat. > > I have been using the pharo launcher for a few years, and it lets you do all of these things with no fuss.. > > check out: https://pharo.org/download > >> On Jan 23, 2024, at 11:39â¯AM, Davide Varvello via Pharo-users <pharo-users(a)lists.pharo.org> wrote: >> >> First: it is not possible anymore to drag and drop the image file on the VM (pharo.app), it was very comfortable. >> >> Second: If I open the pharo.app and choose an image that becomes the only running image, I can't launch the pharo.app to run another image in parallel > > ---- > peace, > sergio > photographer, journalist, visionary > > Public Key: https://pgp.key-server.io/pks/lookup?op=get&search=0x69B08F58923AB3A2 > #BitMessage BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV > @sergio_101@mastodon.social > https://sergio101.com > http://www.codeandmusic.com > http://www.twitter.com/sergio_101 > http://www.facebook.com/sergio101 >

Jan. 24, 2024