February 2022 - Pharo-users

Re: Too many parenthesis - a matter of syntax

by Richard O'Keefe

The fact that there is more than you want is precisely why you want to make classes for the data you *do* want. I do have kit for streaming JSON out directly without creating JSON data internally, but I'm still trying to find a good way to stream JSON in creating wanted objects on-the-fly so that the unwanted data are never stored. I think it can be done from the same schema language that I use to generate classes. On Mon, 28 Feb 2022 at 20:09, Kasper Osterbye <kasper.osterbye(a)gmail.com> wrote: > Thanks Richard, > > I tend to agree with your design experience. As it happens, in my concrete > code I get JSON back from a github api which serves me more than I want. I > am therefore not interested in making classes for those aspects of the data > I throw out. > > The way I handle this in practice myself is to introduce a local variable > for each level. Makes it easier to debug too. > > Best, > > Kasper > > On 27 Feb 2022, at 00.42, Richard O'Keefe <raoknz(a)gmail.com> wrote: > > I was bemused to realise that I've actually been programming > for literally 50 years. It finally seeped through my thick > skull I make enough mistakes that if it's hard to read, I > probably got it wrong. And THIS code fragment is hard to > read. I don't care if you use parentheses or pipes, it's > hard to read either way. Oh, the pipes make the structure > easier to see, true. But I am still left guessing what it > is FOR. What's it SUPPOSED to mean? And the problem is that > there are some abstractions missing. Of course this is JSON's > fault. > > This is the first code smell, and in my experience it is > almost ALWAYS a code smell: you are using JSON as a > "processing" data structure instead of as a "communication" > syntax. Using JSON inside your program, instead of at the > edges, means that the semantics gets scattered all over the > code, which leads to complexity and inconsistency. > > The convention I follow is that data structure more complicated > than a string or an array of numbers has a Smalltalk class > Whatsit>>asJson converts an instance to a JSON value > Whatsit class>>fromJson: converts a JSON value to an instance. > I'll start with > topLevel := TopLevelWhatsit fromJson: someStream nextJson. > and from then on I'm working with pure Smalltalk. > > This has the extra benefit of validating the input right away. > I don't want my program running for several hours and then > running into trouble because some component of the JSON value > is missing or ill-formed. > > In practice, the time cost of converting JSON to (application- > specific) Smalltalk is quite small compared with the cost of > reading the JSON in the first place, and there can be seriously > worthwhile savings in memory. > > For this example, we'd be looking at > topLevel tree blobs > collect: [:each | each path] > thenSelect: [:path | path hasAnyExtension: #('md' 'mic')] > > My Filename class has methods > has[Any]Extension:[ignoringCase:] > which I have shamelessly exploited here. I like the > way that they hide the structure of a Filename. > > The portmanteau methods > Collection>>collect:thenSelect: > Collection>>select:thenCollect: > have existed in Pharo as long as Pharo has existed. > They have two rationales: > (a) improve readability > (b) permit optimisation by eliminating an intermediate collection. > Sequences exploit (b). Sets could too but happen not to. > > THEREFORE, here are free implementations of > Set>>collect:thenSelect: and Set>>select:thenCollect: > consistent with Pharo's Set>>collect: > > collect: collectBlock thenSelect: selectBlock > "Override Collection>>collect:thenSelect: like OrderedCollection. > Beware: 'self species' is often inappropriate, as in #collect:." > |newSet| > newSet := self species new: self size. > self do: [:each | > |item| > item := collectBlock value: each. > (selectBlock value: each) ifTrue: [newSet add: item]]. > ^newSet > > select: selectBlock thenCollect: collectBlock > "Override Collection>>select:thenCollect: like OrderedCollection. > Beware: 'self species' is often inappropriate, as in #collect:." > |newSet| > newSet := self species new: self size. > self do: [:each | > (selectBlock value: each) ifTrue: [ > newSet add: (collectBlock value: each)]]. > ^newSet > > > > On Wed, 26 Jan 2022 at 22:19, Kasper Osterbye <kasper.osterbye(a)gmail.com> > wrote: > >> Cheers all >> >> I have noticed that I often ends up with quite a number of nested >> expressions, for example: >> >> (((json at: 'tree') >> select: [ :e | (e at: 'type') = âblob' ]) >> collect: [:e | Path from: (e at: 'path')]) >> select: [ :p | p segments last >> in: [ :name | (name endsWith: '.md') | >> (name endsWith: '.mic') ] ] >> >> What kind of proposals (if any) have been for a different syntax which >> could give a more streamlined syntax? >> >> My own thinking has been around an alternative to the cascade semicolon. >> What symbol to use does not matter for me, but something like >> json at: âtree' Âº >> select: [ :e | ((e at: 'type') = 'blobâ)]Âº >> collect: [:e | Path from: (e at: 'pathâ)]Âº >> select: [ :p | p segments last >> in: [ :name | (name endsWith: '.md') | (name endsWith: >> '.mic') ] ] >> >> Basically, a send the right hand expression to the result of the left >> hand expression. >> >> Has anyone ever tried this, or is it just one of the many small >> annoyances best left alone? >> >> Best, >> >> Kasper > > >

Feb. 28, 2022

Re: Too many parenthesis - a matter of syntax

by Kasper Osterbye

Thanks Richard, I tend to agree with your design experience. As it happens, in my concrete code I get JSON back from a github api which serves me more than I want. I am therefore not interested in making classes for those aspects of the data I throw out. The way I handle this in practice myself is to introduce a local variable for each level. Makes it easier to debug too. Best, Kasper > On 27 Feb 2022, at 00.42, Richard O'Keefe <raoknz(a)gmail.com> wrote: > > I was bemused to realise that I've actually been programming > for literally 50 years. It finally seeped through my thick > skull I make enough mistakes that if it's hard to read, I > probably got it wrong. And THIS code fragment is hard to > read. I don't care if you use parentheses or pipes, it's > hard to read either way. Oh, the pipes make the structure > easier to see, true. But I am still left guessing what it > is FOR. What's it SUPPOSED to mean? And the problem is that > there are some abstractions missing. Of course this is JSON's > fault. > > This is the first code smell, and in my experience it is > almost ALWAYS a code smell: you are using JSON as a > "processing" data structure instead of as a "communication" > syntax. Using JSON inside your program, instead of at the > edges, means that the semantics gets scattered all over the > code, which leads to complexity and inconsistency. > > The convention I follow is that data structure more complicated > than a string or an array of numbers has a Smalltalk class > Whatsit>>asJson converts an instance to a JSON value > Whatsit class>>fromJson: converts a JSON value to an instance. > I'll start with > topLevel := TopLevelWhatsit fromJson: someStream nextJson. > and from then on I'm working with pure Smalltalk. > > This has the extra benefit of validating the input right away. > I don't want my program running for several hours and then > running into trouble because some component of the JSON value > is missing or ill-formed. > > In practice, the time cost of converting JSON to (application- > specific) Smalltalk is quite small compared with the cost of > reading the JSON in the first place, and there can be seriously > worthwhile savings in memory. > > For this example, we'd be looking at > topLevel tree blobs > collect: [:each | each path] > thenSelect: [:path | path hasAnyExtension: #('md' 'mic')] > > My Filename class has methods > has[Any]Extension:[ignoringCase:] > which I have shamelessly exploited here. I like the > way that they hide the structure of a Filename. > > The portmanteau methods > Collection>>collect:thenSelect: > Collection>>select:thenCollect: > have existed in Pharo as long as Pharo has existed. > They have two rationales: > (a) improve readability > (b) permit optimisation by eliminating an intermediate collection. > Sequences exploit (b). Sets could too but happen not to. > > THEREFORE, here are free implementations of > Set>>collect:thenSelect: and Set>>select:thenCollect: > consistent with Pharo's Set>>collect: > > collect: collectBlock thenSelect: selectBlock > "Override Collection>>collect:thenSelect: like OrderedCollection. > Beware: 'self species' is often inappropriate, as in #collect:." > |newSet| > newSet := self species new: self size. > self do: [:each | > |item| > item := collectBlock value: each. > (selectBlock value: each) ifTrue: [newSet add: item]]. > ^newSet > > select: selectBlock thenCollect: collectBlock > "Override Collection>>select:thenCollect: like OrderedCollection. > Beware: 'self species' is often inappropriate, as in #collect:." > |newSet| > newSet := self species new: self size. > self do: [:each | > (selectBlock value: each) ifTrue: [ > newSet add: (collectBlock value: each)]]. > ^newSet > > > > On Wed, 26 Jan 2022 at 22:19, Kasper Osterbye <kasper.osterbye(a)gmail.com <mailto:kasper.osterbye@gmail.com>> wrote: > Cheers all > > I have noticed that I often ends up with quite a number of nested expressions, for example: > > (((json at: 'tree') > select: [ :e | (e at: 'type') = âblob' ]) > collect: [:e | Path from: (e at: 'path')]) > select: [ :p | p segments last > in: [ :name | (name endsWith: '.md') | (name endsWith: '.mic') ] ] > > What kind of proposals (if any) have been for a different syntax which could give a more streamlined syntax? > > My own thinking has been around an alternative to the cascade semicolon. What symbol to use does not matter for me, but something like > json at: âtree' Âº > select: [ :e | ((e at: 'type') = 'blobâ)]Âº > collect: [:e | Path from: (e at: 'pathâ)]Âº > select: [ :p | p segments last > in: [ :name | (name endsWith: '.md') | (name endsWith: '.mic') ] ] > > Basically, a send the right hand expression to the result of the left hand expression. > > Has anyone ever tried this, or is it just one of the many small annoyances best left alone? > > Best, > > Kasper

Feb. 28, 2022

Re: Too many parenthesis - a matter of syntax

by Richard O'Keefe

I was bemused to realise that I've actually been programming for literally 50 years. It finally seeped through my thick skull I make enough mistakes that if it's hard to read, I probably got it wrong. And THIS code fragment is hard to read. I don't care if you use parentheses or pipes, it's hard to read either way. Oh, the pipes make the structure easier to see, true. But I am still left guessing what it is FOR. What's it SUPPOSED to mean? And the problem is that there are some abstractions missing. Of course this is JSON's fault. This is the first code smell, and in my experience it is almost ALWAYS a code smell: you are using JSON as a "processing" data structure instead of as a "communication" syntax. Using JSON inside your program, instead of at the edges, means that the semantics gets scattered all over the code, which leads to complexity and inconsistency. The convention I follow is that data structure more complicated than a string or an array of numbers has a Smalltalk class Whatsit>>asJson converts an instance to a JSON value Whatsit class>>fromJson: converts a JSON value to an instance. I'll start with topLevel := TopLevelWhatsit fromJson: someStream nextJson. and from then on I'm working with pure Smalltalk. This has the extra benefit of validating the input right away. I don't want my program running for several hours and then running into trouble because some component of the JSON value is missing or ill-formed. In practice, the time cost of converting JSON to (application- specific) Smalltalk is quite small compared with the cost of reading the JSON in the first place, and there can be seriously worthwhile savings in memory. For this example, we'd be looking at topLevel tree blobs collect: [:each | each path] thenSelect: [:path | path hasAnyExtension: #('md' 'mic')] My Filename class has methods has[Any]Extension:[ignoringCase:] which I have shamelessly exploited here. I like the way that they hide the structure of a Filename. The portmanteau methods Collection>>collect:thenSelect: Collection>>select:thenCollect: have existed in Pharo as long as Pharo has existed. They have two rationales: (a) improve readability (b) permit optimisation by eliminating an intermediate collection. Sequences exploit (b). Sets could too but happen not to. THEREFORE, here are free implementations of Set>>collect:thenSelect: and Set>>select:thenCollect: consistent with Pharo's Set>>collect: collect: collectBlock thenSelect: selectBlock "Override Collection>>collect:thenSelect: like OrderedCollection. Beware: 'self species' is often inappropriate, as in #collect:." |newSet| newSet := self species new: self size. self do: [:each | |item| item := collectBlock value: each. (selectBlock value: each) ifTrue: [newSet add: item]]. ^newSet select: selectBlock thenCollect: collectBlock "Override Collection>>select:thenCollect: like OrderedCollection. Beware: 'self species' is often inappropriate, as in #collect:." |newSet| newSet := self species new: self size. self do: [:each | (selectBlock value: each) ifTrue: [ newSet add: (collectBlock value: each)]]. ^newSet On Wed, 26 Jan 2022 at 22:19, Kasper Osterbye <kasper.osterbye(a)gmail.com> wrote: > Cheers all > > I have noticed that I often ends up with quite a number of nested > expressions, for example: > > (((json at: 'tree') > select: [ :e | (e at: 'type') = âblob' ]) > collect: [:e | Path from: (e at: 'path')]) > select: [ :p | p segments last > in: [ :name | (name endsWith: '.md') | > (name endsWith: '.mic') ] ] > > What kind of proposals (if any) have been for a different syntax which > could give a more streamlined syntax? > > My own thinking has been around an alternative to the cascade semicolon. > What symbol to use does not matter for me, but something like > json at: âtree' Âº > select: [ :e | ((e at: 'type') = 'blobâ)]Âº > collect: [:e | Path from: (e at: 'pathâ)]Âº > select: [ :p | p segments last > in: [ :name | (name endsWith: '.md') | (name endsWith: > '.mic') ] ] > > Basically, a send the right hand expression to the result of the left hand > expression. > > Has anyone ever tried this, or is it just one of the many small annoyances > best left alone? > > Best, > > Kasper

Feb. 26, 2022

Re: Too many parenthesis - a matter of syntax

by Kasper Osterbye

All the answers have been good. I am somewhat provoked (in the good sense of forcing me to think) by Siemen who sort of think of it as a code-smell. Best, Kasper > On 26 Feb 2022, at 17.14, Siemen Baader <siemenbaader(a)gmail.com> wrote: > > Hi Kasper, > > perhaps not what you are asking, but I find that this kind of nesting happens to me when parsing serialized data (web page sources or JSON as in your example). For me, the root cause of the problem is that these data structures are not represented by real classes in my code. I often start with what you are showing in a Playground, but then refactor it into specific parsers for the web sites I am scraping. The parsing selectors go into classes that mirror the parts of the data I am interested in. I find this to be more declarative and maintainable, and more natural in the Pharo environment with its browsers and code extractors. > > I hope this is of any use :)

Feb. 26, 2022

Re: Too many parenthesis - a matter of syntax

by Siemen Baader

Hi Kasper, perhaps not what you are asking, but I find that this kind of nesting happens to me when parsing serialized data (web page sources or JSON as in your example). For me, the root cause of the problem is that these data structures are not represented by real classes in my code. I often start with what you are showing in a Playground, but then refactor it into specific parsers for the web sites I am scraping. The parsing selectors go into classes that mirror the parts of the data I am interested in. I find this to be more declarative and maintainable, and more natural in the Pharo environment with its browsers and code extractors. I hope this is of any use :) cheers Siemen On Fri, Jan 28, 2022 at 11:55 PM Vitor Medina Cruz <vitormcruz(a)gmail.com> wrote: > I think that's OK when you can choose when to use parentheses. If you > think it would improve readability it is ok to use it, the problem is to be > forced to use it even when you think it decreases readability, what I > believe to be the case in discussion. > > On Thu, Jan 27, 2022 at 3:24 PM Russ Whaley <whaley.russ(a)gmail.com> wrote: > >> What I like about parentheses (and I hate parentheses) is that it allows >> me to view/describe the intent of the code. When parens are not used, it is >> up to me (perhaps years later) to determine whether the original developer >> (sometimes me) understood (or not) the actual 'order of processing'. >> Parens - or another vehicle - should help me understand the intent (as >> would detailed comments) - so I can devise tests (oh yeah, are those >> available, too?) for the intent - even if it is just me in the debugger. >> >> So, I'm for whatever helps me understand the intent of the code - even if >> there is some slick way to nest everything. I generally prefer breaking >> nested processes down into multiple steps. Benchmarking rarely shows >> significant performance differences, for me. >> >> (and I've used parentheses 7 times in this one email!) :-) >> >> Russ >> >> On Wed, Jan 26, 2022 at 4:20 AM Kasper Osterbye < >> kasper.osterbye(a)gmail.com> wrote: >> >>> Cheers all >>> >>> I have noticed that I often ends up with quite a number of nested >>> expressions, for example: >>> >>> (((json at: 'tree') >>> select: [ :e | (e at: 'type') = âblob' ]) >>> collect: [:e | Path from: (e at: 'path')]) >>> select: [ :p | p segments last >>> in: [ :name | (name endsWith: '.md') | >>> (name endsWith: '.mic') ] ] >>> >>> What kind of proposals (if any) have been for a different syntax which >>> could give a more streamlined syntax? >>> >>> My own thinking has been around an alternative to the cascade semicolon. >>> What symbol to use does not matter for me, but something like >>> json at: âtree' Âº >>> select: [ :e | ((e at: 'type') = 'blobâ)]Âº >>> collect: [:e | Path from: (e at: 'pathâ)]Âº >>> select: [ :p | p segments last >>> in: [ :name | (name endsWith: '.md') | (name endsWith: >>> '.mic') ] ] >>> >>> Basically, a send the right hand expression to the result of the left >>> hand expression. >>> >>> Has anyone ever tried this, or is it just one of the many small >>> annoyances best left alone? >>> >>> Best, >>> >>> Kasper >> >> >> >> -- >> Russ Whaley >> whaley.russ(a)gmail.com >> >

Feb. 26, 2022

R: Re: Image

by kikka

Thank you a lot for you tip about newest version; Iâll take it for sure :) And thanks for your indications; Iâm watching the video you sent. Regards Federica Cordiali saluti Federica Schiavina Da: Tim Mackinnon [mailto:tim@testit.works] Inviato: giovedÃ¬ 24 febbraio 2022 15.21 A: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> Oggetto: [Pharo-users] Re: Image Hi Federica - that is a very old version of Pharo that you are using - you should consider using a much newer version (ideally the latest - as there are many more tools for recovering lost work, and in fact the environment can detect it and prompt you, equally there is GIT integration which is something you should also consider learning about). This said - the above doesn't help you now. You are correct, that the .changes file will have your work in it. I don't quite recall back then what worked - I see in this video https://www.youtube.com/watch?v=jwKDFbPkHzw that you might be able to drag and drop that file to access them - or - worst case is, you can open that file with a pharo editor and then you can hilite sections and use "doit" to re-evaluate them. Or use a text editor to open the file and then find the code you are missing and paste it into pharo. Its a bit painful, but you should be able to get things back reasonably quickly. Someone else might remember more. If you are cutting and pasting - I would consider doing it with a newer version of Pharo. Hope this helps, Tim On Thu, 24 Feb 2022, at 1:45 PM, kikka wrote: Hi everybody, I have a big problem. After working on my application I closed Pharo. When I got back the shortcut wasnât working any more and I realized my image got ruined. I could recover just a very old version of my C:\Seaside-3.1-portable\Seaside-3.1-portable.app\Contents\Resources\Pharo4.0-portable.image (no recent backup). I have seen that all the changes I have developed can be seen in C:\Seaside-3.1-portable\Seaside-3.1-portable.app\Contents\Resources\Pharo4.0-portable.changes I was wondering if it was possible to load all the changes on the old Pharo4.0-portable.image without losing all my work. Hanks in advance for any help. Regards. Federica <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> Mail priva di virus. <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> www.avast.com -- Questa e-mail Ã¨ stata controllata per individuare virus con Avast antivirus. https://www.avast.com/antivirus

Feb. 24, 2022

Re: Image

by Tim Mackinnon

Hi Federica - that is a very old version of Pharo that you are using - you should consider using a much newer version (ideally the latest - as there are many more tools for recovering lost work, and in fact the environment can detect it and prompt you, equally there is GIT integration which is something you should also consider learning about). This said - the above doesn't help you now. You are correct, that the .changes file will have your work in it. I don't quite recall back then what worked - I see in this video https://www.youtube.com/watch?v=jwKDFbPkHzw that you might be able to drag and drop that file to access them - or - worst case is, you can open that file with a pharo editor and then you can hilite sections and use "doit" to re-evaluate them. Or use a text editor to open the file and then find the code you are missing and paste it into pharo. Its a bit painful, but you should be able to get things back reasonably quickly. Someone else might remember more. If you are cutting and pasting - I would consider doing it with a newer version of Pharo. Hope this helps, Tim On Thu, 24 Feb 2022, at 1:45 PM, kikka wrote: > Hi everybody, > > I have a big problem. > > After working on my application I closed Pharo. > > When I got back the shortcut wasnât working any more and I realized my image got ruined. > > I could recover just a very old version of my C:\Seaside-3.1-portable\Seaside-3.1-portable.app\Contents\Resources\Pharo4.0-portable.image (no recent backup). > > I have seen that all the changes I have developed can be seen in C:\Seaside-3.1-portable\Seaside-3.1-portable.app\Contents\Resources\Pharo4.0-portable.changes I was wondering if it was possible to load all the changes on the old Pharo4.0-portable.image without losing all my work. > > Hanks in advance for any help. > > Regards. > > Federica > > <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> > Mail priva di virus. www.avast.com <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campai…> <https://www.fastmail.com/mail/list.1-pharo/compose/Me918b843c4f1c7537ab8ea4…>

Feb. 24, 2022

Image

by kikka

Hi everybody, I have a big problem. After working on my application I closed Pharo. When I got back the shortcut wasn't working any more and I realized my image got ruined. I could recover just a very old version of my C:\Seaside-3.1-portable\Seaside-3.1-portable.app\Contents\Resources\Pharo4.0 -portable.image (no recent backup). I have seen that all the changes I have developed can be seen in C:\Seaside-3.1-portable\Seaside-3.1-portable.app\Contents\Resources\Pharo4.0 -portable.changes I was wondering if it was possible to load all the changes on the old Pharo4.0-portable.image without losing all my work. Hanks in advance for any help. Regards. Federica -- Questa e-mail Ã¨ stata controllata per individuare virus con Avast antivirus. https://www.avast.com/antivirus

Feb. 24, 2022

Re: Changes to class not recorded in change.log?

by Stewart MacLean

Hi Tim, Apologies for not replying sooner - I'm a recent migrant to GMail and it keeps flagging good mail as spam! I haven't explored this further, I think I was using the old Changes Browser. As I'm back to "square one" I've moved on to other problems, but when I get a chance I'll conduct some tests. Thanks, Stew On Tue, Feb 15, 2022 at 4:57 AM Tim Mackinnon <tim(a)testit.works> wrote: > Hi Stewart - are you using the Code Changes (Epicea) browser - or trying > to use the older changes files? > > Your message wasn't clear - and I have seen oddities with Epicea too - but > normally I have been able to recover instance variables too (sometimes the > restore options were a bit confusing and I did it in the wrong order). > > Note - I haven't tried this in V9 though - so possibly something has > regressed. Thought it worth checking though. > > Tim > > On Mon, 14 Feb 2022, at 7:36 AM, Stewart MacLean wrote: > > Hi, > > The worst case scenario has just happened - my image is hosed. > > I've managed to recover a previous set of change/image files (thanks > CrashPlan!). > > Then I've replayed all the intervening changes - however I find that some > instance variables that I had defined haven't been reflected in class shape > changes. > > I notice all the changes for the complete change log are for Method, and > Do It (image saves) > > Surely class shape changes should be recorded as well? Is this a bug? > > Cheers, > > Stewart > > Platform Mac Mini > Pharo 9.0.0 > Build information: > Pharo-9.0.0+build.1573.sha.0e09d756fc99383cbb498565200d9e5e9841ce11 (64 Bit) > > >

Feb. 21, 2022

Fwd: ESUG 2022 call for presentations And Call for student volunteers

by stephane ducasse

A reminderâ¦ S > Begin forwarded message: > > From: "stephane.ducasse(a)free.fr" <stephane.ducasse(a)free.fr> > Subject: ESUG 2022 call for presentations And Call for student volunteers > Date: 13 January 2022 at 13:23:44 CET > > ESUG 2022 > Serbia 22. â 26.8. > > You can support the ESUG conference in many different ways: > Sponsor the conference. New sponsoring packages are described at http://www.esug.org/supportesug/becomeasponsor/ <http://www.esug.org/supportesug/becomeasponsor/> > Submit a talk, a software or a paper to one of the events. See below. > Attend the conference. We'd like to beat the previous record of attendance (170 people at Amsterdam 2008)! > Students can get free registration and hosting if they enroll into the the Student Volunteers program. See below. > <>Developers Forum: International Smalltalk Developers Conference > > We are looking for YOUR experience on using Smalltalk. You will have 30 min for presentations and 45 min for hands-on tutorials. > The list of topics for the normal talks and tutorials includes, but is not limited to the following: > XP practices, Development tools, Experience reports > Model driven development, Web development, Team management > Meta-Modeling, Security, New libraries & frameworks > Educational material, Embedded systems and robotics > SOA and Web services, Interaction with other programming languages > <>Teaching Pearls and Show us Your Business > > New this year!!! We added two types of sessions in addition to the regular talks and show us your projects sessions. > Show your business 10 min session (Get prepared!!) > Teaching pearls : we want some session on how to teach some design aspects. We want your tip and tricks to teach Smalltalk or OOP. > We expect to have several 10 to 15 min sessions aggregated. > <>How to submit? > > Make a Pull Request here https://github.com/ESUG/esug.github.io/tree/source/2022-Conference/talks > > Or but only if you are not connected to the worldâ¦ send an email to stephane.ducasse(a)inria.fr > > Title: [ESUG 2022] Please follow the template below the email will be automatically processed! > Name: > Email: > Abstract: > Bio: > > Call for Student Volunteers > Student volunteers help keep the conference running smoothly; in return, they have free accommodations, while still having most of the time to enjoy the conference. > > Pay attention: the places are limited so do not wait till the last minute to apply. > > Conference details: > Send an email to stephane.ducasse at inria.fr and serge.stinckwich at gmail.com with: > > title: [ESUG 2022 Student] > name, gender, university/school, country, email address > short description of you and why you are interested in participating > For which period is accommodation covered? Accommodation is covered from Sunday 21 August until Friday 26 August 2022 (including nights from Sunday to Monday and from Thursday to Friday). Students will be hosted in student rooms. ESUG additionally covers for the lunches during the week and one dinner. > > Duties include handling registration as people arrive at the conference, filling coffee machines, collecting presentation slides for ESUG right after the presentation is given, being present at an information desk to answer questions, and generally being helpful. Student volunteering makes the conference better, takes a fairly small amount of time and doesn't significantly interfere with enjoying and learning from the conference. Please Note, this role requires discipline and constant attention to all attendees. > > Information about hotel > Student Volunteer rooms are booked at (to be announced). If you are student volunteer, do not book yourself, we have arranged the booking already! >

Feb. 20, 2022

Re: [ANN] Pharo LZ4 Tools

by ducasse

Yes this is a nice conversation. I know that marcus is working on slim binary. The idea is to compress but I forgot if it was bytecode or trees. Now I wonder if the code text is worth compression. >> On 18 Feb 2022, at 21:25, Guillermo Polito <guillermopolito(a)gmail.com> wrote: >> >> Thanks Sven, great stuff :) > > Thanks! > > This allows you to easily play/explore/experiment with certain ideas. > > In the past we discussed about the option of bringing source code inside the image, what if we applied compression ? > > The total size of all Object methods is about 100k: > > Object allMethods sum: [ :each | each sourceCode size ]. > > "104633" > > We can compress each individual method as an LZ4 block and see what that gives us. > > LZ4Compressor new in: [ :compressor | > Object allMethods sum: [ :each | | compressed | > compressed := compressor compressBlock: each sourceCode utf8Encoded. > compressed size ] ]. > > "81584" > > (104633/81584) reciprocal asFloat. > > "0.7797157684478129" > > That is about 22% smaller. This is not a very good result. But that is to be expected because methods are small and there is often not much to compress. > > If we concatenate all source code and feed that as one big chunk to the compressor we get much better results. > > (LZ4Compressor new compress: > (String streamContents: [ :out | > Object allMethods do: [ :each | out nextPutAll: each sourceCode ] ]) utf8Encoded) size. > > "53544" > > (104633/53544) reciprocal asFloat. > > "0.5117314805080615" > > Now we get an almost 50% reduction in size. But methods are independent, so that is not an option. What if we used a dictionary, a predefined set of words/substrings that are common in source code. > > I found a list of the 500 most common English words. Let's add some common selectors and globals. > > IdentityBag new in: [ :bag | > SystemNavigation default allMethods do: [ :each | > each literals select: [ :x | x isSymbol ] thenDo: [ :x | bag add: x ] ]. > bag sortedCounts select: [ :x | x key > 100 ] ]. > > IdentityBag new in: [ :bag | > SystemNavigation default allMethods do: [ :each | > each literals select: [ :x | x isVariableBinding ] thenDo: [ :x | bag add: x key ] ]. > bag sortedCounts select: [ :x | x key > 100 ] ]. > > The smallest possible match in LZ4 is 4 bytes (3 letters and a space). > > words := Character space join: (((FileLocator desktop / 'en-500.csv' readStreamDo: [ :in | (NeoCSVReader on: in) addIgnoredField; addField; upToEnd ]) collect: #first) select: [ :each | each size > 2 ]). > > That are 473 words. Next are 137 selectors. > > selectors := ' ifTrue: assert: class assert:equals: ifTrue:ifFalse: ifNil: ifFalse: yourself name and: ifNotNil: traitComposition add: first deny: includes: isEmpty asString nextPutAll: with: isNil collect: initialize subclassResponsibility to:do: selector localMethodDict should:raise: theme notNil printString on:do: streamContents: at:ifAbsent: copy contents error: last model default ifNil:ifNotNil: organization skipOrReturnWith:ifSkippable: current parserExceptions nonEmpty select: asSymbol name: readStream includesKey: basicNew title: empty reject: whileTrue: keys space class: extent: close anySatisfy: parse:documentURI: isLocalSelector: traitSource second position print: whileFalse: asArray format: printOn: selectors isKindOf: copyFrom:to: color: shouldnt:raise: width height max: named: signal hasProperty: anyOne text detect:ifNone: label: ensure: ifEmpty: extent text: entity addAll: negated includesLocalSelector: addSelector:withMethod: traitDefining:ifNone: hash addSelector:on: asInteger min: translated iconNamed: method arguments position: withIndexDo: perform: methods delete url: occurrencesOf: selector: hResizing: with:with: pass notEmpty flag: values removeKey: fromString: classNamed: reset changed removeKey:ifAbsent: width: announce: repository: signal: setUp addLast: session uniqueInstance assert:description: asOrderedCollection compiledMethod assert:gives: '. > > Finally 73 globals. > > globals := ' String OrderedCollection Array Smalltalk Color Error Character Dictionary TraitChange ByteArray Object UIManager DateAndTime Set Form Time ZTimestamp Date RBParser World Protocol Duration Processor SAXHandler Display MetaLink HelpTopic ReflectivityExamples IdentitySet OCOpalExamples GLMTabulator Float SpecLayout UUID WAMimeType SystemAnnouncer STON XMLDOMParser ZnMimeType Transcript ZnEntity ExternalType CompiledMethod GRPlatform Semaphore FileSystem ReadWriteStream ZnClient WriteStream Delay CmdContextMenuActivation ZnResponse FileLocator IdentityDictionary Morph MCSnapshot ReflectiveMethod XMLValidationException Integer MCMethodDefinition Path ClyClassScope MCClassDefinition RBCondition MCVersionInfo MCVersion SmallInteger Cursor TraitedClass GoferVersionReference SortedCollection MCOrganizationDefinition XMLWellFormednessException '. > > dictionary := (globals , words , selectors) utf8Encoded. > > This dictionary is less than 5K. > > (LZ4Compressor new dictionary: dictionary) in: [ :compressor | > Object allMethods sum: [ :each | | compressed | > compressed := compressor compressBlock: each sourceCode utf8Encoded. > compressed size ] ]. > > "69146" > > (104633/69146) reciprocal asFloat. > > "0.6608431374422983" > > Now we get a 33% reduction in size, which is better. > > I am sure that with a more carefully, better tuned dictionary the compression rate could be improved a couple of percent. There also exist tools that can compute an optimal dictionary from a given input set. > > Sorry for the long post, I hope at least someone found this interesting. > > Sven > > >> EnvoyÃ© depuis mon tÃ©lÃ©phone Huawei >> >> >> -------- Message original -------- >> De : Sven Van Caekenberghe <sven(a)stfx.eu> >> Date : ven. 18 fÃ©vr. 2022 Ã 21:13 >> Ã : Any question about pharo is welcome <pharo-users(a)lists.pharo.org> >> Objet : [Pharo-users] [ANN] Pharo LZ4 Tools >> Hi, >> >> Pharo LZ4 Tools (https://github.com/svenvc/pharo-lz4-tools) is an implementation of LZ4 compression and decompression in pure Pharo. >> >> LZ4 is a lossless compression algorithm that is focused on speed. It belongs to the LZ77 family of byte-oriented compression schemes. >> >> - https://en.wikipedia.org/wiki/LZ4_(compression_algorithm) >> - https://lz4.github.io/lz4/ >> - https://github.com/lz4/lz4 >> >> Both the frame format (https://github.com/lz4/lz4/blob/dev/doc/lz4_Frame_format.md) as well as the block format (https://github.com/lz4/lz4/blob/dev/doc/lz4_Block_format.md) are implemented. Dictionary based compression/decompression is available too. The XXHash32 algorithm is also implemented. >> >> Of course this implementation is not as fast as highly optimised native implementations, but it works quite well and is readable/understandable, if you like this kind of stuff. It can be useful to interact with other systems using LZ4. >> >> Sven

