- Pharo-dev - lists.pharo.org

This week (51/2023) on the Pharo Issue Tracker
by Marcus Denker Jan. 23, 2024

Jan. 23, 2024

A little bit late... # Features - Implements hierarchical senders system command #15822 https://github.com/pharo-project/pharo/pull/15822 - Shuffle tests #15581 https://github.com/pharo-project/pharo/pull/15581 # Fixes - 15801-Cmd-B-on-Transcript-raises-an-error #15802 https://github.com/pharo-project/pharo/pull/15802 - 15798-Compiler-error-when-iteration-step-is-nil #15803 https://github.com/pharo-project/pharo/pull/15803 - Fix for Calypso discard code with error and prevent to fix it #15834 https://github.com/pharo-project/pharo/pull/15834 - Make TraitedClass part of the trait composition of TraitedMetaclasses #15833 https://github.com/pharo-project/pharo/pull/15833 - Display trait icon in Calypso class definition editor #15828 https://github.com/pharo-project/pharo/pull/15828 - fix some button orders #15820 https://github.com/pharo-project/pharo/pull/15820 - Prevent logging exceptions twice when debugger is opened #15746 https://github.com/pharo-project/pharo/pull/15746 # Variables - Undeclared: inlining of declare:from: #15827 https://github.com/pharo-project/pharo/pull/15827 - UndeclaredVariable read/write: context as argument #15821 https://github.com/pharo-project/pharo/pull/15821 - #usingClasses for the Slot Hierachy #15815 https://github.com/pharo-project/pharo/pull/15815 # Refactoring Engine - Position temp definition before first occurrence of extracted expression, and always in outer scope (fixes #14611) #15781 https://github.com/pharo-project/pharo/pull/15781 - Fix rename refactoring call to support class methods. #15816 https://github.com/pharo-project/pharo/pull/15816 - Enh/refactoring pass over rename driver and tests #15808 https://github.com/pharo-project/pharo/pull/15808 # Tests - Shuffle tests #15581 https://github.com/pharo-project/pharo/pull/15581 - New source code command for running current test #15832 https://github.com/pharo-project/pharo/pull/15832 - Fix shuffle seed printing #15831 https://github.com/pharo-project/pharo/pull/15831 # Cleanup - Unify packaging of Announcement>>#affects* #15734 https://github.com/pharo-project/pharo/pull/15734 - Remove ChangeSet #15794 https://github.com/pharo-project/pharo/pull/15794 - (Re)Moved ProfilerUI package #15797 https://github.com/pharo-project/pharo/pull/15797 - Fix a few reflection: pragmas #15812 https://github.com/pharo-project/pharo/pull/15812 - fix a method that has a wrong category #15814 https://github.com/pharo-project/pharo/pull/15814 - Cleanup notNil to isNotNil in AST-CORE #15840 https://github.com/pharo-project/pharo/pull/15840

1 0

[ANN] New Success Story posted
by Marcus Denker Jan. 21, 2024

Jan. 21, 2024

There is a new âSuccess Storyâ posted on pharo.org <http://pharo.org/>: Casino - Revolutionizing Application Migration for Berger-Levrault https://www.pharo.org/success/BergerLevrault-Casino.html If you have an idea for something like that, you can do PRs for the site here: https://github.com/pharo-project/pharo-website

3 3

This week (03/2024) on the Pharo Issue Tracker
by Marcus Denker Jan. 19, 2024

Jan. 19, 2024

