- Pharo-users - lists.pharo.org

Removing and object from an OrderedCollection in the inspector
by sergio ruiz Jan. 14, 2024

Jan. 14, 2024

I am trying to remove some objects from an OrderedCollection in the inspector. I have class called Event. This has a class variable called Events which is a storage are for and ordered collection of Events. So, i inspected âEvent Eventsâ and I see my ordered collection. In the inspector, I select on of the objects, and I try to evaluate âEvent Events remove: selfâ.. But I am getting an error: an Event not found in OrderedCollection. Does anyone have any ideas on how iâd do this? Thanks! ï¿¼ ---- peace, sergio photographer, journalist, visionary Public Key: https://pgp.key-server.io/pks/lookup?op=get&search=0x69B08F58923AB3A2 #BitMessage BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV @sergio_101@mastodon.social https://sergio101.com http://www.codeandmusic.com http://www.twitter.com/sergio_101 http://www.facebook.com/sergio101

2 1

How to halt on Test errors?
by Davide Varvello Jan. 9, 2024

Jan. 9, 2024

Hi Guys, Sometimes I'd like to stop my test suite when an error occurs. My raw approach is to put a self halt in the TestResult>>addError:Â and look at the debugger, but I'm wondering if there is a more suitable way. Can you help me, please? TIADavide

5 9