Feb. 20, 2022

Re: [ANN] Pharo LZ4 Tools

by Sven Van Caekenberghe

> On 18 Feb 2022, at 21:25, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > > Thanks Sven, great stuff :) Thanks! This allows you to easily play/explore/experiment with certain ideas. In the past we discussed about the option of bringing source code inside the image, what if we applied compression ? The total size of all Object methods is about 100k: Object allMethods sum: [ :each | each sourceCode size ]. "104633" We can compress each individual method as an LZ4 block and see what that gives us. LZ4Compressor new in: [ :compressor | Object allMethods sum: [ :each | | compressed | compressed := compressor compressBlock: each sourceCode utf8Encoded. compressed size ] ]. "81584" (104633/81584) reciprocal asFloat. "0.7797157684478129" That is about 22% smaller. This is not a very good result. But that is to be expected because methods are small and there is often not much to compress. If we concatenate all source code and feed that as one big chunk to the compressor we get much better results. (LZ4Compressor new compress: (String streamContents: [ :out | Object allMethods do: [ :each | out nextPutAll: each sourceCode ] ]) utf8Encoded) size. "53544" (104633/53544) reciprocal asFloat. "0.5117314805080615" Now we get an almost 50% reduction in size. But methods are independent, so that is not an option. What if we used a dictionary, a predefined set of words/substrings that are common in source code. I found a list of the 500 most common English words. Let's add some common selectors and globals. IdentityBag new in: [ :bag | SystemNavigation default allMethods do: [ :each | each literals select: [ :x | x isSymbol ] thenDo: [ :x | bag add: x ] ]. bag sortedCounts select: [ :x | x key > 100 ] ]. IdentityBag new in: [ :bag | SystemNavigation default allMethods do: [ :each | each literals select: [ :x | x isVariableBinding ] thenDo: [ :x | bag add: x key ] ]. bag sortedCounts select: [ :x | x key > 100 ] ]. The smallest possible match in LZ4 is 4 bytes (3 letters and a space). words := Character space join: (((FileLocator desktop / 'en-500.csv' readStreamDo: [ :in | (NeoCSVReader on: in) addIgnoredField; addField; upToEnd ]) collect: #first) select: [ :each | each size > 2 ]). That are 473 words. Next are 137 selectors. selectors := ' ifTrue: assert: class assert:equals: ifTrue:ifFalse: ifNil: ifFalse: yourself name and: ifNotNil: traitComposition add: first deny: includes: isEmpty asString nextPutAll: with: isNil collect: initialize subclassResponsibility to:do: selector localMethodDict should:raise: theme notNil printString on:do: streamContents: at:ifAbsent: copy contents error: last model default ifNil:ifNotNil: organization skipOrReturnWith:ifSkippable: current parserExceptions nonEmpty select: asSymbol name: readStream includesKey: basicNew title: empty reject: whileTrue: keys space class: extent: close anySatisfy: parse:documentURI: isLocalSelector: traitSource second position print: whileFalse: asArray format: printOn: selectors isKindOf: copyFrom:to: color: shouldnt:raise: width height max: named: signal hasProperty: anyOne text detect:ifNone: label: ensure: ifEmpty: extent text: entity addAll: negated includesLocalSelector: addSelector:withMethod: traitDefining:ifNone: hash addSelector:on: asInteger min: translated iconNamed: method arguments position: withIndexDo: perform: methods delete url: occurrencesOf: selector: hResizing: with:with: pass notEmpty flag: values removeKey: fromString: classNamed: reset changed removeKey:ifAbsent: width: announce: repository: signal: setUp addLast: session uniqueInstance assert:description: asOrderedCollection compiledMethod assert:gives: '. Finally 73 globals. globals := ' String OrderedCollection Array Smalltalk Color Error Character Dictionary TraitChange ByteArray Object UIManager DateAndTime Set Form Time ZTimestamp Date RBParser World Protocol Duration Processor SAXHandler Display MetaLink HelpTopic ReflectivityExamples IdentitySet OCOpalExamples GLMTabulator Float SpecLayout UUID WAMimeType SystemAnnouncer STON XMLDOMParser ZnMimeType Transcript ZnEntity ExternalType CompiledMethod GRPlatform Semaphore FileSystem ReadWriteStream ZnClient WriteStream Delay CmdContextMenuActivation ZnResponse FileLocator IdentityDictionary Morph MCSnapshot ReflectiveMethod XMLValidationException Integer MCMethodDefinition Path ClyClassScope MCClassDefinition RBCondition MCVersionInfo MCVersion SmallInteger Cursor TraitedClass GoferVersionReference SortedCollection MCOrganizationDefinition XMLWellFormednessException '. dictionary := (globals , words , selectors) utf8Encoded. This dictionary is less than 5K. (LZ4Compressor new dictionary: dictionary) in: [ :compressor | Object allMethods sum: [ :each | | compressed | compressed := compressor compressBlock: each sourceCode utf8Encoded. compressed size ] ]. "69146" (104633/69146) reciprocal asFloat. "0.6608431374422983" Now we get a 33% reduction in size, which is better. I am sure that with a more carefully, better tuned dictionary the compression rate could be improved a couple of percent. There also exist tools that can compute an optimal dictionary from a given input set. Sorry for the long post, I hope at least someone found this interesting. Sven > EnvoyÃ© depuis mon tÃ©lÃ©phone Huawei > > > -------- Message original -------- > De : Sven Van Caekenberghe <sven(a)stfx.eu> > Date : ven. 18 fÃ©vr. 2022 Ã 21:13 > Ã : Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > Objet : [Pharo-users] [ANN] Pharo LZ4 Tools > Hi, > > Pharo LZ4 Tools (https://github.com/svenvc/pharo-lz4-tools) is an implementation of LZ4 compression and decompression in pure Pharo. > > LZ4 is a lossless compression algorithm that is focused on speed. It belongs to the LZ77 family of byte-oriented compression schemes. > > - https://en.wikipedia.org/wiki/LZ4_(compression_algorithm) > - https://lz4.github.io/lz4/ > - https://github.com/lz4/lz4 > > Both the frame format (https://github.com/lz4/lz4/blob/dev/doc/lz4_Frame_format.md) as well as the block format (https://github.com/lz4/lz4/blob/dev/doc/lz4_Block_format.md) are implemented. Dictionary based compression/decompression is available too. The XXHash32 algorithm is also implemented. > > Of course this implementation is not as fast as highly optimised native implementations, but it works quite well and is readable/understandable, if you like this kind of stuff. It can be useful to interact with other systems using LZ4. > > Sven

