- Pharo-users - lists.pharo.org

Re: About String and Symbol equality

by Jupiter Jones

my 2c... There are arguments for and against any of the semantics decisions, so leaving those aside for greater minds... +1 GemStone Pharo and GemStone have long been an enviable workflow for âcomplex problems". They go together in a project, each providing a necessary part of the puzzle. Pharo and VW more often play in the same space, not exactly competitors, but typically the choice of one OR the other for any particular project. Disclaimer - as much as I love VW, I work with GemStone almost every day and can attest that every little divergence between Pharo and GemStone adds a non-trivial burden to the project and team. GS also considers Pharo as a âreferenceâ platform. You mentioned Jamesâ amazing work running a Pharo image on GemStone. They have adopted the Pharo FileSystem, and the latest version has a first-step implementation of traits. Some of the Smalltalk community projects lost to Pharo through traits will get a new lease on life! However, itâs fair to expect that having been in isolation for so long, there will be semantic âgotchasâ to find. Would be nice if they could be minimised as part of Pharos' semantic policy. The closer Pharo & GemStone work together, the easier it will be to achieve awesome end-to-end smalltalk projects, and by extension, make the world a better place :) > On 3 Feb 2025, at 4:35â¯AM, stephane ducasse <stephane.ducasse(a)inria.fr> wrote: > > Hello people > > In Pharo (following Squeak tradition) a string is equals to its symbol representation. > e.g. > âtintinâ = #tintin > > true > > In other Smalltalk dialects this is not the case. > > We have been working (sponsored by Lifeware) to support both semantics (yes this is a kind of > daunting task and it can raise bugs). > > Our objective is to help people make business with Pharo. So âsimpleâ cross compatibility is something that we consider e.g. to deploy applications in Gemstone for example. > (We would love to have a Pharo compiler working on Gemstone generating Gemstone VM bytecodes this is why we love the work of James Foster but this is another story). > > So since we are pragmatic people we could be convinced that the semantics of Pharo is not good :) > and that by default we should use the semantics of GS or VW. > > The first step is to be able to choose which one to use within Pharo and be able to switch. > We are nearly there for Pharo 13. > > The second step is to get a nice default. > And we need the help of the community for this. > > Do you have any advice, arguments for and against any of the two choices that could be put on the table to influence our decisions for Pharo 14. > > So let us know :) > > Stef on the behalf of the Pharo consortium. > > > > StÃ©phane Ducasse > http://stephane.ducasse.free.fr > 06 30 93 66 73 > > "If you knew today was your last day on earth, what would you do differently? ....ESPECIALLY if, by doing something different, today might not be your last day on earth.â Calvin & Hobbes

Feb. 2, 2025

About String and Symbol equality

by stephane ducasse

Hello people In Pharo (following Squeak tradition) a string is equals to its symbol representation. e.g. âtintinâ = #tintin > true In other Smalltalk dialects this is not the case. We have been working (sponsored by Lifeware) to support both semantics (yes this is a kind of daunting task and it can raise bugs). Our objective is to help people make business with Pharo. So âsimpleâ cross compatibility is something that we consider e.g. to deploy applications in Gemstone for example. (We would love to have a Pharo compiler working on Gemstone generating Gemstone VM bytecodes this is why we love the work of James Foster but this is another story). So since we are pragmatic people we could be convinced that the semantics of Pharo is not good :) and that by default we should use the semantics of GS or VW. The first step is to be able to choose which one to use within Pharo and be able to switch. We are nearly there for Pharo 13. The second step is to get a nice default. And we need the help of the community for this. Do you have any advice, arguments for and against any of the two choices that could be put on the table to influence our decisions for Pharo 14. So let us know :) Stef on the behalf of the Pharo consortium. StÃ©phane Ducasse http://stephane.ducasse.free.fr 06 30 93 66 73 "If you knew today was your last day on earth, what would you do differently? ....ESPECIALLY if, by doing something different, today might not be your last day on earth.â Calvin & Hobbes

Feb. 2, 2025

Re: "Book release: Application Building with Spec 2.0" â New blog post on all: objects all: theTime

by giorgio ferraris

