- Pharo-dev - lists.pharo.org

"Atlas is a Spec application" â New blog post on all: objects all: theTime
by Koen De Hondt May 5, 2024

May 5, 2024

Dear Pharo users and developers, I added the next blog post <https://all-objects-all-the-time.st/#/blog/posts/8> to the series on Atlas, a new browser for Pharo. It describes the relationship between Atlas and Spec, the UI framework of Pharo. The blog post introduces the basic building blocks of the Atlas UI. It also explains the struggle with some aspects of Spec and the Morphic backend. Happy reading! Ciao, Koen

1 0

This week (18/2024) on the Pharo Issue Tracker
by Marcus Denker May 3, 2024

May 3, 2024

With Pharo12 being released, we started to merge more changes in Pharo13. # Pharo12 - Pharo12: ProcessorScheduler>>#activeProcess added no instrumentation pragma #16557 https://github.com/pharo-project/pharo/pull/16557 - Add Toplo world menu entry (part 2) #16478 https://github.com/pharo-project/pharo/pull/16478 # Graphics - Change default value for setting #autoSetCanvasScaleFactor to true #16529 https://github.com/pharo-project/pharo/pull/16529 - missing stroke paint method #16531 https://github.com/pharo-project/pharo/pull/16531 - Change #shrinkTo: on FreeTypeCache to selectively remove entries rather than all of them #16419 https://github.com/pharo-project/pharo/pull/16419 # Bugs - ExteranlAddress>>fromString: converts string to UTF-8 first #16560 https://github.com/pharo-project/pharo/pull/16560 - ProcessorScheduler>>#activeProcess added no instrumentation pragma #16551 https://github.com/pharo-project/pharo/pull/16551 # Refactoring Engine - Refactoring of the RefactoryChange manager #16526 https://github.com/pharo-project/pharo/pull/16526 - Composite extract method refactoring #16525 https://github.com/pharo-project/pharo/pull/16525 # Speed - Announcer: Return early if there isn't any subscriber #16336 https://github.com/pharo-project/pharo/pull/16336 # Cleanup / Misc - New pass at removing SystemAnnouncer references #16518 https://github.com/pharo-project/pharo/pull/16518 - update with latest changes from Pharo12 #16523 https://github.com/pharo-project/pharo/pull/16523 - remove interactionState: #16559 https://github.com/pharo-project/pharo/pull/16559 - the tests use #category: from the package Deprecated12 #743 https://github.com/pharo-spec/NewTools/pull/743 # Tests - add tests for testDoWhileFalse: and testDoWhileTrue: #16532 https://github.com/pharo-project/pharo/pull/16532 - 5 test for rules #16524 https://github.com/pharo-project/pharo/pull/16524

1 0

[Success Story] Support Wizard by Thales
by Marcus Denker April 30, 2024

April 30, 2024

Support Wizard by Thales =================== Support Wizard is an application developped by Pierre Laborde and Eric Le Pors, Global Design and Innovation Leaders at Thales. It is using the latest technological innovations from Pharo to create native and high-performance desktop human-machine interfaces (Bloc graphics engine, Toplo libraries and OS tools). The application is structured with the open-source component architecture framework Molecule. The simplicity and speed of production offered by Pharo and the power of its language allows Thales to focus our efforts on ergonomics and graphic design of the application to offer the best possible user experience. Link (with more infos): https://www.pharo.org/success/Thales-SupportWizard.html Youtube Video: https://www.youtube.com/watch?v=t5qaFM2F3J0

1 0

Re: [Esug-list] [ANN] Pharo 12 released !
by stephane ducasse April 26, 2024

April 26, 2024

