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

GSUG -- German Smalltalk User Group : die deutschsprachige Smalltalk-Anwendergemeinde trifft sich jetzt auf LinkedIn

by Nowak, Helge

Hallo Smalltalker! Die weltweite deutschsprachige Smalltalk-Anwendergemeinde hat einen neuen Treffpunkt: die GSUG-Gruppe auf LinkedIn: https://www.linkedin.com/groups/12754122/ Hier wollen wir uns zu allen Themen rund um Smalltalk austauschen: Technologien, Produkte und Projekte vorstellen und diskutieren, Stellenangebote und -gesuche bekanntmachen, und was uns sonst noch zu unserer Lieblingsumgebung bewegt. Die Gruppe ist dialektneutral und offen fÃ¼r Erweiterungen im Geiste von Smalltalk, wie Self, Strongtalk oder Newspeak. Wir sind schon gespannt auf die nÃ¤chsten innovativen Ideen! Wir freuen uns auf Euch! Anmelden und Weitersagen ð Smalltalk ist anders - und das ist gut so! Helge Nowak

Jan. 30, 2023

This week (4/2023) on the Pharo Issue Tracker

by Marcus Denker

This week, we merged 28 Pull requests, fixing 31 issues Fixes ===== - Update BaselineOfPharo with Roassal3 version v0.9.9L #12430 https://github.com/pharo-project/pharo/pull/12430 - checkIfMustRefresh in OmBlockFileStore>>blockForLocalNameAsInteger: #12197 https://github.com/pharo-project/pharo/pull/12197 - Fix for multiple Epicea issues #12375 https://github.com/pharo-project/pharo/pull/12375 - FIX CI issues - FFIExternalString>>#basicHandle:at: calls deprecated message #12405 https://github.com/pharo-project/pharo/pull/12405 - Fix for "Browse this version in Calypso" Error after clicking an unloaded package #12423 https://github.com/pharo-project/pharo/pull/12423 - 12410-Minimal-Image-does-not-open-ChangesFile-correctly #12411 https://github.com/pharo-project/pharo/pull/12411 - fix testTallyInstructions #12393 https://github.com/pharo-project/pharo/pull/12393 - Spotter is broken> DNU #tools #12397 https://github.com/pharo-project/pharo/pull/12397 Cleanups ======== - RubScrolledTextMorph>>#mouseWheel: sends unimplemented message #scrolâ¦ #12402 https://github.com/pharo-project/pharo/pull/12402 - 12416-Fixing-Classes-Reported-by-NoUnusedVariablesLeftTest #12417 https://github.com/pharo-project/pharo/pull/12417 - 12413-Improving-the-dependency-of-Formatter-Settings-with-EFFormatter #12414 https://github.com/pharo-project/pharo/pull/12414 - Move #asNumber from AST-Core to Kernel (where it is also already tested) #12388 https://github.com/pharo-project/pharo/pull/12388 - extract return from ifTrue:ifFalse: in Integer>>#printStringRadix: #12433 https://github.com/pharo-project/pharo/pull/12433 - 11x Cleanups of the kind Cleanup: Condense Calypso packages #12284 https://github.com/pharo-project/pharo/pull/12284 this Changelog is archived at https://github.com/pharo-project/pharo-changelogs/blob/master/weekly/2023/4…

Jan. 27, 2023

Re: Sacrilegeous question : what are compelling use cases for Pharo

by Richard O'Keefe

To Konrad Hinsen: you HERO. On Thu, 26 Jan 2023 at 02:40, Konrad Hinsen <konrad.hinsen(a)fastmail.net> wrote: > "Richard O'Keefe" <raoknz(a)gmail.com> writes: > > > Thus I hypothesise that there is room for Smalltalk as a tool for > > *generating* and configuring HPC code. > > Yes. But it will be hard to convince people that Smalltalk is a better > choice than Python (well established in HPC as you say) for this use > case. > > > My main worry is that when it comes to "bet your whole economy" > > software and worse still, "bet the entire global economy and human > > happiness for centuries" software like climate models, it's > > appropriate to use the very highest quality assurance tools practical, > > including *serious* verification. That's not common practice. > > Indeed, and that's one of my main worries in computational science as > well. There is a culture of scientific validation, but not of technical > verification of artifacts such as code. > > My own project in this space (implemented in Pharo) aims at supporting > *human* verification for the aspects that no automatic tool can possibly > verify. In technical terms, that's verifying the formal specification > rather than the implementation of some method. The first step, which I > have made good progress on, is a specification language for scientific > models and methods that human readers would be happy to proofread. > Details: > > https://github.com/khinsen/leibniz-pharo/ > https://science-in-the-digital-era.khinsen.net/#Leibniz > > Konrad >

Jan. 26, 2023

Re: Sacrilegeous question : what are compelling use cases for Pharo

by Konrad Hinsen