Thanks for writing the book, Stefan (and all the other guys) ciao giorgio On Sat, Feb 1, 2025 at 5:07â¯PM stephane ducasse <stephane.ducasse(a)inria.fr> wrote: > Thanks. > Writing this book was a daunting huge difficult exhausting task that took > me around 4 years or more. > > This publisher is managed using a not so great Php software and I can tell > you that you can feel it when > you have to manage the books. > > S > > On 30 Jan 2025, at 17:51, giorgio ferraris <giorgio.ferraris(a)gmail.com> > wrote: > > hello!, > > Thank you for the answer, I ordered the book today, please note that it > still seems that is written in French. > > happy smalltalking > > > giorgio > > On Thu, Nov 7, 2024 at 1:23â¯PM Koen De Hondt < > koen(a)all-objects-all-the-time.st> wrote: > >> Hi Giorgio, >> >> Thank you for reporting the issue. >> >> Yes, it is an error. We saw it a few days ago, but it has not been fixed >> yet. >> >> Best regards, >> Koen >> >> On 7 Nov 2024, at 12:27, giorgio ferraris <giorgio.ferraris(a)gmail.com> >> wrote: >> >> hello, >> >> The Amazon site says that the language is French. Is that an error? >> >> thanks >> >> ciao >> >> giorgio >> >> <Screenshot 2024-11-07 at 12.25.47.png> >> >> On Thu, Nov 7, 2024 at 6:32â¯AM Koen De Hondt < >> koen(a)all-objects-all-the-time.st> wrote: >> >>> Dear Pharo users and developers, >>> >>> It required an enormous effort to review, rewrite, and extend it, but I >>> am happy to announce that it is finally here: the book on application >>> building in Pharo with Spec 2.0. >>> >>> I wrote a blog post about it >>> <https://all-objects-all-the-time.st/#/blog/posts/9>. Happy reading! >>> >>> Ciao, >>> Koen >>> >> >> > StÃ©phane Ducasse > http://stephane.ducasse.free.fr > 06 30 93 66 73 > > "If you knew today was your last day on earth, what would you do > differently? ....ESPECIALLY if, by doing something different, today > might not be your last day on earth.â Calvin & Hobbes > > > > > >

Feb. 2, 2025

Re: "Book release: Application Building with Spec 2.0" â New blog post on all: objects all: theTime

by Mark O'Donoghue

Congratulation Stephane on completing this book. I feel it is crucial. It removes a major hurdle for new, part time and/or returning programmers to get what they need with a UI for their Pharo programs. For me, it also helps me advocating for Pharo with my colleagues. Cheers Mark On Sun, 2 Feb 2025, 12:07 am stephane ducasse, <stephane.ducasse(a)inria.fr> wrote: > Thanks. > Writing this book was a daunting huge difficult exhausting task that took > me around 4 years or more. > > This publisher is managed using a not so great Php software and I can tell > you that you can feel it when > you have to manage the books. > > S > > On 30 Jan 2025, at 17:51, giorgio ferraris <giorgio.ferraris(a)gmail.com> > wrote: > > hello!, > > Thank you for the answer, I ordered the book today, please note that it > still seems that is written in French. > > happy smalltalking > > > giorgio > > On Thu, Nov 7, 2024 at 1:23â¯PM Koen De Hondt < > koen(a)all-objects-all-the-time.st> wrote: > >> Hi Giorgio, >> >> Thank you for reporting the issue. >> >> Yes, it is an error. We saw it a few days ago, but it has not been fixed >> yet. >> >> Best regards, >> Koen >> >> On 7 Nov 2024, at 12:27, giorgio ferraris <giorgio.ferraris(a)gmail.com> >> wrote: >> >> hello, >> >> The Amazon site says that the language is French. Is that an error? >> >> thanks >> >> ciao >> >> giorgio >> >> <Screenshot 2024-11-07 at 12.25.47.png> >> >> On Thu, Nov 7, 2024 at 6:32â¯AM Koen De Hondt < >> koen(a)all-objects-all-the-time.st> wrote: >> >>> Dear Pharo users and developers, >>> >>> It required an enormous effort to review, rewrite, and extend it, but I >>> am happy to announce that it is finally here: the book on application >>> building in Pharo with Spec 2.0. >>> >>> I wrote a blog post about it >>> <https://all-objects-all-the-time.st/#/blog/posts/9>. Happy reading! >>> >>> Ciao, >>> Koen >>> >> >> > StÃ©phane Ducasse > http://stephane.ducasse.free.fr > 06 30 93 66 73 > > "If you knew today was your last day on earth, what would you do > differently? ....ESPECIALLY if, by doing something different, today > might not be your last day on earth.â Calvin & Hobbes > > > > > >

