March 2024 - Pharo-dev - lists.pharo.org

Re: "Introducing Atlas" â New blog post on all: objects all: theTime

by Noury Bouraqadi

I read the blog post and I liked it. Thank you Koen! I've also liked very much the discussion in this thread. I hope that you guys would expand your ideas and give talks at the ESUG conference next July. FYI here is the page with the ESUG call for presentations https://esug.github.io/2024-Conference/call2024.html Noury ;-) On Mar 11 2024, at 4:27 pm, Aik-Siong Koh <askoh(a)askoh.com> wrote: > Atlas is indeed ambitious, and I am glad you want to push the boundaries. > > Over the decades, GUIs have introduced a bewildering array of widgets and designs that I think we are in a mess again. > I feel we should restart again with a blank window, allow select and rightclick for context menu, and proceed for there to introduce the base minimum for a functional GUI. > I believe "select and rightclick context menu" can solve almost every GUI need simply. > I also think the single column menu can be updated to a two-column menu which is more compact and balanced. > The cursor can be centered between the two columns instead of being at the top left corner. > The cursor has to travel less for any selection. > https://askoh.com/index.html#TwoColumnMenu > > All the best, > Aik-Siong Koh > > On Mon, 11 Mar 2024 09:58:40 +0000, "Tim Mackinnon" <tim(a)testit.works> wrote: > > As browsers are a passion in the Smalltalk world it will be great to read your thoughts - as its certainly a hot potato, and we don't seem to have quite cracked it so far. > > I recall the presentations on Calypso from Pharo days (might have been recorded for review if you haven't seen them). I recall being won over at the time (and I was hesitant) - there was lots of flexibility that had been thought about, and many useful and tricky browsing patterns were covered - but over time I think its proved tricky to work with. In Pharo 11, the browsers don't seem to work as well as they should (lots of funny focus issues and loss of context that I don't recall in previous version - which I think is more down to understanding how it was supposed to work than technical flaws). > > It's definitely worth generating conversation and getting some consensus otherwise it will be a rise and fall scenario all over again. This said, continuing to find a good model that is both flexible and simple is useful. > > Tim > > p.s. On thing I recall from those Calypso presentations was that the model should have let us design browsers where we have different navigation models (e.g. you in theory you could design something where a class has a path to methods which are both instance and class so you don't have to have a mode to swap between them - something I find distracting when designing the interface of a class and trying to figure out how you instantiate/initialize it and you want to jump between the 2 view - I just want to see all all the methods in a list, differentiated in some way vs. hiding them). > > On Sun, 10 Mar 2024, at 5:24 PM, Koen De Hondt wrote: > > Dear Pharo users and developers, > > > > Some people already know that I am working on a browser for Pharo. With this announcement, I make it official ð. > > In my latest blog post (https://all-objects-all-the-time.st/#/blog/posts/6) I introduce Atlas as an ambitious successor of Calypso. It is the first post in a series. > > > > Happy reading! > > > > Ciao, > > Koen > > > > > >

March 13, 2024

ESUG24 Call for Student Volunteers, 8-11 July, Lille, France

by Steven Costiou

CALL FOR STUDENT VOLUNTEERS, ESUG 2024, 8-11 JULY, LILLE, FRANCE Student volunteers help 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 volunteers-esug24(a)inria.fr. * title: [ESUG 2024 Student] * name, gender, university/school, country, email address * short description of you and why you are interested in participating Accommodation is covered from Sunday 7 July until 8 Thursday July 2024 (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. Travel costs are *not* covered by the student volunteers program. 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.

March 12, 2024

[ANN] Pharo 12 development is now frozen

by Esteban Lorenzano

Hi, As we announced a couple of weeks ago, Pharo 12 development entered its freeze status. This means no more new features will be included, we will concentrate until release just in important bugfixes. If you have an issue that you consider a showstopper for your workflow/needs, let us now and we will consider it. Cheers! Esteban

March 12, 2024

Re: "Introducing Atlas" â New blog post on all: objects all: theTime

by Aik-Siong Koh

Atlas is indeed ambitious, and I am glad you want to push the boundaries. Over the decades, GUIs have introduced a bewildering array of widgets and designs that I think we are in a mess again. I feel we should restart again with a blank window, allow select and rightclick for context menu, and proceed for there to introduce the base minimum for a functional GUI. I believe "select and rightclick context menu" can solve almost every GUI need simply. I also think the single column menu can be updated to a two-column menu which is more compact and balanced. The cursor can be centered between the two columns instead of being at the top left corner. The cursor has to travel less for any selection. https://askoh.com/index.html#TwoColumnMenu All the best, Aik-Siong Koh On Mon, 11 Mar 2024 09:58:40 +0000, "Tim Mackinnon" <tim(a)testit.works> wrote: Â As browsers are a passion in the Smalltalk world it will be great to read your thoughts - as its certainly a hot potato, and we don't seem to have quite cracked it so far. Â I recall the presentations on Calypso from Pharo days (might have been recorded for review if you haven't seen them). I recall being won over at the time (and I was hesitant) Â - there was lots of flexibility that had been thought about, and many useful and tricky browsing patterns were covered - but over time I think its proved tricky to work with. In Pharo 11, the browsers don't seem to work as well as they should (lots of funny focus issues and loss of context that I don't recall in previous version - which I think is more down to understanding how it was supposed to work than technical flaws). Â It's definitely worth generating conversation and getting some consensus otherwise it will be a rise and fall scenario all over again. This said, continuing to find a good model that is both flexible and simple is useful. Â Tim Â p.s. On thing I recall from those Calypso presentations was that the model should have let us design browsers where weÂ have different navigation models Â (e.g. you in theory you could design something where a class has a path to methods which are both instance and class so you don't have to have a mode to swap between them - something I find distracting when designing the interface of a class and trying to figure out how you instantiate/initialize it and you want to jump between the 2 view - I just want to see all all the methods in a list, differentiated in some way vs. hiding them). Â On Sun, 10 Mar 2024, at 5:24 PM, Koen De Hondt wrote: Dear Pharo users and developers, Â Some people already know that I am working on a browser for Pharo. With this announcement, I make it official ð. InÂ my latest blog post, I introduce Atlas as an ambitious successor of Calypso. It is the first post in a series. Â Happy reading! Â Ciao, Koen Â

March 11, 2024

Re: "Introducing Atlas" â New blog post on all: objects all: theTime

by Tim Mackinnon

As browsers are a passion in the Smalltalk world it will be great to read your thoughts - as its certainly a hot potato, and we don't seem to have quite cracked it so far. I recall the presentations on Calypso from Pharo days (might have been recorded for review if you haven't seen them). I recall being won over at the time (and I was hesitant) - there was lots of flexibility that had been thought about, and many useful and tricky browsing patterns were covered - but over time I think its proved tricky to work with. In Pharo 11, the browsers don't seem to work as well as they should (lots of funny focus issues and loss of context that I don't recall in previous version - which I think is more down to understanding how it was supposed to work than technical flaws). It's definitely worth generating conversation and getting some consensus otherwise it will be a rise and fall scenario all over again. This said, continuing to find a good model that is both flexible and simple is useful. Tim p.s. On thing I recall from those Calypso presentations was that the model should have let us design browsers where we have different navigation models (e.g. you in theory you could design something where a class has a path to methods which are both instance and class so you don't have to have a mode to swap between them - something I find distracting when designing the interface of a class and trying to figure out how you instantiate/initialize it and you want to jump between the 2 view - I just want to see all all the methods in a list, differentiated in some way vs. hiding them). On Sun, 10 Mar 2024, at 5:24 PM, Koen De Hondt wrote: > Dear Pharo users and developers, > > Some people already know that I am working on a browser for Pharo. With this announcement, I make it official ð. > In my latest blog post <https://all-objects-all-the-time.st/#/blog/posts/6>, I introduce Atlas as an ambitious successor of Calypso. It is the first post in a series. > > Happy reading! > > Ciao, > Koen

March 11, 2024

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

by Marcus Denker

# Pharo 10 - Fix for: UFFI/TFFI call for WebBrowser with specific URL length adds strange characters to the URL #15980 #16253 https://github.com/pharo-project/pharo/pull/16253 # Pharo 11 - Fix for: UFFI/TFFI call for WebBrowser with specific URL length adds strange characters to the URL #15980 #16284 https://github.com/pharo-project/pharo/pull/16284 # Fixes - do not spam selectPage: #1528 https://github.com/pharo-spec/Spec/pull/1528 - Restore original message String #16274 https://github.com/pharo-project/pharo/pull/16274 - Fix Method name editor dialog up/down buttons #16273 https://github.com/pharo-project/pharo/pull/16273 - Fix Bug: OrderedDictionary>>#at:at:put: not updating ordered keys #16260 https://github.com/pharo-project/pharo/pull/16260 - Minor improvement in TF test class #16257 https://github.com/pharo-project/pharo/pull/16257 - Fix #magnifyBy:smoothing: on OSSDL2ExternalForm #16225 https://github.com/pharo-project/pharo/pull/16225 - fix a failing test #714 https://github.com/pharo-spec/NewTools/pull/714 # Improvements - Make #reportTestCase:runBlock: on HDTestReport print the test run time on the progress log stream #16266 https://github.com/pharo-project/pharo/pull/16266 # Refactoring Engine - Fix: rename method shortcut #16251 https://github.com/pharo-project/pharo/pull/16251 - Remove unused instance variable in #ReRenameMethodRefactoring #16279 https://github.com/pharo-project/pharo/pull/16279 - Fix: rename method preconditions fail with DNU #16270 https://github.com/pharo-project/pharo/pull/16270 - Test: rename method driver #16269 https://github.com/pharo-project/pharo/pull/16269 - Cleanup: rename method refactoring driver to new architecture with breaking choices #16258 https://github.com/pharo-project/pharo/pull/16258 # Cleanups - Refactor various âworldMenuâ registration methods to use #iconName: instead of #icon: #711 https://github.com/pharo-spec/NewTools/pull/711 - Updated baseline of Dependency analyzer #16278 https://github.com/pharo-project/pharo/pull/16278 - 16246-CI-Failing-test-SystemDependenciesTesttestExternalIDEDependencies #16264 https://github.com/pharo-project/pharo/pull/16264

March 11, 2024

"Introducing Atlas" â New blog post on all: objects all: theTime

by Koen De Hondt

Dear Pharo users and developers, Some people already know that I am working on a browser for Pharo. With this announcement, I make it official ð. In my latest blog post <https://all-objects-all-the-time.st/#/blog/posts/6>, I introduce Atlas as an ambitious successor of Calypso. It is the first post in a series. Happy reading! Ciao, Koen

March 10, 2024

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

by Marcus Denker

# Features - integrating Debug Points model into Pharo #16177 https://github.com/pharo-project/pharo/pull/16177 # Fixes - add back isGlobalClassNameBinding #16035 https://github.com/pharo-project/pharo/pull/16035 - FFIUnsupportedUntypedLiteral when using WebBrowser classes on Windows #16262 https://github.com/pharo-project/pharo/pull/16262 - Fix adding slots in Ring #16247 https://github.com/pharo-project/pharo/pull/16247 - use the correct integration branch for iceberg and Pharo #16244 https://github.com/pharo-project/pharo/pull/16244 - fixing reflectivity bug that executes a #before metalink twice if an #after metalink is installed #16236 https://github.com/pharo-project/pharo/pull/16236 - MCWorkingCopy class>>#infoFromDictionary:cache: sends a deprecated method #16231 https://github.com/pharo-project/pharo/pull/16231 - 16204-RubPluggableTextFieldMorph-does-not-open-drop-list #16205 https://github.com/pharo-project/pharo/pull/16205 - Bug fix: Context menu item âRevert to selected versionâ in recent versions of a method does not revert #710 https://github.com/pharo-spec/NewTools/pull/710 - ExpressionFinder - matches browser now knows the method that is showing #709 https://github.com/pharo-spec/NewTools/pull/709 # Graphics / Rendering / UI - Make EpEntryItem use FormSet for the icons #16240 https://github.com/pharo-project/pharo/pull/16240 - Fix #freshLogFromSelection: on EpUnifiedBrowserPresenter to map trigger references #16239 https://github.com/pharo-project/pharo/pull/16239 - Refactor various âworldMenuâ registration methods to use #iconName: instead of #icon: #16237 https://github.com/pharo-project/pharo/pull/16237 # Refactoring Engine - Fix: use new API for getting the package name in CopyClassRegexRefactoring #16256 https://github.com/pharo-project/pharo/pull/16256 - Fix: multiple exceptions when executing a rb move class transformation #16250 https://github.com/pharo-project/pharo/pull/16250 - Fix: #16209: [RB] Insert superclass refactoring breaks class side hierarchy #16234 https://github.com/pharo-project/pharo/pull/16234 # Cleanup - Removed CursorWithAlpha as is not used #16229 https://github.com/pharo-project/pharo/pull/16229 - [Cleanup] #notNil to #isNotNil in Spec #1527 https://github.com/pharo-spec/Spec/pull/1527 # Documentation - In TerseGuide fix documentation #16228 https://github.com/pharo-project/pharo/pull/16228

March 1, 2024