- Pharo-users - lists.pharo.org

This week (16/2024) on the Pharo Issue Tracker
by Marcus Denker April 23, 2024

April 23, 2024

# Bugs - Fix bug while adding a trait to a class without trait #16473 https://github.com/pharo-project/pharo/pull/16473 - Restore fileIn button in File Browser #16470 https://github.com/pharo-project/pharo/pull/16470 - Do not select the # in symbol selection #16469 https://github.com/pharo-project/pharo/pull/16469 - 16447-Dropping-window-outside-of-Pharo-window-borders-closes-the-window #16467 https://github.com/pharo-project/pharo/pull/16467 - 16355-Wrong-class-definition-creates-strange-DNUs #16466 https://github.com/pharo-project/pharo/pull/16466 - Fix: PullUpClassVar was not checking breaking change preconditions #16464 https://github.com/pharo-project/pharo/pull/16464 - fix access to false positive in Renraku #16457 https://github.com/pharo-project/pharo/pull/16457 - Fix #visitBehaviorRepackagedChange: on EpHasImpactVisitor to send #not instead of #y #16449 https://github.com/pharo-project/pharo/pull/16449 - 16365 Add subclass can create trait subclasses #16442 https://github.com/pharo-project/pharo/pull/16442 - Clean package generation of "Jump to test class" #16434 https://github.com/pharo-project/pharo/pull/16434 - Add LibTTY providing access to the VM library for spawning a process connected to a pseudo-terminal #16427 https://github.com/pharo-project/pharo/pull/16427 - fix: Socket>>#waitForSendDoneFor: does not return a boolean (but ZdcSocketStream expects it to) #16425 https://github.com/pharo-project/pharo/pull/16425 - Update the Playground shortcut #16422 https://github.com/pharo-project/pharo/pull/16422 - Fix code highlighting in debug points browser, for debug points set on AST node #726 https://github.com/pharo-spec/NewTools/pull/726 - fix layouts #1539 https://github.com/pharo-spec/Spec/pull/1539 - Adding textChanged notification to SpStringTableColumn #1360 https://github.com/pharo-spec/Spec/pull/1360 # Cleanup - Removing old object-centric breakpoint's integration to the inspector #733 https://github.com/pharo-spec/NewTools/pull/733 - Changed protocol for displayStringOn: to displaying #737 https://github.com/pharo-spec/NewTools/pull/737 - Change superclass of StDebuggerTest from TestCase to SpBaseTest #740 https://github.com/pharo-spec/NewTools/pull/740 - Removing old breakpoint system's integration to Calypso #16397 https://github.com/pharo-project/pharo/pull/16397 - reuse of #isFalsePositive:forRuleId:versionId: in #falsePositiveOf: #16475 https://github.com/pharo-project/pharo/pull/16475

1 0

UKSTUG meeting - Tudor GÃ®rba: What exactly is Glamorous Toolkit? - 24 April 2024
by UK Smalltalk April 22, 2024

April 22, 2024