Feb. 1, 2025

Re: "Book release: Application Building with Spec 2.0" â New blog post on all: objects all: theTime

by stephane ducasse

Thanks. Writing this book was a daunting huge difficult exhausting task that took me around 4 years or more. This publisher is managed using a not so great Php software and I can tell you that you can feel it when you have to manage the books. S > On 30 Jan 2025, at 17:51, giorgio ferraris <giorgio.ferraris(a)gmail.com> wrote: > > hello!, > > Thank you for the answer, I ordered the book today, please note that it still seems that is written in French. > > happy smalltalking > > > giorgio > > On Thu, Nov 7, 2024 at 1:23â¯PM Koen De Hondt <koen(a)all-objects-all-the-time.st <mailto:koen@all-objects-all-the-time.st>> wrote: >> Hi Giorgio, >> >> Thank you for reporting the issue. >> >> Yes, it is an error. We saw it a few days ago, but it has not been fixed yet. >> >> Best regards, >> Koen >> >>> On 7 Nov 2024, at 12:27, giorgio ferraris <giorgio.ferraris(a)gmail.com <mailto:giorgio.ferraris@gmail.com>> wrote: >>> >>> hello, >>> >>> The Amazon site says that the language is French. Is that an error? >>> >>> thanks >>> >>> ciao >>> >>> giorgio >>> >>> <Screenshot 2024-11-07 at 12.25.47.png> >>> >>> On Thu, Nov 7, 2024 at 6:32â¯AM Koen De Hondt <koen(a)all-objects-all-the-time.st <mailto:koen@all-objects-all-the-time.st>> wrote: >>>> Dear Pharo users and developers, >>>> >>>> It required an enormous effort to review, rewrite, and extend it, but I am happy to announce that it is finally here: the book on application building in Pharo with Spec 2.0. >>>> >>>> I wrote a blog post about it <https://all-objects-all-the-time.st/#/blog/posts/9>. Happy reading! >>>> >>>> Ciao, >>>> Koen >> StÃ©phane Ducasse http://stephane.ducasse.free.fr 06 30 93 66 73 "If you knew today was your last day on earth, what would you do differently? ....ESPECIALLY if, by doing something different, today might not be your last day on earth.â Calvin & Hobbes

Feb. 1, 2025

Pharo News of the Week 05/2025

by Marcus Denker