[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

Re: [Pharo-dev] [ANN] success story: ApptiveGrid
by Norbert Hartl Dec. 29, 2023

Dec. 29, 2023

Thanks to all of you for the nice comments. I wish you, pharo and the community all the best for 2024. In 2024 there will be a soil release that I promised for this year but I didnât make it. Norbert > Am 14.12.2023 um 15:19 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: > > Yes, this is a really nice project, the front end as well. > > It reminds me a bit of FileMaker, but for the web. > > I am hoping you have commercial success with ApptiveGrid ! > >> On 12 Dec 2023, at 13:02, Norbert Hartl <norbert(a)hartl.name> wrote: >> >> 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. >> >> <BildschirmÂfoto 2023-12-12 um 12.39.29.png> >> >> 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â¦ >> >> <BildschirmÂfoto 2023-12-12 um 12.40.48.png> >> >> 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. >> >> <BildschirmÂfoto 2023-12-12 um 12.44.10.png> >> >> 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 >>

1 0

Smallscript - A Smalltalk-Inspired Scripting Language
by Craig Johnson Dec. 28, 2023

Dec. 28, 2023

for those who are interested. https://www.codeproject.com/Articles/5373567/Smallscript-A-Smalltalk-Inspir…

3 2

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

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

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

Dec. 14, 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

2 1

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

Dec. 11, 2023

# Features - Add class comment as tooltip in Calypso. #15660 https://github.com/pharo-project/pharo/pull/15660 - Add file out for Epicea entries #15644 https://github.com/pharo-project/pharo/pull/15644 - Debugger: Integrating assertion rewriting (2nd attempt) #626 https://github.com/pharo-spec/NewTools/pull/626 # Fixes - Prevent font chooser open error listing #638 https://github.com/pharo-spec/NewTools/pull/638 - Preventing "Run to" debugger command from raising update events, in order to prevent unnecessary (and broken) updates #642 https://github.com/pharo-spec/NewTools/pull/642 - Traits: Fix wrong source pointer (v2) #15741 https://github.com/pharo-project/pharo/pull/15741 - Fix: Syntax highlight of inst vars in inspector eval pane #15723 https://github.com/pharo-project/pharo/pull/15723 - Calypso: Do not crash if a baseline is wrongly defined #15711 https://github.com/pharo-project/pharo/pull/15711 - Fix ephemeron support in Fuel #15670 https://github.com/pharo-project/pharo/pull/15670 - Change to size_t for ffi calls that currently use ulong for pointers. #15696 https://github.com/pharo-project/pharo/pull/15696 - Fix a ZeroDivide exception when scroll target is 0 calculating scroll deltas #15702 https://github.com/pharo-project/pharo/pull/15702 - Fix/baseline repo #15629 https://github.com/pharo-project/pharo/pull/15629 # Rendering / Graphics - Rework #nonCachingFullDrawOn: on HandMorph to use a matching ScalingCanvas for the shadow form #15736 https://github.com/pharo-project/pharo/pull/15736 - Add #drawFormSet:at: and #translucentFormSet:at: to AthensCanvasWrapper #15735 https://github.com/pharo-project/pharo/pull/15735 - Add ScalingCanvas and #canvasScaleFactor for OSWorldRenderer #15647 https://github.com/pharo-project/pharo/pull/15647 - Add initialization of ScalingCanvas to BaselineOfMorphic #15672 https://github.com/pharo-project/pharo/pull/15672 - Fix #checkForNewScreenSize on OSWorldRenderer to also check the #actualScreenSize #15673 https://github.com/pharo-project/pharo/pull/15673 - Make MorphTreeNodeMorph and IndentingListItemMorph use a FormSet for the expand/collapse toggle #15676 https://github.com/pharo-project/pharo/pull/15676 - Refactor IconicButtonMorph to support use of a FormSet #15680 https://github.com/pharo-project/pharo/pull/15680 # Refactoring Engine - Tests and enhancements for RenameInstanceVariableDriver #15703 https://github.com/pharo-project/pharo/pull/15703 - Refactor: extract method third pass #15693 https://github.com/pharo-project/pharo/pull/15693 - New Refactoring Driver to rename variables #15617 https://github.com/pharo-project/pharo/pull/15617 - Cleanup/extract method first pass #15674 https://github.com/pharo-project/pharo/pull/15674 - Test: removal of non-empty class with subclasses #15671 https://github.com/pharo-project/pharo/pull/15671 - Refactor: extract method transformation cleanup #15675 https://github.com/pharo-project/pharo/pull/15675 - Enhance driver #15679 https://github.com/pharo-project/pharo/pull/15679 # Variables - 15665-Not-possible-to-edit-slots-when-using-new-definition-format--RBLiteralValueNode-DNU-name #15667 https://github.com/pharo-project/pharo/pull/15667 - Do not use #classVarNamed: / #classVarNamed:put: #15685 https://github.com/pharo-project/pharo/pull/15685 - refactor more #classPool users #15710 https://github.com/pharo-project/pharo/pull/15710 - rewrite #anyUserOfClassVarNamed: using the Variable API #15717 https://github.com/pharo-project/pharo/pull/15717 - Cleanup: move extension methods Slot package to where the classes are #15742 https://github.com/pharo-project/pharo/pull/15742 # Compiler / Compilation / CompiledMethods - 15697-Playground-need-to-color-not-yet-created-bindings-red #15698 https://github.com/pharo-project/pharo/pull/15698 - move error handling from CompiledMethod to CompiledCode and rename #15651 https://github.com/pharo-project/pharo/pull/15651 - 15640-Objectclone-has-code-for-CompiledCode #15648 https://github.com/pharo-project/pharo/pull/15648 - 15126-IRSequencenotEmpty-should-be-isNotEmpty #15714 https://github.com/pharo-project/pharo/pull/15714 - deprecate #noPattern and noPattern: #15715 https://github.com/pharo-project/pharo/pull/15715 - 6470-Improve-the-class-comment-of-RBScanner #15716 https://github.com/pharo-project/pharo/pull/15716 - 15596-Cleanup-respondsTo-check-for-doItReceiver #15712 https://github.com/pharo-project/pharo/pull/15712 - cleanup #doitReceiver check #1485 https://github.com/pharo-spec/Spec/pull/1485 # Class Builder / Class Installer - Merge package Shift-Changes into the main Shift-ClassBuilder package #15663 https://github.com/pharo-project/pharo/pull/15663 - check if we can have WeakLayout as a subclass of VariableLayout #15658 https://github.com/pharo-project/pharo/pull/15658 - reduce the senders of #asSlotCollection #15659 https://github.com/pharo-project/pharo/pull/15659 - do not use #slotsFromString: / sharedVariablesFromString: #15654 https://github.com/pharo-project/pharo/pull/15654 - Small cleanup ClassInstaller #15686 https://github.com/pharo-project/pharo/pull/15686 - ClassBuilder: remove Ficus from Shift baseline #15690 https://github.com/pharo-project/pharo/pull/15690 - Classbuilder: rewrite users of #sharedPools: with string arguments #15695 https://github.com/pharo-project/pharo/pull/15695 - use sharedPoolsFromString: in old style class defs and Hermes #15706 https://github.com/pharo-project/pharo/pull/15706 - Deprecate old API for traits #15713 https://github.com/pharo-project/pharo/pull/15713 - simplify and comment #sharedVariablesFromString #15692 https://github.com/pharo-project/pharo/pull/15692 - move ClassInstaller into the Builder package #15727 https://github.com/pharo-project/pharo/pull/15727 - ClassInstaller: use the oldClass of the builder #15739 https://github.com/pharo-project/pharo/pull/15739 # Bootstrap / Full Image Load - Introduce Kernel-CodeModel package #15583 https://github.com/pharo-project/pharo/pull/15583 - Update BaselineOfPharoBootstrapProcess.class.st #15691 https://github.com/pharo-project/pharo/pull/15691 - Extract ClassDefinitionPrinters from the Kernel #15656 https://github.com/pharo-project/pharo/pull/15656 # CI/Tests - No rule check for non-existing super implementor (Second PR) #15705 https://github.com/pharo-project/pharo/pull/15705 - Better name for testNoSentButNotImplementedSelectors #15720 https://github.com/pharo-project/pharo/pull/15720 - ReSuperSendsNewRule has a typo in description (#initiailize -> #initiâ¦ #15725 https://github.com/pharo-project/pharo/pull/15725 # Cleanup - Remove ChangeSorter from loading #634 https://github.com/pharo-spec/NewTools/pull/634 - Harvested and improved some changes proposed in a PR that was also reâ¦ #15745 https://github.com/pharo-project/pharo/pull/15745 - Startup preferences shoud not be in morphic baseline #15731 https://github.com/pharo-project/pharo/pull/15731 - Fix a deprecated send in testComparisonToSimilarQueryButWithDifferentTag #15661 https://github.com/pharo-project/pharo/pull/15661 - Merge package ParametrizedTests into SUnit #15662 https://github.com/pharo-project/pharo/pull/15662

1 0