Thanks to all the team and contributors for this cool release. S > On 26 Apr 2024, at 12:18, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > Dear Pharo users and dynamic language lovers: > > We have released Pharo <https://pharo.org/> version 12! > > What is Pharo? > > Pharo is a pure object-oriented programming language and a powerful environment focused on simplicity and immediate feedback. > > > > Simple & powerful language: No constructors, no types declaration, no interfaces, no primitive types. Yet a powerful and elegant language with a full syntax fitting in one postcard! Pharo is objects and messages all the way down. > Live, immersive environment: Immediate feedback at any moment of your development: Developing, testing, debugging. Even in production environments, you will never be stuck in compiling and deploying steps again! > Amazing debugging experience: Pharo environment includes a debugger unlike anything you've seen before. It allows you to step through code, restart the execution of methods, create methods on the fly, and much more! > Pharo is yours: Pharo is made by an incredible community, with more than 100 contributors for the last revision of the platform and hundreds of people constantly contributing with frameworks and libraries. > Fully open-source: Pharo full stack is released under MIT <https://opensource.org/licenses/MIT> License and available on GitHub <https://github.com/pharo-project/pharo> > ... more on the Pharo Features page <http://www.pharo.org/features>. > > In this iteration of Pharo, we continue working on our objectives of improvement, clean-up and modularization. Also, we included a number of usability and speed improvements. A complete list of changes and improvements is available in our Changelog <https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo120Chang…> > Some highlights of this amazing version: > > Highlights > > New breakpoint system > > The debug point system is a breakpoint model that supersedes the previous implementation of breakpoints and watchpoints. They are configurable, composable, and extensible. The traditional breakpoints remain available, including conditional breakpoints, one-time breakpoints, and object-centric breakpoints. Additionally, there are new types of breakpoints, such as chained-breakpoints, which condition the activation of certain breakpoints on the triggering of others (e.g., breakpoint B only activates if breakpoint A is hit first). Debug points also feature a dedicated browser and integration options. > > > > Tools > > Scalable fluid class syntax is now the default one > Preparing the introduction of the Bloc graphic system by migrating more tools to Spec2 widgets > Spec2 UI framework enhancements to support GTK 4 > Leaner version of the Metacello package manager > More robust and strict mode for FFI > System > > New architecture for refactorings and domain specific transformations > Code loading speed improvement > Fast browsing via fully optimized package tags > Optmized memory usage via optimized method protocols > Compiler simplifications and improvements > Virtual machine > > Massive image support with permanent space > String/ByteArray comparison speed up > Development Effort > > This new version is the result of 1895 Pull Requests integrated just in the Pharo repository. We have closed 865 issues and received contributions from more than 70 different contributors. We have also a lot of work in the separate projects that are included in each Pharo release: > > http://github.com/pharo-spec/NewTools <https://github.com/pharo-spec/NewTools> > http://github.com/pharo-spec/NewTools-DocumentBrowser <https://github.com/pharo-spec/NewTools-DocumentBrowser> > http://github.com/pharo-spec/Spec <https://github.com/pharo-spec/Spec> > http://github.com/pharo-vcs/Iceberg <https://github.com/pharo-vcs/Iceberg> > http://github.com/ObjectProfile/Roassal3 <https://github.com/ObjectProfile/Roassal3> > http://github.com/pillar-markup/Microdown <https://github.com/pillar-markup/Microdown> > http://github.com/pillar-markup/BeautifulComments <https://github.com/pillar-markup/BeautifulComments> > http://github.com/pharo-project/pharo-vm <https://github.com/pharo-project/pharo-vm> > Contributors > > We always say Pharo is yours. It is yours because we made it for you, but most importantly because it is made by the invaluable contributions of our great community (yourself). A large community of people from all around the world contributed to Pharo 12.0 by making pull requests, reporting bugs, participating in discussion threads, providing feedback, and a lot of helpful tasks in all our community channels. Thank you all for your contributions. > > The Pharo Team > > Discover Pharo: https://pharo.org/features > > Try Pharo: http://pharo.org/download <https://pharo.org/download> > Learn Pharo: http://pharo.org/documentation <https://pharo.org/documentation> > > _______________________________________________ > Esug-list mailing list -- esug-list(a)lists.esug.org > To unsubscribe send an email to esug-list-leave(a)lists.esug.org 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

1 0

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

April 26, 2024