# Pharo News of the Week 05/2025 - [Video] Tp33 first pattern programming: https://www.youtube.com/watch?v=EwPuypfRQTg - [ANN] Google Summer of Code 2025: Call for Students https://gsoc.pharo.org If you want to add your news to this list, use this form: https://tinyurl.com/4c89buy4 # The week on the Pharo Issue Tracker # Pharo 11 - Backport fix-SDL-default-renderer-by-platform to Pharo 11 #17696 https://github.com/pharo-project/pharo/pull/17696 # Pharo 12 - Backport correction evaluation of dynamic variables from the debugger #956 - Backport correction evaluation of dynamic variables from the debugger #956 https://github.com/pharo-spec/NewTools/pull/956 - Update version in #newTools for BaselineOfPharo for Pharo 12 to âv0.9.2â #17691 https://github.com/pharo-project/pharo/pull/17691 # Fixes - Do not restore ffi methods if they are not installed #17686 https://github.com/pharo-project/pharo/pull/17686 - Fix broken Pharo image #17712 https://github.com/pharo-project/pharo/pull/17712 - Bring back 'Fit all' menu item #17709 https://github.com/pharo-project/pharo/pull/17709 - Fixes: 17680 RB-Rename-class-from-in-text-editor-select-the-class-of-â¦ #17681 https://github.com/pharo-project/pharo/pull/17681 - 17677 pharo syntax tutorial testtest divide two by zero signals zero divide #17679 https://github.com/pharo-project/pharo/pull/17679 # Rules - Edited two rules to implement that #initializeWindow: has to call super and can't override preferredExtent #17695 https://github.com/pharo-project/pharo/pull/17695 - Refactoring Engine https://github.com/pharo-project/pharo/pull/17654 # Window Handling - Migrate about window to Spec #17708 https://github.com/pharo-project/pharo/pull/17708 - Cleaning window title #17711 https://github.com/pharo-project/pharo/pull/17711 # VM - Forward port 10.3.3 to pharo-12 branch #903 https://github.com/pharo-project/pharo-vm/pull/903 - Improve project structure #904 https://github.com/pharo-project/pharo-vm/pull/904 # Iceberg / Git - Cleaning Spec #1885 https://github.com/pharo-vcs/iceberg/pull/1885 - Removing dead code #1890 https://github.com/pharo-vcs/iceberg/pull/1890 - Fix IceTipCommitBrowser to have a cleaner initialization of the model #1888 https://github.com/pharo-vcs/iceberg/pull/1888 - Clean protocols #1886 https://github.com/pharo-vcs/iceberg/pull/1886 - Improve protocols #89 https://github.com/pharo-vcs/libgit2-pharo-bindings/pull/89 # Newtools - SpClosedWindowPresenter don't add itself in last closed window now #969 https://github.com/pharo-spec/NewTools/pull/969 - No glamorous icon names #968 https://github.com/pharo-spec/NewTools/pull/968 - No glamorous icon names #967 https://github.com/pharo-spec/NewTools/pull/967 - Cleaning title definition #966 https://github.com/pharo-spec/NewTools/pull/966 - Introduce a new About Pharo based on Spec instead of Morphic #965 https://github.com/pharo-spec/NewTools/pull/965 - Categorize an uncategorized method #964 https://github.com/pharo-spec/NewTools/pull/964 - Closed window is now independent and works with Announcements #963 https://github.com/pharo-spec/NewTools/pull/963 - Post cleaning fix2 #962 https://github.com/pharo-spec/NewTools/pull/962 - Post cleaning fixes #961 https://github.com/pharo-spec/NewTools/pull/961 - On the class side of course #960 https://github.com/pharo-spec/NewTools/pull/960 - Fixing the build I hope #959 https://github.com/pharo-spec/NewTools/pull/959 - Cleaning spec #957 https://github.com/pharo-spec/NewTools/pull/957 # Cleanup - Cleaning spec #1709 https://github.com/pharo-spec/Spec/pull/1709 - Cleaning title definition #1711 https://github.com/pharo-spec/Spec/pull/1711 - Cleaning SpMorphic: less duplication around centered #1712 https://github.com/pharo-spec/Spec/pull/1712 - Branch: automatebenchresult, Adding the timing to the benchmarks , aâ¦ #17622 https://github.com/pharo-project/pharo/pull/17622 - Cleanup compiler extensions. #17662 https://github.com/pharo-project/pharo/pull/17662 - AST-Core-Tests should not depend on Monticello #17665 https://github.com/pharo-project/pharo/pull/17665 - Branch: RedoingClosePresenter, Deleted everything so SpClosedWindowListPresenter can be independant #17676 https://github.com/pharo-project/pharo/pull/17676 - Move (OC)DoItVariable to the compiler #17678 https://github.com/pharo-project/pharo/pull/17678 - Cleaning Presenter #17683 https://github.com/pharo-project/pharo/pull/17683 - Post clean fix2 #17693 https://github.com/pharo-project/pharo/pull/17693 - Reintroducing test methods in a way that they are not counted as simiâ¦ #17694 https://github.com/pharo-project/pharo/pull/17694 - Reduce usage of protocol initialize-release #17701 https://github.com/pharo-project/pharo/pull/17701 - Cleanup refactorings #17700 https://github.com/pharo-project/pharo/pull/17700 - Depends on Roassal branch Pharo13 #17705 https://github.com/pharo-project/pharo/pull/17705 - Removed the undeclared for now. #17706 https://github.com/pharo-project/pharo/pull/17706 - Cleanup Tests #17710 https://github.com/pharo-project/pharo/pull/17710

Jan. 31, 2025

Re: "Book release: Application Building with Spec 2.0" â New blog post on all: objects all: theTime

by giorgio ferraris