After a holiday break, we resume the weekly issue tracker report # Pharo 11 - Extend FFIExternalStructureReferenceHandle with tfPointerAddress #15951 https://github.com/pharo-project/pharo/pull/15951 # Bugs - Fix bug in integer vs float comparisons #15973 https://github.com/pharo-project/pharo/pull/15973 - adding back millisecondsToRun: but we will deprecate it. #15969 https://github.com/pharo-project/pharo/pull/15969 # Refactoring Engine - Fix: instance and shared variables driver bugs #15983 https://github.com/pharo-project/pharo/pull/15983 - Fix: cannot move method to class side #15981 https://github.com/pharo-project/pharo/pull/15981 - Adding documentation on the rewrite rules #15966 https://github.com/pharo-project/pharo/pull/15966 - Make insert superclass and subclass working again #15957 https://github.com/pharo-project/pharo/pull/15957 - Add rb to any rb entity printString! Green tests #15959 https://github.com/pharo-project/pharo/pull/15959 - Refactor: pass on refactoring preconditions #15954 https://github.com/pharo-project/pharo/pull/15954 # Metacello Cleanup - Clean(Gofer, Metacello): remove junk and old/unused repositories. #15968 https://github.com/pharo-project/pharo/pull/15968 # Rules / Code Critic - Improve ReMultiplePeriodsTerminatingStatementRule #15956 https://github.com/pharo-project/pharo/pull/15956 - Add release test for ReDoNotSendSuperInitializeInClassSideRule #15972 https://github.com/pharo-project/pharo/pull/15972

1 0

ESUG 2024 book the dates
by stephane ducasse Jan. 15, 2024

Jan. 15, 2024

Hello The ESUG board decided the dates and location of the next ESUG conference ESUG 2024 will be at Lille from 8th to 11th July 2024. Notice that this year the conference will be on 4 days. The early rate registration will be 15 of April 2024. The IWST workshop will be chaired by G. Rakic and S. Ducasse. To help us organizing the conference we will ask authors to register to the conference when submitting their article. In the really rare case an article would not be accepted, ESUG will fully reimburse you without any cost. We will update the website. Stef -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr / http://www.pharo.org 03 59 35 87 52 Assistant: Aurore Dalle FAX 03 59 57 78 50 TEL 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza Villeneuve d'Ascq 59650 France

1 0

[ANN] Pharo Consortium New Bronze Member: ApptiveGrid
by Marcus Denker Jan. 8, 2024

Jan. 8, 2024

The Pharo Consortium is very happy to announce that ApptiveGrid GmbH has joined the Consortium as a Bronze Member. About - ApptiveGrid: https://www.apptivegrid.de - Pharo Consortium: http://consortium.pharo.org ApptiveGrid is a SaaS tool to digitalize and automatize business processes. ApptiveGrid is a visual database that lets you effortlessly create and modify your data models through a web frontend, seamlessly integrates with REST API for external access, and features a dynamic form creator for easy data collection. It's also a powerful workflow system, where you can design and automate your processes, responding to both internal changes and external triggers through web hooks. The backend of ApptiveGrid is 100% Pharo: It uses [zinc](https://github.com/svenvc/zinc) components for the HTTP frontend and [soil](https://github.com/ApptiveGrid/Soil) as the persistence solution. The goal of the Pharo Consortium is to allow companies and institutions to support the ongoing development and future of Pharo. Individuals can support Pharo via the Pharo Association https://association.pharo.org

1 0

Call for chapters
by stephane ducasse Jan. 6, 2024

Jan. 6, 2024