"Richard O'Keefe" <raoknz(a)gmail.com> writes: > Thus I hypothesise that there is room for Smalltalk as a tool for > *generating* and configuring HPC code. Yes. But it will be hard to convince people that Smalltalk is a better choice than Python (well established in HPC as you say) for this use case. > My main worry is that when it comes to "bet your whole economy" > software and worse still, "bet the entire global economy and human > happiness for centuries" software like climate models, it's > appropriate to use the very highest quality assurance tools practical, > including *serious* verification. That's not common practice. Indeed, and that's one of my main worries in computational science as well. There is a culture of scientific validation, but not of technical verification of artifacts such as code. My own project in this space (implemented in Pharo) aims at supporting *human* verification for the aspects that no automatic tool can possibly verify. In technical terms, that's verifying the formal specification rather than the implementation of some method. The first step, which I have made good progress on, is a specification language for scientific models and methods that human readers would be happy to proofread. Details: https://github.com/khinsen/leibniz-pharo/ https://science-in-the-digital-era.khinsen.net/#Leibniz Konrad

Jan. 25, 2023

Re: Squeak By Example 5.3 book

by HernÃ¡n Morales Durand

Probably you'd like to ask the Squeak mailing list instead of Pharo mailing list? Cheers, HernÃ¡n El vie, 20 ene 2023 a las 23:46, <danhunfeldz(a)mail.com> escribiÃ³: > There is a new edition of Squeak by Example which is now 5.3. Amazon is > selling only the old edition from 2011. Can I upload the SBE 5.3 edition > PDF to lulu.com and have it printed as a bound book? >

Jan. 22, 2023

Squeak By Example 5.3 book

by danhunfeldz＠mail.com

There is a new edition of Squeak by Example which is now 5.3. Amazon is selling only the old edition from 2011. Can I upload the SBE 5.3 edition PDF to lulu.com and have it printed as a bound book?

Jan. 21, 2023

[ANN] Pharo Mastodon

by Marcus Denker

Yes, not really news: Since Jan 4, 2018 we have a mastodon account. Esteban created that very early on, for now it re-shares the @pharoproject twitter account. https://mastodon.social/@pharoproject <https://mastodon.social/@pharoproject> I have finally updated https://www.pharo.org/community to link to it. Marcus

Jan. 20, 2023

Re: Removing Calypso rule critiques

by Arturo Zambrano

Hi Sebastian, Try this: ClyCriticBrowserPlugin disable. ClyCriticEnvironmentPlugin disable. ClyNavigationEnvironment reset. best, Arturo On Wed, Jan 18, 2023 at 11:01 AM Sebastian Jordan Montano < sebastian.jordan(a)inria.fr> wrote: > Hello everyone, > > I would like to hide/remove all Calypso rules. I tried in Settings > Code > Browsing > Calypso Browser > "Show critiques method" group but it does not > work. > When you are new in Pharo they are ok because they help you learn Pharo. > But after a time they only bother and occupy space. > > Does anyone know how to make Calypso not show them ? > > thanks, > Sebastian Jordan > -- Arturo Zambrano LinkedIn: https://www.linkedin.com/in/arturozambrano/

Jan. 18, 2023

Removing Calypso rule critiques

by Sebastian Jordan Montano

Hello everyone, I would like to hide/remove all Calypso rules. I tried in Settings > Code Browsing > Calypso Browser > "Show critiques method" group but it does not work. When you are new in Pharo they are ok because they help you learn Pharo. But after a time they only bother and occupy space. Does anyone know how to make Calypso not show them ? thanks, Sebastian Jordan

Jan. 18, 2023

Re: How do I unsubscribe?

by Hedley Finger

Thanks James. I usually only look at the header details when I suspect the sender is a scammer. You learn something new every day. Regards, Hedley Hedley Finger hedley.finger(a)gmail.com On Wed, 18 Jan 2023, 11:14 James Foster, <smalltalk(a)jgfoster.net> wrote: > Hi Hedley, > > If you look at the raw source for the email, it includes the following > lines in the header: > > Reply-To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org > > > Subject: [Pharo-users] How do I unsubscribe? > List-Id: Any question about pharo is welcome <pharo-users.lists.pharo.org> > List-Archive: < > https://lists.pharo.org/archives/list/pharo-users@lists.pharo.org/> > List-Help: <mailto:pharo-users-request@lists.pharo.org?subject=help > <pharo-users-request(a)lists.pharo.org?subject=help>> > List-Owner: <mailto:pharo-users-owner@lists.pharo.org > <pharo-users-owner(a)lists.pharo.org>> > List-Post: <mailto:pharo-users@lists.pharo.org > <pharo-users(a)lists.pharo.org>> > List-Subscribe: <mailto:pharo-users-join@lists.pharo.org > <pharo-users-join(a)lists.pharo.org>> > List-Unsubscribe: <mailto:pharo-users-leave@lists.pharo.org > <pharo-users-leave(a)lists.pharo.org>> > > So, it appears that pharo-users-leave(a)lists.pharo.org is correct. > > James > > On Jan 17, 2023, at 2:18 PM, Hedley Finger <hedley.finger(a)gmail.com> > wrote: > > I can't find any info at the Affinity list-server about unsubscribing from > this list. Presumably there is a special address but I can't think what > command to add after pharo-users-???. TIA. > > Hedley Finger > hedley.finger(a)gmail.com > > > >

Jan. 18, 2023