- Pharo-users - lists.pharo.org

Re: RB - New introduced refactorings

by Evelyn Cusi Lopez

Hi, The current move method to class side refactoring, doesn't correct the senders of this method, neither checks correctly references to instance variables or method calls (on instance side). At the moment this improvement only covers that method's senders won't break, creating a method on instance side with the same name referring to the method on side class, as shown in the example. - given a method ClassX >> annotatedBlockMarkup ^ '@@' the result of this refactoring is: ClassX >> annotatedBlockMarkup ^ self class annotatedBlockMarkup ClassX class >> annotatedBlockMarkup ^ '@@' I still need to improve, but it's a small advance that I wanted to show you to get feedback. Regards, Evelyn C. El lun, 8 feb 2021 a las 14:57, Kasper Osterbye (<kasper.osterbye(a)gmail.com>) escribiÃ³: > Hi > > How does your "move method to class side" differ from the one already > there? > > [image: image.png] > > Best, > > Kasper >

Feb. 8, 2021

Re: RB - New introduced refactorings

by Kasper Osterbye

Hi How does your "move method to class side" differ from the one already there? [image: image.png] Best, Kasper

Feb. 8, 2021

Re: pharo 8 - method versions - how to see author/timestamp?

by Davide Varvello

Esteban, Is there a hack I can do to put the timestamp in the VersionBrowser? Thanks Davide Esteban Lorenzano wrote > versions are going to stay there, we never even thought on removing that > ;) > they will come from Epicea instead the changes file (because yes, we want > to remove the changes file... but this one is a hard one ;) ). > and yes, they will have a timestamp (which is what the in-image versions > is lacking now). > > Esteban > On Feb 5 2021, at 4:47 pm, Noury Bouraqadi < > bouraqadi@ > > wrote: >> So, will this remain in the image, and the timestamp will be eventually >> fixed? >> >> Thanks -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Feb. 8, 2021

RB - New introduced refactorings

by Evelyn Cusi Lopez

Hello all, These weeks I added new refactorings, following I will give some examples of them. *1. Create accessors with lazy initialization* This refactoring create accessors for variables with lazy initialization, for example: - we have a class Object subclass: #SomeClass instanceVariableNames: 'stringVar' classVariableNames: '' package: 'Example' - we can create accessors with lazy initialization executing this script: (RBCreateAccessorsWithLazyInitializationForVariableRefactoring variable: #stringVar class: SomeClass classVariable: false defaultValue: '''example''') execute the result of this refactoring is: SomeClass >> stringVar ^ stringVar ifNil: [ stringVar := '' ] SomeClass >> stringVar: anObject stringVar := anObject *2. Extract setUp refactoring* (is the first version by the moment, it need to be improved) This refactoring create a setUp method from a code fragment. You can select an interval of some code in a test method and call this refactoring to create a setUp method implementing that code and replace the code by nothing. The selected class need to be a subclass of TestCase. For example: - given a class TestCase subclass: #SomeTest instanceVariableNames: '' classVariableNames: '' package: 'Example' SomeTest >>testFoo self x. self assert: true SomeTest >> self x self doSomething - To extract setUp method you can execute this script: (RBExtractSetUpMethodRefactoring extract: (10 to: 16) from: #testFoo in: SomeTest) execute the result of this refactoring is: SomeTest >> setUp super setUp. self x. SomeTest >> testFoo self assert: true *3. Move method to class side refactoring* (This refactoring is still awaiting review) This refactoring move a method to class side. For example: - given a method ClassX >> annotatedBlockMarkup ^ '@@' - we can execute the refactoring with this script: (RBMoveMethodToClassSideRefactoring method: (ClassX >> #annotatedBlockMarkup) class: ClassX) execute. the result of this refactoring is: ClassX >> annotatedBlockMarkup ^ self class annotatedBlockMarkup ClassX class >> annotatedBlockMarkup ^ '@@' Any suggestions or comment of these refactorings are welcome. I hope these new refactorings are useful to you . Regards, Evelyn C.

Feb. 8, 2021

UK Smalltalk User Group meeting - Wednesday February 24th

by Giovanni Corriga