hello!, Thank you for the answer, I ordered the book today, please note that it still seems that is written in French. happy smalltalking giorgio On Thu, Nov 7, 2024 at 1:23â¯PM Koen De Hondt < koen(a)all-objects-all-the-time.st> wrote: > Hi Giorgio, > > Thank you for reporting the issue. > > Yes, it is an error. We saw it a few days ago, but it has not been fixed > yet. > > Best regards, > Koen > > On 7 Nov 2024, at 12:27, giorgio ferraris <giorgio.ferraris(a)gmail.com> > wrote: > > hello, > > The Amazon site says that the language is French. Is that an error? > > thanks > > ciao > > giorgio > > <Screenshot 2024-11-07 at 12.25.47.png> > > On Thu, Nov 7, 2024 at 6:32â¯AM Koen De Hondt < > koen(a)all-objects-all-the-time.st> wrote: > >> Dear Pharo users and developers, >> >> It required an enormous effort to review, rewrite, and extend it, but I >> am happy to announce that it is finally here: the book on application >> building in Pharo with Spec 2.0. >> >> I wrote a blog post about it >> <https://all-objects-all-the-time.st/#/blog/posts/9>. Happy reading! >> >> Ciao, >> Koen >> > >

Jan. 30, 2025

Google Summer of Code 2025

by Sebastian Jordan

Hello people, We are applying for the GSoC (Google Sumer of Code) this year (again)! Info: https://summerofcode.withgoogle.com/ TLDR: It is an initiative from Google for student/beginner coders to contribute to open-source projects. There are Organizations that propose projects (like us), Google selects some of them, and then the people can read the proposals and apply for them. If they are selected and everything goes ok, Google pays to the student (for his/her work) and to the Organization (for mentoring them). To be selected, we need a good list of ideas/projects where outside people can contribute. We have these from the last year: https://gsoc.pharo.org/ideas. So, Iâm sending this to please ask you: 1. If there is any idea listed where you are supervisor (you can use the filter) -> Check if it is still valid 2. If there is no, you can think of one :) 3. Any change (update of one existing idea, delete or add one) must be done in this JSON: https://github.com/pharo-project/pharo-gsoc/blob/master/data/ideas.json You can: - Send directly a Pull Request with the changes to the repo (https://github.com/pharo-project/pharo-gsoc) ð - Or send us the updated JSON, and weâll push it ð Remember that the mentors of any idea have to be available for: - Response to the student applications - Supervise their work (probably some kind of interactions weekly) It is better to be 2, 3, or 4 mentors per idea so we can guarantee availability. The deadlines (https://developers.google.com/open-source/gsoc/timeline) are: * February 11 - to make the list of ideas * February 27 - Google lists the accepted Organizations * March 24 to April 8 - students apply to projects * June / July / August - CODING More info: https://developers.google.com/open-source/gsoc/resources/guide Thank you all! GSoC organizers from the Pharo Consortium

Jan. 29, 2025

UK Smalltalk User Group meeting: 2024 retrospective and what to expect in 2025 - 29 January 2025

by UK Smalltalk

For our first meeting of the year, we'll hold a retrospective on what has happened in the Smalltalk world in 2024, and discuss what we can expect in 2025. Join us to share what you learned, and what you are looking forward to! 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/305378616/ ) to receive the meeting details. Donât forget to bring your laptop and drinks!

Jan. 28, 2025

Pharo News of the Week 04/2025

by Marcus Denker