We finally released Pharo 12! Find the announcement here: https://www.pharo.org/news/2024-04-26-pharo12-released.html Last week we merged quite some fixes that where tagged as release critical. And of course some small cleanups. We have opened the Pharo 13 branch, new changes will from now on go there and we back-port important fixes. # Pharo 12 Release fixes - Release waiting processes when destroying a socket (without ThreadedFFI dependency) #16172 https://github.com/pharo-project/pharo/pull/16172 - P12 external projects fix repository versions #16509 https://github.com/pharo-project/pharo/pull/16509 - Adding a Calypso class to display the Debug Points menu group in the method list context menu #16507 https://github.com/pharo-project/pharo/pull/16507 - FFI_i386>>#newCallbackArgumentReaderForCallback:inContext: into "callbacks" like any other #16505 https://github.com/pharo-project/pharo/pull/16505 - Clean System-Announcements-Tests #16503 https://github.com/pharo-project/pharo/pull/16503 - Athens Demo not working #16502 https://github.com/pharo-project/pharo/pull/16502 - Remove some users of SystemAnnoucer class>>#uniqueInstance #16498 https://github.com/pharo-project/pharo/pull/16498 - Remove calypso context from search dialogs #16493 https://github.com/pharo-project/pharo/pull/16493 - Revert "Fix for Wrong focus in Calypso Find Class Dialog causes exception" #16492 https://github.com/pharo-project/pharo/pull/16492 - Changed the description when trying to delete a class. #16491 https://github.com/pharo-project/pharo/pull/16491 - Issue 16462: Find and replace setup is quadruplicated in the context menu #16490 https://github.com/pharo-project/pharo/pull/16490 - Fix 16345: serialization of classes with traits in hierarchy #16487 https://github.com/pharo-project/pharo/pull/16487 - During compilation there are redundant allocation of collections #16486 https://github.com/pharo-project/pharo/pull/16486 - fixes #16362: Abstract instance variables DNU #16482 https://github.com/pharo-project/pharo/pull/16482 - Add setting to set the world renderer canvas scale factor automatically #16479 https://github.com/pharo-project/pharo/pull/16479 - Font-Tests: #testIsAbstractClass should be testIsAbstract like in othâ¦ #16477 https://github.com/pharo-project/pharo/pull/16477 - Added the compare methods to all the byte array classes so they use the new primitiveCompareBytes #16461 https://github.com/pharo-project/pharo/pull/16461 - Fix: rename method loop #16444 https://github.com/pharo-project/pharo/pull/16444 # Pharo 13 - P13 use branch repository #16519 https://github.com/pharo-project/pharo/pull/16519 - add Open as external window option #16511 https://github.com/pharo-project/pharo/pull/16511 - Add rule for Point x: x y: y -> x@y #16508 https://github.com/pharo-project/pharo/pull/16508 - Rename SqueakEpoch to Epoch #16418 https://github.com/pharo-project/pharo/pull/16418

1 0

Re: [Esug-list] [ANN] Pharo 12 released !
by Norbert Hartl April 26, 2024

April 26, 2024

1 0

[P12 nearing realease] dark theme problems (wrt. code snippets)
by Miloslav.Raus＠cuzk.cz April 23, 2024

April 23, 2024

Hi, Currently, if you use dark theme, for example the Welcome or Documentation apps show dark code on dark background. I know it's pretty late, but perhaps an easy fix would be possible (?themed regions for code? or something) ? Cheers, M.R.

2 2

P12 vs P11 difference: Class side trait composition
by Noury Bouraqadi April 23, 2024

April 23, 2024

Hi, Why is the handling of empty trait compositions is different for class side? Suppose we have trait T used by class A. Consider B a subclass of A. B traitComposition ---> TaEmptyTraitComposition "Same for P11 and P12" B class trait "Difference !!!" ---> TaEmptyTraitComposition "in P11" ---> TaSequence {TaEmptyTraitComposition. TraitedClass} "in P12" Noury Noury

2 2

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

Will there be a new PharoLauncher (with [somewhat] current VM) for the 12.0 Release ?
by Miloslav.Raus＠cuzk.cz April 19, 2024

April 19, 2024

Hi. The official launcher (from Downloads page) is dated-a-f. (For example won't repaint when alt-tabbed to, unless some <event>). The latest release from github also wasn't satisfactory (but IDK exactly how). I'm currently using a contemporary image/vm with master PharoLauncher, and the experience seems the best. If at all possible, new official Launcher release (based on P11 or P12) would be welcome. Thanks (but no expectations / pressure), M.R.

2 1