The next meeting of the UK Smalltalk User Group will be on Wednesday, February 24th. Christian Haider will guide us in a tour of the Amber dialect of Smalltalk and its Silk web framework. In his own words... Amber [1], created by Nicolas Petton, is a Smalltalk implemented in JavaScript running in a web browser. Silk [2], written by the Amber maintainer Herby VojÄÃk, is a web framework in Amber. I was looking for a good solution for the web for a long time. At the last ESUG, I was bugging everybody about a Smalltalk in the browser, because I decided to redo the frontend of my current project [3] in Smalltalk instead of JavaScript. There were some developments, but only Amber was available. So I tried it for real on a little side project [4] to see if this route is viable - spoiler: it is! Silk, the web framework, caught my attention and I fell in love with it. Silk is very simple, straight forward and powerful, just the properties I love Smalltalk for. A Silk is basically a facade for a DOM node in the browser allowing the programmer to build up and manipulate the DOM in a direct way. Silk is so easy and intuitive that it never stood in the way and just worked. So, I could just concentrate on the complexities of the web (and the app). In this presentation I will walk you through the setup, show you the Amber tools and explore what you can do with Silk. I will try to justify my enthusiasm and appreciation for Silk :-). About me: My name is Christian Haider [5] and I use Smalltalk since the mid-90s. Fortunately, I earn my living with Smalltalk and use it on a daily bases (mostly VisualWorks). I like programming UIs and graphics. My largest open source contribution is a PDF library [6], the most significant one is Values [7]. [1] https://amber-lang.net/ [2] https://smalltalkrenaissance.wordpress.com/2015/06/29/silk-is-just-too-flex… [3] https://unsere-gelder.de/ (in German) [4] https://covidcrt.uber.space/ (sources at https://github.com/ChristianHaider/CoViD19UI) [5] https://christianhaider.de/ (in German) [6] https://wiki.pdftalk.de/doku.php [7] https://wiki.pdftalk.de/doku.php?id=complexvalues Given the current COVID-19 restrictions, 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/cbklbryccdbgc/ ) to receive the meeting details. Donât forget to bring your laptop and drinks! * <https://www.blogger.com/#>*

Feb. 7, 2021

Fwd: [Esug-list] grants Master Internship / offres de stage Master

by StÃ©phane Ducasse