# Pharo News of the Week 04/2025 - [ANN] New VM Release v10.3.3 https://www.pharo.org/news/2025-01-21-VM10-3-3.html - [Blog Post]: Subject in SUnit Tests https://all-objects-all-the-time.st/#/blog/posts/ - [Survey] please take a second to take the spotter survey: https://sondages.inria.fr/index.php/319877?lang=en If you want to add your news to this list, use this form: https://tinyurl.com/4c89buy4 # The week on the Pharo Issue Tracker # Pharo 11 - Update version in #iceberg for BaselineOfPharo for Pharo 11 to âv2.2.3â #17644 https://github.com/pharo-project/pharo/pull/17644 # Pharo 12 - Update version in #newTools for BaselineOfPharo for Pharo 12 to âv0.9.1â #17666 https://github.com/pharo-project/pharo/pull/17666 - Update version in #spec for BaselineOfPharo for Pharo 12 to âv1.3.5â #17643 https://github.com/pharo-project/pharo/pull/17643 # Features - Update Fuel for Pharo 13 #17635 https://github.com/pharo-project/pharo/pull/17635 # Fixes - Fixed fall back code on new tenured primitives by jordanmontt Â· Pull Request #17617 Â· pharo-project/pharo https://github.com/pharo-project/pharo/pull/17617 - Calypso: Fix remove protocol when there is no method in the protocol #17628 https://github.com/pharo-project/pharo/pull/17628 - Branch: realunclosewindow, added all behaviors needed to use SpClosedWindowListPresebter #17629 https://github.com/pharo-project/pharo/pull/17629 - Update word navigation to handle different character groups #17630 https://github.com/pharo-project/pharo/pull/17630 - Fix timestamp parsing in SourceFileArray #17633 https://github.com/pharo-project/pharo/pull/17633 # VM - Remove old versions of libgit in new builds #902 https://github.com/pharo-project/pharo-vm/pull/902 # Compiler - Move OpalCompiler-UI tests to OpalCompiler-UI-Tests #17664 https://github.com/pharo-project/pharo/pull/17664 - Move OCBytecodeDecompilerExamplesTest to Flashback #17663 https://github.com/pharo-project/pharo/pull/17663 # Iceberg /Tonel /git - Port Hernan's snapshot browser to Iceberg #1875 https://github.com/pharo-vcs/iceberg/pull/1875 - Improve error messages #123 https://github.com/pharo-vcs/tonel/pull/123 # CI/Bootrap/Image load - Load roassal before NewTool https://github.com/pharo-project/pharo/pull/17650 - Remove double loading of welcome browser #17655 https://github.com/pharo-project/pharo/pull/17655 - Load Microdown before NewTools (Anyway NewTools will load it) #17652 https://github.com/pharo-project/pharo/pull/17652 # Newtools - Branch: Pharo13, renamed it to presenter and cleaned the class #941 https://github.com/pharo-spec/NewTools/pull/941 - Merge ColorPicker in NewTools #954 https://github.com/pharo-spec/NewTools/pull/954 - Fix Code Rewriter to take care of the context's application #953 https://github.com/pharo-spec/NewTools/pull/953 - Remove method with equivalent in traits #952 https://github.com/pharo-spec/NewTools/pull/952 - Integrate Welcome Browser into NewTools by jecisc Â· Pull Request #951 Â· pharo-spec/NewTools https://github.com/pharo-spec/NewTools/pull/951 - Branch: Making Playground Memorizing its Size #949 https://github.com/pharo-spec/NewTools/pull/949 - Branch: FixingLastInitialExtentForWindow #948 https://github.com/pharo-spec/NewTools/pull/948 - Branch: 946-StFinder-produces-DNU-on-browse, Fixes: #964 #947 https://github.com/pharo-spec/NewTools/pull/947 - Add drag&drop support to inspectors #945 https://github.com/pharo-spec/NewTools/pull/945 # Spec - Allow passwords in SpRequestDialog, Fixes #1705 #1706 https://github.com/pharo-spec/Spec/pull/1706 - fix: make Fuel serialization work with native collections #1704 https://github.com/pharo-spec/Spec/pull/1704 - P13: Introduce metadata and properties support in SpAbstractPresenterâ¦ #1701 https://github.com/pharo-spec/Spec/pull/1701 # Cleanup - Remove dead code #17632 https://github.com/pharo-project/pharo/pull/17632 - Moving ColorPicker extension to the extended class. #17637 https://github.com/pharo-project/pharo/pull/17637 - Remove the refresh because we should not have a dependency from Morphâ¦ #17638 https://github.com/pharo-project/pharo/pull/17638 - Branch: MakingDrTestMemorizingSize. #17649 https://github.com/pharo-project/pharo/pull/17649 - Remove Morphic MCSnapshotBrowser #17659 https://github.com/pharo-project/pharo/pull/17659 - Remove dead code #17658 https://github.com/pharo-project/pharo/pull/17658 - Doing a pass on ProfStef. #17653 https://github.com/pharo-project/pharo/pull/17653 # Website - Update Companies.md: new form links #82 https://github.com/pharo-project/pharo-website/pull/82

Jan. 27, 2025