To some people Glamorous Toolkit is a Pharo environment. To others itâs a knowledge management system. Others might see a code analysis platform, a data visualization or an API browsing tool. Yet others see the graphical stack with its interactive editors. Glamorous Toolkit is all of these. But itâs really also none of these. These are merely examples of the many forms the environment can be molded to. And there can be many more. Glamorous Toolkit is primarily an environment that makes it possible to create many experiences seamlessly and contextually. This then leads to a new way of programming that we call Moldable Development. Tudor GÃ®rba is a software environmentalist and the CEO of feenk.com ( http://feenk.com/ ) where he works with an amazing team to make the inside of systems explainable. Much of the work is embodied in Glamorous Toolkit ( gtoolkit.com) a novel environment that enables moldable development. 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/300575234/ ) to receive the meeting details. Donât forget to bring your laptop and drinks!

1 0

How to log pharo output to stdio safely?
by Tim Mackinnon April 20, 2024

April 20, 2024

Hi - I've been messing around with deploying a hobby pharo app to the web.. which has become a lot simpler over the years, although the tech keeps changing and you have to relearn things. Anyway, I have my image in one of the wonderful BA Docker containers, and it runs well - and the host I'm using will show the logs for you, so you can figure out what is going on... well that is if your logs come out properly (and of course, if it gets really hairy then you can get a VNC session onto the image and figure stuff out) So logs are handy, and pharo these days has a nice headless mode that redirects the Transcript to stdout - and there are also a few decent logging frameworks as well. But as most things go to the Transcript, and that goes to stdout - it should be good. HOWEVER - flushing is the killer, as if things happen and the last thing goes wrong, but the output isn't flushed, then you aren't going to see it. So my question is how to properly flush? And I'm sure I've read something about this before, but I can't find it. >From memory, you often need to have a Transcript cr. to flush your last line. BUT, most things in the image seem to use "self crTrace:" these days, which is a cr to ensure the previous msg is separated from what you want to write, and then you write your line out. However, as there is now cr - you might not see it. So I tried changing my stuff to use "self traceCr:" (which is in the image), and that still didn't seem to work - the last failing line wasn't being output. Worse still, its confusing, as many things in the image are using crTrace: and so you get intermingled messages, which are hard to decipher. So I tried: Transcript cr; show: msg; flush But that didn't seem to work (which I don't understand) Eventually I did: Transcript show: msg; cr; flush And this seems to ensure things do reliably get outputted - but I'm wondering if anyone can shed light on this areas? Ideally I want to use: Transcript cr'; show: msg; flush As this plays much better with everything that is in the image - but is there some way to do this? And indeed, will log tools the Bettersatack or papertail play ball with output like this (as I guess they operate on complete lines to interpret log levels etc), Anyway - I'm curious if anyone else has done work in this area to shed light? Thanks, Tim As an aside - for deployment - several years ago I came across dockerize.io - which lets you upload a Docker image to a host, and it will run it for you. Sadly that service didn't survive... but there are quite a few like it now, and so I'm trying Render.com - which is similar, but the twist is you need to store a Docker image in a registry somewhere (I use gitlab from my CI pipeline), and then it will retrieve it and run it for you (for either free in 40 minute chunks, or for $7/m - which is pretty good, and possibly bit simpler than Digital Ocean). Its pretty cool, and maybe I will write up about it sometime

6 6

[ANN] docker-pharo-runtime v11.0.0-2024-04-18 [v11.0.0 [2024-04-18]] released!
by Buenos Aires Smalltalk April 18, 2024

April 18, 2024

1 0

[ANN] docker-pharo-vm v10.1.0-2024-04-18 [v10.1.0 [2024-04-18]] released!
by Buenos Aires Smalltalk April 18, 2024

April 18, 2024

1 0

remove breakpoint ?
by Haroldo Stenger April 14, 2024

April 14, 2024

hi nice pharo people I'm doing my very initial attempts in Pharo. Having read something here and there. Now I've put myself to subclass BlElement in order to add a method of myself to this subclass. The subclass got named 'Circulo'. Then I had a hard time trying to create a protocol to 'host' it, but finally it got created as protocol 'a'. Initially it got created in the third pane in the browser, below without any apparent 'breakpoint hierarchy'. However, as soon as I wrote the method and got to save/accept it, something strange happened, namely, 'brakepoint' protocol was created out of nothing , and my 'a' protocol was put under it. The method itself in the fourth pane, has a red ! sign. If I right click on the method, and try to remove the breakpoint, it does nothing. What happens this and how can I have a normal situation , since I did not put breakpoints ? Thanks for your kind help

2 3

This week (15/2024) on the Pharo Issue Tracker
by Marcus Denker April 12, 2024

April 12, 2024

# Speed - 16407-RBNodes-errorNotices-creates-unneeded-empty-collections #16408 https://github.com/pharo-project/pharo/pull/16408 # Bug Fixes - Fix Preview Settings Browser: does not open when a custom setting is used #734 https://github.com/pharo-spec/NewTools/pull/734 - Remove async playground doits #735 https://github.com/pharo-spec/NewTools/pull/735 - Fix issue while trying to display file setting items #736 https://github.com/pharo-spec/NewTools/pull/736 - quick fix that hide the debug context menus when there are unsaved changes #16382 https://github.com/pharo-project/pharo/pull/16382 - Fix Generate Equals and Hash DNU #16384 https://github.com/pharo-project/pharo/pull/16384 - Fix for Wrong focus in Calypso Find Class Dialog causes exception #16386 https://github.com/pharo-project/pharo/pull/16386 - Provide a default String for settings without #default: sends. #16400 https://github.com/pharo-project/pharo/pull/16400 - fix MethodConstantTest #16405 https://github.com/pharo-project/pharo/pull/16405 - fix enum type initialization on structures #16406 https://github.com/pharo-project/pharo/pull/16406 - Do not suggest trait when deprecating a class #16409 https://github.com/pharo-project/pharo/pull/16409 - 16366 Insert superclass refactoring is allowed on trait and gives DNU #16413 https://github.com/pharo-project/pharo/pull/16413 - 16423-Scrolling-always-acts-as-if-macOS-option-Use-inertia-when-scrolling-is-turned-off #16426 https://github.com/pharo-project/pharo/pull/16426 - Fix Refactorings should have help menus to explain their actions #16421 https://github.com/pharo-project/pharo/pull/16421 - Reposition Calypso contextual class menu items #16420 https://github.com/pharo-project/pharo/pull/16420 # Improvements - Add support for Epicea file out #16401 https://github.com/pharo-project/pharo/pull/16401 - Add Toplo world menu entry #16429 https://github.com/pharo-project/pharo/pull/16429 # UI - Exclude some commands from virtual method groups on Calypso #16404 https://github.com/pharo-project/pharo/pull/16404 - fix enter/escape behavior on dialogs #1537 https://github.com/pharo-spec/Spec/pull/1537 - Improving the behavior in all the dialogs #1536 https://github.com/pharo-spec/Spec/pull/1536 - Fix selection bug in SpFilteringSelectableListPresenter #1535 https://github.com/pharo-spec/Spec/pull/1535 - fix: SpSelectDialog should select the first item #1530 #1534 https://github.com/pharo-spec/Spec/pull/1534 - Improve SpSelectDialog for handling line splitting texts #1533 https://github.com/pharo-spec/Spec/pull/1533 - Cleanup/remove rename default spec to default layout refactoring #1515 https://github.com/pharo-spec/Spec/pull/1515 # Cleanups - moved to Spec2-Transmission package #1538 https://github.com/pharo-spec/Spec/pull/1538 - Use #setUp instead of #initialize for test cases #16417 https://github.com/pharo-project/pharo/pull/16417 - Remove CharacterTable #16416 https://github.com/pharo-project/pharo/pull/16416

1 0

Early rate deadline is approaching....
by stephane ducasse April 9, 2024

April 9, 2024

Hello People do not miss this unique opportunity to participate in ESUG in early July https://esug.org Pay attention that the early rate end is approachingâ¦ 15 of April 2024. https://registration.esug.org/ESUG 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

3 2

This week (14/2024) on the Pharo Issue Tracker
by Marcus Denker April 5, 2024

April 5, 2024

# Fixes - Provide a default String for settings without #default: sends. #16400 https://github.com/pharo-project/pharo/pull/16400 - 16356-Rename-class-refactoring-popup-does-not-have-default-button #16392 https://github.com/pharo-project/pharo/pull/16392 - Small fixes pre release #16381 https://github.com/pharo-project/pharo/pull/16381 - Revert comment change from commit f5df5966bd73d05bc04806d2f8735baa4b1783cb #16376 https://github.com/pharo-project/pharo/pull/16376 - Fix function signature in #getVolumeInfo:into:size: for StWin32Info #730 https://github.com/pharo-spec/NewTools/pull/730 - Adapt #getVolumeInfo:into:size: for StWin32Info to strict FFI #729 https://github.com/pharo-spec/NewTools/pull/729 - Change #getTempPath:buffer: on WinPlatform to use âGetTempPathWâ instead of âGetTempPath2Wâ #16342 https://github.com/pharo-project/pharo/pull/16342 - latest changes #1532 https://github.com/pharo-spec/Spec/pull/1532 # UI/Tools Fixes - improve/spRequiestDialog-issue-16356 #1531 https://github.com/pharo-spec/Spec/pull/1531 - Remove Monticello shortcut references #16388 https://github.com/pharo-project/pharo/pull/16388 - remaining morphic dialogs: aligning the default option to right #16352 https://github.com/pharo-project/pharo/pull/16352 - 16363-Improve-Expand-menu-for-class-definition #16371 https://github.com/pharo-project/pharo/pull/16371 - New tools parent menu entry #16379 https://github.com/pharo-project/pharo/pull/16379 - Open Calpyso with 915px wide such that the entire toolbar is visible #16380 https://github.com/pharo-project/pharo/pull/16380 - Make #cascadeFor:initialExtent:world: for RealEstateAgent use integral positions when using the worldâs center #16390 https://github.com/pharo-project/pharo/pull/16390 - Fix issue while trying to display file setting items #736 https://github.com/pharo-spec/NewTools/pull/736 - Remove async playground doits #735 https://github.com/pharo-spec/NewTools/pull/735 - Fix Preview Settings Browser: does not open when a custom setting is used #734 https://github.com/pharo-spec/NewTools/pull/734 - Fix "Open terminal here" in new File browser #732 https://github.com/pharo-spec/NewTools/pull/732 - Add 3 new entries to easily access the new tools from the System menu. #731 https://github.com/pharo-spec/NewTools/pull/731 # Cleanups - Deprecate #newMethod:header: with rewritting to #basicNew:header: #16375 https://github.com/pharo-project/pharo/pull/16375 - Remove StWindowsExtensionsTest #728 https://github.com/pharo-spec/NewTools/pull/728 - Remove old backward compatibility code from FFILibrary #16349 https://github.com/pharo-project/pharo/pull/16349

1 0

Call for Presentations @ ESUG 2024
by stephane ducasse April 4, 2024

April 4, 2024

Dear Friends The deadline for the presentation proposal was 1st of April. We extended it until 8th of April. You are probably busy but we the organisers deserve consideration too. ESUG 2024 Call for Presentations from 8 to 11 July 2024 Lille France https://esug.github.io <https://esug.github.io/> https://esug.github.io/2024-Conference/conf2024.html 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/ - Submit a talk, software to the award competition, or a paper to IWST http://https://esug.github.io/2024-Conference/IWST2024.html - Attend the conference. We'd like to beat the previous record of attendance (180 people at Koln 2019)! - Students can get free registration and hosting if they enroll in 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 We added two types of sessions in addition to the regular talks and ''Show us your project'' sessions. - Show your business in a 10-minute session (Get prepared!!) - Teaching pearls: we want some sessions 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-minute sessions aggregated. ### How to submit? Make a Pull Request here https://github.com/ESUG/esug.github.io/tree/source/2024-Conference/talks [Or but only if you are not connected to the worldâ¦ send an email to stephane.ducasse(a)inria.fr <mailto:stephane.ducasse@inria.fr>] Title: [ESUG 2024] Please follow the template below the email will be automatically processed! Name: Email: Abstract: Bio:

1 0