Feb. 20, 2022

UK Smalltalk User Group meeting - 23 February 2022

by Giovanni Corriga

For this month's UKSTUG meeting, we'll open the floor to the whole audience and let people show what they are working on. If you have an interesting project to show, or if you'd like to get some help with some hard problem, just show up and be ready to present! This will be an online meeting from home. If you'd like to join us, please sign up in advance on the meeting's Meetup page ( https://www.meetup.com/UKSTUG/events/284113812/ ) to receive the meeting details. Donât forget to bring your laptop and drinks!

Feb. 19, 2022

Re: [ANN] Pharo LZ4 Tools

by Guillermo Polito

Feb. 18, 2022

[ANN] Pharo LZ4 Tools

by Sven Van Caekenberghe

Hi, Pharo LZ4 Tools (https://github.com/svenvc/pharo-lz4-tools) is an implementation of LZ4 compression and decompression in pure Pharo. LZ4 is a lossless compression algorithm that is focused on speed. It belongs to the LZ77 family of byte-oriented compression schemes. - https://en.wikipedia.org/wiki/LZ4_(compression_algorithm) - https://lz4.github.io/lz4/ - https://github.com/lz4/lz4 Both the frame format (https://github.com/lz4/lz4/blob/dev/doc/lz4_Frame_format.md) as well as the block format (https://github.com/lz4/lz4/blob/dev/doc/lz4_Block_format.md) are implemented. Dictionary based compression/decompression is available too. The XXHash32 algorithm is also implemented. Of course this implementation is not as fast as highly optimised native implementations, but it works quite well and is readable/understandable, if you like this kind of stuff. It can be useful to interact with other systems using LZ4. Sven

Feb. 18, 2022

[ANN] Stargate v7.0.1 [v7.0.1] released!

by Buenos Aires Smalltalk

Feb. 18, 2022

[ANN] Stargate-Consul v3.0.1 [v3.0.1] released!

by Buenos Aires Smalltalk

Feb. 18, 2022

Re: [Issue tracker] Please check your older issues

by Marcus Denker

Thanks to everyone who helped digging through the old issues! We managed to close over 140 issue in 2022 already, with just 801 issues open (and >3500 issues closed overall since we moved to this issue tracker). Often it feels a bit useless âjust one issue downâ¦ what difference does that make?â. But you can only close 3500 issues by looking at each of them, one after the other... Marcus > On 7 Feb 2022, at 11:56, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Hi, > > We are seeing lots of issue that are still open, but already fixed or just not valid anymore. > e.g. > > - the fix that was merged but the issue was not closed (sometimes GitHub has problems doing that) > - Bug was fixed independent of the issue > - The issue is just not relevant anymore > > > It is often quite time consuming to even find out that an issue is already fixedâ¦ > > It would be nice if everyone could check the issues that > > - you submitted yourself > - that are assigned to you > - [Bonus] where you were part of some discussion > > > https://github.com/pharo-project/pharo/issues > > > Marcus

Feb. 15, 2022

Re: Changes to class not recorded in change.log?

by Tim Mackinnon

Hi Stewart - are you using the Code Changes (Epicea) browser - or trying to use the older changes files? Your message wasn't clear - and I have seen oddities with Epicea too - but normally I have been able to recover instance variables too (sometimes the restore options were a bit confusing and I did it in the wrong order). Note - I haven't tried this in V9 though - so possibly something has regressed. Thought it worth checking though. Tim On Mon, 14 Feb 2022, at 7:36 AM, Stewart MacLean wrote: > Hi, > > The worst case scenario has just happened - my image is hosed. > > I've managed to recover a previous set of change/image files (thanks CrashPlan!). > > Then I've replayed all the intervening changes - however I find that some instance variables that I had defined haven't been reflected in class shape changes. > > I notice all the changes for the complete change log are for Method, and Do It (image saves) > > Surely class shape changes should be recorded as well? Is this a bug? > > Cheers, > > Stewart > > Platform Mac Mini > Pharo 9.0.0 > Build information: Pharo-9.0.0+build.1573.sha.0e09d756fc99383cbb498565200d9e5e9841ce11 (64 Bit) >

Feb. 14, 2022

Re: Changes to class not recorded in change.log?

by Marcus Denker

> On 14 Feb 2022, at 08:36, Stewart MacLean <stewart(a)xtra.co.nz> wrote: > > Hi, > > The worst case scenario has just happened - my image is hosed. > > I've managed to recover a previous set of change/image files (thanks CrashPlan!). > > Then I've replayed all the intervening changes - however I find that some instance variables that I had defined haven't been reflected in class shape changes. > > I notice all the changes for the complete change log are for Method, and Do It (image saves) > > Surely class shape changes should be recorded as well? Is this a bug? > Yes, normally the lass change should be recorded, too. So that looks like a bug. Marcus

Feb. 14, 2022

Changes to class not recorded in change.log?

by Stewart MacLean

Hi, The worst case scenario has just happened - my image is hosed. I've managed to recover a previous set of change/image files (thanks CrashPlan!). Then I've replayed all the intervening changes - however I find that some instance variables that I had defined haven't been reflected in class shape changes. I notice all the changes for the complete change log are for Method, and Do It (image saves) Surely class shape changes should be recorded as well? Is this a bug? Cheers, Stewart Platform Mac Mini Pharo 9.0.0 Build information: Pharo-9.0.0+build.1573.sha.0e09d756fc99383cbb498565200d9e5e9841ce11 (64 Bit)

Feb. 14, 2022

Spec border widths of 0 are showing as lines?

by Stewart MacLean

Hi all, I have set the border widths of SpBoxLayout to 0, but there are still lines showing between the various components. Please see attached. As a work around, I thought to set the color of the border to the background color of each panel, but SpBoxLayout doesn't have a borderColor: method. How do I get borders to not show so that adjacent panels blend? And how do I set the color of borders? I am using SpRoassalPresenters and have tried setting the borderColor against them to no effect. Thanks, Stewart

Feb. 11, 2022

Re: [Pharo-users] Re: What is "Fluid"?

by contactme＠kathe.in

On Thursday, February 10, 2022 15:33 CET, Marcus Denker <marcus.denker(a)inria.fr> wrote: Â Â It is a real interesting research question: How an you build Systems that can evolve over a long time ? Systems which evolve over time need to have a very tiny core which is supremely malleable. For one, I would start with a "Forth" and add an object-system to it using the "Metaobject Protocol" along with a Common Lisp like "Condition System". Â Â Forth in the context of the core of an object system is interestingâ¦ someone did in 1979 a Smalltalk and Forth inspired system called âRosetta Smalltalk"Â https://dl.acm.org/doi/10.1145/1113572.1113555Â But: the nice thing of evolving a system is that you *always* can show a real, working result. You can have users, including yourselfâ¦ you can find ways of financingÂ your work that is not just promising something for the future. (which you can only do so often before people get sceptical).Â I think being part of the early Squeak community kind of burned for me the âletâs not improve that (relatively) simple thing A, instead wait for <genius X> to finish <amazing Project Z>.Â Imagine instead you would build a feedback-loop *inside* of your system...Â Â Marcus Agree about what you felt within the Squeak community, I was there too around 1999~2000. There were a bunch of geniuses there, but the way I understand it, geniuses produce the initial spark, but you need strong-willed, perseverent people to kindle the project there-after. The reason I was drawn to Pharo is because of what Ducasse and you and others like you have done with the core spark of Smalltalk-80 based Squeak running Morphic. Though, I've always liked the MVC environment more and fell in love with the "Third-Way" project to deliver a full-blown widget-set for MVC developed by a guy called Gartner (I think) from Germany. Â Do you have a pointer?---- Yes, I got the URL after searching through Google a lot of times. :-) His name is Boris Gaertner and he is/was from Germany. https://wiki.squeak.org/squeak/1829.diff?id=19 I couldn't find his webpage though, and I couldn't locate the code of his framework. Maybe you could ask on the Squeak mailing list! Â Can you elaborate on your feedback-loop *inside* the system idea? Especially in the context of Pharo? Â Â So your âSystems which evolve over time need to have a very tiny core which is supremely malleableâ I actually think is very true.. and Pharo clearly is not there yet.(and what that even is supposed to be.. has many answers).Â But what we technical people are the quickly to say âaÂ malleableÂ system needs a very tiny core, so letâs first do thatâ. And abandon what we have.Â Â But if you step back, for the end-âuserâ (that is programmer) it would not change much, it would solve nothing on that level of the problem of howto evolve a platform *and* the systems using it. Which might be even harder to do right than the kernel...Â Another aspect is that âlets build the perfect evolvable systemâ is as impossible as âlets build the perfect systemââ¦ when you are done, yourealise that you could do even better!Â Â Marcus---- Yes, I agree on the point of things just never being done in the world of software. Though, I do tend to think "Common Lisp" is a done language, but their development environments (even commercial ones) leave a lot to be desired. For a moment think from the perspective of art, as one of the greats had mentioned; perfection is achieved when there's nothing more to take away. I think what you and the core team did using the stuff (core Squeak + Morphic) available to you back then without knowledge about Boris Gaertner's work is quite an achievement. But Pharo is really too big, especially when you compare it with a standard Smalltalk-80 system. Maybe the core team "could" consider going along the same path of cleaning-up and simplifying the core Smalltalk system further but instead of working with the bloat of Morphic, instead go with that MVC-based "ThirdWay" framework! In fact, I would wholeheartedly support the core team changing a lot of what it means to be Smalltalk if the end result can be made smaller and more malleable. As an example of a minimalistic and extremely malleable language, take a look at "io"; https://iolanguage.org/ Yes, it's a lot bigger than a Forth, but at least it won't drive normal people to insanity. :-D Just a suggestion, no intention of denigrating the work that has been done till date. Â

Feb. 11, 2022

Re: What am I doing wrong with Spec2 in Pharo 9?

by Robert Briggs

Thanks Kasper Thatâs kind of what I thought.Â I think itâs because I did not enclose the instance in a layout such as SpBoxLayout which meant I couldnât get the reference to the instance in order to execute valueAtCollumn:row:. Iâve implemented a new subclass to verify this and it works. Regards Bob From: Kasper Osterbye <kasper.osterbye(a)gmail.com> Reply to: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> Date: Thursday, 10 February 2022 at 14:30 To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> Subject: [Pharo-users] Re: What am I doing wrong with Spec2 in Pharo 9? It might be something else, but the browser to the left is looking at the instance side, whereas the browser to the right is looking at the class side. Hence, your class side method openAttributeEditorOn: do not know about the instance side method valueAtColumn:row: It is hard to guess from your code, but I guess you need to capture the table instance in the double click and pass that to the class side, or implement the openAttributeEditorOn: on the instance side to give access self on the instance side. Best, Kasper On 10 Feb 2022, at 12.27, Robert Briggs via Pharo-users <pharo-users(a)lists.pharo.org> wrote: I have a subclass of SpTablePresenter which correctly displays a list of items. It is set up to activateOnDoubleClick as I want to open another SpPresenter I have created on the selected table row using the value in the first column to complete the presenter. My SpTablePresenter headed Element Attributes is shown bottom left in the attached screenshot. The class method top right reports that valueAtColumn:row: is sent but not implemented and yet it clearly is implemented by the superclass of my presenter (and I have used the method elsewhere in my project (NB: this method is just an instrument at the moment so that I can check what is happening. Double clicking a table row executes the method openAttributeEditorOn: but the debugger reports instance of my presenter class did not understand valueAtColumn:row: So what am I doing wrong here? Advice please. Regards Bob Briggs <PharoScreenshot.2.png>

Feb. 10, 2022

Re: What is "Fluid"?

by Offray Vladimir Luna CÃ¡rdenas

On 10/02/22 9:33, Marcus Denker wrote: > > So your âSystems which evolve over time need to have a very tiny core > which is supremely malleableâ I actually think is very true.. and > Pharo clearly is not there yet. > (and what that even is supposed to be.. has many answers). > > But what we technical people are the quickly to say > âaÂ malleableÂ system needs a very tiny core, so letâs first do thatâ. > And abandon what we have. > > But if you step back, for the end-âuserâ (that is programmer) it would > not change much, it would solve nothing on that level of the problem > of how > to evolve a platform *and* the systems using it. Which might be even > harder to do right than the kernel... > > Another aspect is that âlets build the perfect evolvable systemâ is as > impossible as âlets build the perfect systemââ¦ when you are done, you > realise that you could do even better! > > Marcus Recently I was seeing some videos abut GToolkit and Cuis and I thought about how both approach to malleability/understandability in different interesting ways: Cuis by providing a small extensible core that gets simpler over time and GToolkit by providing a compelling default user experience that invites to use and query the system in different ways. I think that the ways Smalltalk systems approach malleability (particularly Pharo/Cuis based) can have deep impacts for populations beyond programmers, as showcased in my recent list post about sharing data stories powered by Pharo, that in fact related with Malleable Systems Wiki [1], [1] https://mutabit.com/repos.fossil/malleable-systems/doc/trunk/wiki/en/mallea… Cheers, Offray

Feb. 10, 2022