> Begin forwarded message: > > From: Pierre Bommel <bommel(a)cirad.fr> > Subject: [Esug-list] grants Master Internship / offres de stage Master > Date: 3 February 2021 at 18:49:20 CET > To: esug-list(a)lists.esug.org > > Hello, Bonjour, Hola, > > We are looking for a Master internship to work on Cormas, a simulation platform (https://github.com/cormas/cormas <https://github.com/cormas/cormas> , or see here for our presentation at ESUG:https://hackmd.iscpif.fr/GGwvzBFqRASE5zCzlRwArQ?view <https://hackmd.iscpif.fr/GGwvzBFqRASE5zCzlRwArQ?view>). > Nous recherchons un stagiaire de Master pour travailler sur Cormas, une plateforme de simulation (https://github.com/cormas/cormas <https://github.com/cormas/cormas> , cf. notre prÃ©sentation Ã ESUG:https://hackmd.iscpif.fr/GGwvzBFqRASE5zCzlRwArQ?view <https://hackmd.iscpif.fr/GGwvzBFqRASE5zCzlRwArQ?view>). > Estamos buscando un estudiante de MaestrÃa para trabajar en Cormas. > > Voici l'annonce en franÃ§ais (in English below) : https://www.hdigitag.fr/fr/les-offres-de-stage-digitag/ <https://www.hdigitag.fr/fr/les-offres-de-stage-digitag/> > > Simulation participative de la gestion des ressources renouvelables dans des environnements hybrides > Mots-clÃ©: Simulation participative, Computer Vision , Smalltalk, Cormas > > DurÃ©e souhaitÃ©e du stage (nombre de mois): 8 > Date de dÃ©but du stage: 1/02/2021 > UnitÃ© de recherche: Green, Cirad > Contact: Bommel Pierre : bommel(a)cirad.fr <mailto:bommel@cirad.fr> > #DigitAg: Axe 2 : Innovations en agriculture numÃ©rique, Axe 6 : ModÃ©lisation et simulation (systÃ¨mes de production agricole) / Challenge 1 : Le challenge agroÃ©cologique, Challenge 2 : Le phÃ©notypage rapide, Challenge 6 : La gestion des territoires agricoles, Challenge 7 : IntÃ©gration de lâagriculture dans les chaÃ®nes de valeur, Challenge 8 : DÃ©veloppement agricole au Sud > Lâambition dâÃ©liminer les interfaces physiques qui permettent lâinteraction avec les machines est une idÃ©e ancienne dans le monde de lâinformatique qui a pris plusieurs directions. La plus emblÃ©matique pour le grand public a Ã©mergÃ© en 2005 sous le nom de âprojet Natalâ repris et dÃ©mocratisÃ© par Microsoft dans sa derniÃ¨re version baptisÃ©e âAzure Kinectâ (2019). Ce capteur dÃ©tecte les mouvements et les objets dans le champ de vision de lâutilisateur pour produire des rÃ©sultats dans un logiciel. Il a Ã©tÃ© abondamment dÃ©tournÃ© et enrichi depuis ses dÃ©buts grand public pour permettre de nouvelles maniÃ¨res dâinteragir avec les machines. > > Par ailleurs, le groupe de chercheurs Ã lâorigine de la crÃ©ation dâune plateforme de modÃ©lisation Ã base dâagents baptisÃ©e Cormas [1] fait actuellement face Ã des besoins accrus dâinteractivitÃ©s dans les simulations participatives. BasÃ©e sur le langage Smalltalk, Cormas est dÃ©veloppÃ©e depuis la fin des annÃ©es 1990 par une Ã©quipe fortement interdisciplinaire. Au-delÃ des usages traditionnels de la modÃ©lisation agents, Cormas se dÃ©marque des autres plateformes par des processus originaux de modÃ©lisation : lâapproche ComMod (pour Companion Modeling : modÃ©lisation dâaccompagnement [2]), qui vise Ã proposer des outils permettant de participer activement Ã la conception dâun modÃ¨le, mais aussi de sâimmerger dans des situations de jeux interactifs. Le jeu (de plateau ou informatisÃ©) sert alors de support pour Ã©changer sur une situation vÃ©cue. > > En 2012, pour la premiÃ¨re fois, lâÃ©quipe utilisait un video-projecteur Ã ultra-courte focale pour projeter sur une table un plateau de jeu. Ce simple changement a induit des comportements radicalement diffÃ©rents leur permettant une interaction beaucoup plus naturelle avec les simulations informatisÃ©es. En outre, la configuration spatiale des acteurs favorise les interactions sociales. Mais jusquâÃ aujourdâhui, la saisie manuelle par lâanimateur des dÃ©cisions prises par les joueurs reste nÃ©cessaire ce qui rÃ©duit la fluiditÃ© et la spontanÃ©itÃ© des interactions. > > LâÃ©quipe en charge du dÃ©veloppement de Cormas souhaite investiguer les possibilitÃ©s offertes par les nouvelles applications liÃ©es Ã la dÃ©tection dâobjets et de mouvements en portant un prototype de simulation participative dans le champ de la simulation hybride entre modÃ¨le informatique et jeu physique. Ce travail de preuve de concept appliquÃ© au modÃ¨le ReHab (modÃ¨le Ã©cole de ComMod) nÃ©cessitera de mettre au point des mÃ©thodes de dÃ©tection fiables dâobjets physiques pour Ãªtre intÃ©grÃ©es dans le calcul du nouvel Ã©tat simulÃ©. > > Aujourdâhui, Cormas sâappuie sur Pharo (Smalltalk open-source). Cette solution est dÃ©veloppÃ©e par lâINRIA et par un consortium de chercheurs et dâindustriels. La communautÃ© dynamique propose un ensemble de packages permettant de mutualiser le dÃ©veloppement de fonctionnalitÃ©s qui pourraient Ãªtre mobilisÃ©es pour proposer un prototype pour des simulation participative et la dÃ©tection dâobjets > > > English : https://www.hdigitag.fr/en/digitag-master2-internship-offers/ <https://www.hdigitag.fr/en/digitag-master2-internship-offers/> > > Participatory simulation of renewable resource management in hybrid environments > Keywords: Participatory simulation, Computer Vision , Smalltalk, Cormas > Duration: 8 months > Desired start date: 1/02/2021 > Research Unit: Green, Cirad > Contact: Bommel Pierre â bommel(a)cirad.fr <mailto:bommel@cirad.fr> > #DigitAg: Axe 2,Axe 6 â Challenge 1,Challenge 2 ,Challenge 6 ,Challenge 7, Challenge 8 > The ambition to remove the physical interfaces that allow interactions with computers is an old idea in the IT world that took several directions. The most emblematic one for the general public emerged in 2005 under the name of âProject Natalâ taken up and democratized by Microsoft in its latest version called âAzure Kinectâ (2019). This sensor detects movements and objects in the userâs field of vision to produce results in softwares. It has been abundantly diverted and enriched since its beginnings for the general public to allow new ways of interacting with computers. > > In addition, the group of researchers behind the development of an agent-based modeling platform called Cormas [1] is currently facing increased needs for interactivity in participatory simulations. Based on the Smalltalk language, Cormas has been developed since the late 1990s by a highly interdisciplinary team. Beyond the traditional uses of agent modeling, Cormas differs from other platforms by innovative modeling processes: the ComMod approach (Companion Modeling [2]), which aims to provide tools to actively participate in the design of a model, but also to immerse oneself in interactive game situations. The game (board or computer game) is then used as a support to exchange on a real-life situation. > > In 2012, for the first time, the team used an ultra-short focal projector to project a game board on a table. This simple change induced radically different behaviors of the actors allowing them to interact more naturally with computer simulations. In addition, the spatial configuration of the actors favors social interactions. But until today, manual input by the facilitator of the decisions taken by the players remains necessary, which reduces the fluidity and spontaneity of interactions. > > The team in charge of Cormasâ development wishes to investigate the possibilities offered by new opportunities related to the detection of objects and movements by bringing a prototype of participatory simulation in the field of hybrid simulation between computer model and physical game.This proof of concept work applied to the ReHab model (ComModâs school model) will require the development of reliable detection methods for physical objects to be integrated into the calculation of the new simulated state. > > Today, Cormas relies on Pharo (an open-source Smalltalk). This solution is implemented by INRIA and a consortium of researchers and industrialists. The dynamic community proposes a set of packages allowing to mutualize the development of functionalities that could be mobilized to propose a prototype for participative simulation and object detection > > _______________________________________________ > Esug-list mailing list > Esug-list(a)lists.esug.org > http://lists.esug.org/mailman/listinfo/esug-list_lists.esug.org -------------------------------------------- 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

Feb. 6, 2021

Re: RabbitMQ and Pharo

by vincent.blondeau＠polytech-lille.net

Hi Saogat, We are using it for handling distribution of test cases in Pharo. It is based on the SvenÂs Stomp library. You can take a look there: https://github.com/tesonep/pharo-testWorkers Cheers, Vincent From: saogat.rab--- via Pharo-users <pharo-users(a)lists.pharo.org> Sent: vendredi, 5 fÃ©vrier 2021 17:04 To: pharo-users(a)lists.pharo.org Cc: saogat.rab(a)icloud.com Subject: [Pharo-users] RabbitMQ and Pharo Hi, I was wondering if anyone here used RabbitMQ in Pharo. Would like to hear about your experience. Kind regards, Saogat

Feb. 5, 2021

Re: pharo 8 - method versions - how to see author/timestamp?

by Davide Varvello

Thanks Esteban, I've just found this thread of Stephane http://forum.world.st/Cant-add-local-git-repo-to-Iceberg-tp5116836p5117058.… that explains a bit Esteban Lorenzano wrote > Hi, > > From what I see, indeed you are missing some concepts of what iceberg is > and their relation with a package. > 1) iceberg is a VCS for Pharo, a frontend for git. > 2) an iceberg project stores packages and its versions (commits), but for > that you have to add or create an iceberg project and add the packages you > want to handle there. There is no automagical process. > 3) the "pharo" project there has what comes with pharo, not your packages. > If you want to store your packages, you need your own project. > > And well, that. > There are some videos around (no time to look for them now, but I am sure > someone can point to them) explaining how to use it and make things with > it. > But something to keep in mind, if you want to be happy with iceberg is: > Iceberg is NOT ENVY, and it will never be. Its design and patterns are > very different and require a different mindset to use it. > > Esteban > On Feb 5 2021, at 5:29 pm, Davide Varvello via Pharo-users < > pharo-users@.pharo > > wrote: >> Anyway Esteban, it's for sure a limit of mine, but It's an hour I'm >> trying to >> set up a local Iceberg for my package and I can't configure it. >> >> Some issue I faced: >> 1) I opened Iceberg and saw "pharo" had "Local repository missing", I >> guess >> there is a sort of default configuration so I tried to repair it. I ends >> with: "Project location does not seems to be a valid git repository." >> 2) Then I double clicked on "pharo" and searched for my package, there >> wasn't, so I added my package. Now the package is added but the local >> repository is always missing and I don't know how to create a new one. >> >> I wonder why there isn't a local repository by default when you create a >> package >> Thanks >> Davide >> >> >> >> Esteban Lorenzano wrote >> > indeed, it will fetch the history of each method that belongs to an >> > iceberg repository. >> > >> > Esteban >> > On Feb 5 2021, at 11:50 am, Davide Varvello via Pharo-users < >> >> > pharo-users@.pharo >> > > wrote: >> >> Hi Esteban, >> >> The "history" button in the minitoolbar of calypso is related to git, >> >> right? >> >> Because it's not shown in every method >> >> Cheers >> >> Davide >> >> >> >> >> >> Esteban Lorenzano wrote >> >> > Hi all, >> >> > >> >> > While the timestamp for the in-image change is, indeed, missing and >> >> needs >> >> > to be fixed, I want to point that we are abandoning the in-image >> author >> >> > tracking by method and replacing it with the git history (which wive >> >> you >> >> > also authorship and timestamp by commit). >> >> > This method commit history is already there (since Pharo 8) and can >> be >> >> > queried with the "history" button in the minitoolbar of calypso, >> same >> >> > place where you have the access to the version browser. >> >> > Yes, it is not the same, but it fulfills correctly (and improves it, >> >> since >> >> > it gives you the whole method history, not just what you have in >> image) >> >> > the old version functionality, which however will remain as a track >> of >> >> > in-image changes, but without the author (since is not needed). >> >> > >> >> > Even more, all the Author infrastructure is target for removal in >> next >> >> > versions of Pharo (just not right now :P) >> >> > cheers! >> >> > Esteban >> >> > >> >> > On Feb 5 2021, at 9:16 am, Richard Sargent < >> >> >> >> > richard.sargent@ >> >> > > wrote: >> >> >> Oh, yes/ That is one of the things I most love about ENVY and miss >> in >> >> >> everything else. >> >> >> What is the change history of this method, class, package, etc.? >> >> >> >> >> >> >> >> >> >> >> >> On Thu, Feb 4, 2021 at 10:09 PM Kasper Osterbye < >> >> >> >> > kasper.osterbye@ >> >> > (mailto: >> >> > kasper.osterbye@ >> >> > )> wrote: >> >> >> > I went in and updated the corresponding github issue >> >> >> (https://github.com/pharo-project/pharo/issues/7283) The tool is >> >> really >> >> >> useful, and it would be nice to have the author and timestamp in >> place >> >> >> again. >> >> >> > >> >> >> > >> >> >> > >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> -- >> >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >> >> >> >> >> >> >> >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >> -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Feb. 5, 2021

Re: RabbitMQ and Pharo

by Sven Van Caekenberghe

> On 5 Feb 2021, at 17:58, Gabriel Cotelli <g.cotelli(a)gmail.com> wrote: > > You can also take a look at https://github.com/ba-st/ansible Looks nice, Gabriel, I didn't know about this project. > On Fri, Feb 5, 2021, 13:04 saogat.rab--- via Pharo-users <pharo-users(a)lists.pharo.org> wrote: > Hi, > > > > I was wondering if anyone here used RabbitMQ in Pharo. Would like to hear about your experience. > > > > Kind regards, > > Saogat >

Feb. 5, 2021

Re: RabbitMQ and Pharo

by Gabriel Cotelli

You can also take a look at https://github.com/ba-st/ansible On Fri, Feb 5, 2021, 13:04 saogat.rab--- via Pharo-users < pharo-users(a)lists.pharo.org> wrote: > Hi, > > > I was wondering if anyone here used RabbitMQ in Pharo. Would like to hear > about your experience. > > > Kind regards, > > Saogat >

Feb. 5, 2021