Welcome to this collaborative book. We are looking for contributions to new tools in the Pharo ecosystem. Here is a non-exhaustive list of possible tools we have in mind. Development tools such as refactoring, memory usage, and new approaches to debugging Development tools such as UI builders Development tools to develop compilers Tools for modeling such as Cormas, Moose Libraries as basis for advanced tools Each chapter will be reviewed by three reviewers. We expect the chapters to describe the tools, present some clear scenarios, describe key elements of implementations, evidence of use of the tools, Submission process: A chapter must be written in Microdown. Writers may want to clone the current repository and use Pillar (see https://github.com/pillar-markup/pillar and https://github.com/pillar-markup/microdown) The Sample1 folder in the Chapters folder contains a sample chapter. The authors should send an email to stephane.ducasse(a)inria.fr <mailto:stephane.ducasse@inria.fr>, goca(a)dmi.uns.ac.rs <mailto:goca@dmi.uns.ac.rs>, and juanpablo.sandoval(a)uc.cl <mailto:juanpablo.sandoval@uc.cl>. The authors should then do a PR to this repository with their chapter containing all their files. The length of each chapter is not fixed but authors should make sure that the chapter is not either too short or too long. It is worth to see that the format is good for tutorials but is not compact. We will give feedback on this aspect. As usual the material should be new and unpublished. Citations should be expressed using the microdown citation e.g. {!citation|ref=Blac09a!} using {!citation|ref=Blac09a!}, A chapter must be spellchecked with a system such as grammarly, if needed, each chapter should contain a bibfile having the same name than the main folder file, if needed each chapter should contain a folder named 'figures' that contains the figures of the chapter. The Sample1 folder illustrates this structure, it contains: Sample1.bib Sample1.md figures/pharo.png figures/rmod.png This book will be published via the book-on-demand program of http://bod.fr <http://bod.fr/>. It will be published on the Bibliotheque Nationale de France and it will be available on most public platforms such as amazon.com. S. Ducasse, G. Rakic and J-P Sandoval -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr / http://www.pharo.org 03 59 35 87 52 Assistant: Aurore Dalle FAX 03 59 57 78 50 TEL 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza Villeneuve d'Ascq 59650 France

1 0

[ANN] success story: ApptiveGrid
by Norbert Hartl Dec. 30, 2023

Dec. 30, 2023

I wanted to write this for a very long time nowâ¦so finallyâ¦Iâm very proud to announce a new success story: ApptiveGrid ApptiveGrid is a SaaS tool to digitalize and automatize business processes. On the one hand ApptiveGrid is visual database that enables you to model your database via web frontend. At the same time this model is available via REST API. On top of the data model a form creator turns your model into a form that you can send e.g. via email to inquire data from other peopleâ¦ On the other hand ApptiveGrid is a workflow system where you can define your work flow in the web frontend and connect to events. These events are either internal (resulting from a change in your data model) or external where you can use web hooks to kick of work flows. With the combination of both parts ApptiveGrid is able to solve many of modern digital workflows. It enables to make it for low cost and in almost no time which are two pretty good reasons to use it. If you want to use it just visit: http://www.apptivegrid.de. ApptiveGrid provides a start plan at no cost where most of the functionalities are available. If you have additional needs just write me. For the people in the pharo community Iâm sure we can provide a bit more on top. About the tech stack: - The business backend of ApptiveGrid is 100% pharo - It uses https://github.com/svenvc/zinc components for the HTTP frontend - and https://github.com/ApptiveGrid/Soil as the persistence solution. - Each user has its own database (an empty soil database is 24kb on disk, could be made even approx. 5kb). There are over 3100 databases in the system right now - one pharo image holds multiple soil databases open and provides memory caching for the objects - routing of requests is done with haproxy connection persistence - the web frontend is made with Vue.js and a pharo library that we transpile to JS with PharoJS If you are interested you can also watch my ESUG videos at https://www.youtube.com/@esugboard. All talks in the last 2 years were about ApptiveGrid If you have question, donât hesitate to ask, Iâm happy to answer! Norbert

6 6

PhD on Pharo completion with machine learning
by stephane ducasse Dec. 22, 2023

Dec. 22, 2023

Code completion for large projects and small languages https://recrutement.inria.fr/public/classic/fr/offres/2023-07003 S -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr / http://www.pharo.org 03 59 35 87 52 Assistant: Aurore Dalle FAX 03 59 57 78 50 TEL 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza Villeneuve d'Ascq 59650 France

1 0

About Undeclared
by Marcus Denker Dec. 22, 2023

Dec. 22, 2023

Hi, You might have seen that we have done some work related to Undeclared. I did some slides to explain how it worked / how it works now / what remaining problems are / next step.

2 1

This week (50/2023) on the Pharo Issue Tracker
by Marcus Denker Dec. 18, 2023

Dec. 18, 2023

# Pharo 11 - 15769-Backport-15767--Pharo11-Fix-hasSameDefinitionAs-for-IndexedSlot #15785 https://github.com/pharo-project/pharo/pull/15785 - 15096-Backport-Pharo11-AdditionalMethodState-do-not-copy-the-AssociationsPragmas-when-growing-or-shrinking-15090 #15786 https://github.com/pharo-project/pharo/pull/15786 # Fixes - Position temp definition before first occurrence of extracted expression, and always in outer scope (fixes #14611) #15781 https://github.com/pharo-project/pharo/pull/15781 - Allow using ProfilerPresenter on code blocks #15772 https://github.com/pharo-project/pharo/pull/15772 - (Re)Moved Profile It command #1491 https://github.com/pharo-spec/Spec/pull/1491 - Fixed SubscriptionRegistry inspection freezing image #644 https://github.com/pharo-spec/NewTools/pull/644 # Rendering / Fonts - Make FreeTypeFont reuse instances #15756 https://github.com/pharo-project/pharo/pull/15756 - Fix #removeAllForFont: and #removeAllForType: on FreeTypeCache to support different scales #15752 https://github.com/pharo-project/pharo/pull/15752 # Spec - Add a Spec component list example #1488 https://github.com/pharo-spec/Spec/pull/1488 - Make sure that the first item is selected when opening a select dialâ¦ #1489 https://github.com/pharo-spec/Spec/pull/1489 # Refactoring Engine - RBCondition directlydefines -> RBDirectlyDefines #15755 https://github.com/pharo-project/pharo/pull/15755 - New Refactoring Driver for Renaming Shared Variables #15774 https://github.com/pharo-project/pharo/pull/15774 # ClassBuilder / Installer - ShiftClassInstaller: remove unused ivar #15748 https://github.com/pharo-project/pharo/pull/15748 - ClassBuilder: cleanups and #hasSameDefinitionAs: #15747 https://github.com/pharo-project/pharo/pull/15747 - 15758-duplicateClassWithNewName-leads-to-wrong-packageTag #15760 https://github.com/pharo-project/pharo/pull/15760 - ClassInstaller: clients can use #update:to: instead of #fillFor: #15765 https://github.com/pharo-project/pharo/pull/15765 - Try the ShAbstractClassChangeDetector new compare implementation #15776 https://github.com/pharo-project/pharo/pull/15776 - some small cleanups related to ClassBuilder / ClassVariables #15784 https://github.com/pharo-project/pharo/pull/15784 - ClassFactoryForTestCase #update:to: #15787 https://github.com/pharo-project/pharo/pull/15787 - Cleanup: old instance migration code (from before Shift) #15789 https://github.com/pharo-project/pharo/pull/15789 # Variables - Move-Slot-Exceptions #15743 https://github.com/pharo-project/pharo/pull/15743 - Remove the empty package Slot-Core #15757 https://github.com/pharo-project/pharo/pull/15757 - Fix: #hasSameDefinitionAs: for IndexedSlot #15767 https://github.com/pharo-project/pharo/pull/15767 - deprecate #anyUserOfClassVarNamed: #15788 https://github.com/pharo-project/pharo/pull/15788 # Fluid - Ring:â¯Use Fluid syntax for definition string #15763 https://github.com/pharo-project/pharo/pull/15763 - Ring: Migrate traits definition to fluid class syntax #15766 https://github.com/pharo-project/pharo/pull/15766 - 8055-RGClassStrategy-is-the-last-caller-of-definitionWithSlots #15775 https://github.com/pharo-project/pharo/pull/15775 # Tools - Remove change sorter #645 https://github.com/pharo-spec/NewTools/pull/645 - Creates Scopes Editor #585 https://github.com/pharo-spec/NewTools/pull/585 - 248-Definition-pane-on-class-inspector-should-let-the-user-edit-the-text-and-the-context-should-be-the-class- #636 https://github.com/pharo-spec/NewTools/pull/636 - Meta inspector tab unselection makes codepane nil #641 https://github.com/pharo-spec/NewTools/pull/641 # Cleanup - Remove not loaded packages #15793 https://github.com/pharo-project/pharo/pull/15793 - Reduce users of ChangeSet #15791 https://github.com/pharo-project/pharo/pull/15791 - Cleanup: setSourcePointer: vs sourcePointer #15762 https://github.com/pharo-project/pharo/pull/15762 - Repackage layout definitions symbols #15764 https://github.com/pharo-project/pharo/pull/15764

1 0