May 2021 - Pharo-dev - lists.pharo.org

Progress Report -> Refactoring Project - ( May 24 - May 28)

by Evelyn Cusi Lopez

Hi everyone, Last week I did these tasks: - Add the scopes list to the calypso browser (took longer than expected because it had to mimic the behavior of Calypso scopes to receive and execute queries). See the changes in the branch: DefaultScope <https://github.com/Lin777/pharo/tree/DefaultScope>. See the new behavior in the video: Youtube video <https://youtu.be/BV1qSw-Pgdc>. - Add settings option to select a default scope . See the changes in the branch: DefaultScope <https://github.com/Lin777/pharo/tree/DefaultScope>. [image: imagen.png] - Add an intermediate class between modal and dialog to be able to use modals as dialogs specifically in refactorings because these have a strange behavior to get user values (this pr is still pending approval in the Spec project). Check the changes in the PR <https://github.com/pharo-spec/Spec/pull/1079>. To fix issues: #9060 <https://github.com/pharo-project/pharo/issues/9060> and #5894 <https://github.com/pharo-project/pharo/issues/5894>. - Start to fix the rename instance variable refactoring in live objects (check the discussion in a forum <https://github.com/pharo-project/pharo/issues/8665> provided by *seandenigris* to guide me a little better) Tasks for this week: <https://github.com/pharo-project/pharo/issues/9142> <https://github.com/pharo-project/pharo/issues/9142> - Fix issue: RB - Improve instance variable refactoring #8665 <https://github.com/pharo-project/pharo/issues/8665> - Improve messages: No understable message #9229 <https://github.com/pharo-project/pharo/issues/9241> - Fix issue: RB - Inline all senders of class methods (instance creation) doesn't work, need improve pattern to search #9142 <https://github.com/pharo-project/pharo/issues/9142> - Add option to rename scopes of scope lists. - Fix issue: Push Method does not work when the method contains a super call <https://github.com/pharo-project/pharo/issues/9289> - Fix issue: preview default button should be apply <https://github.com/pharo-project/pharo/issues/9263> <https://github.com/pharo-project/pharo/issues/9241> Regards, Evelyn C.

May 31, 2021

2 years engineer position

by StÃ©phane Ducasse

Hello The RMOD team has a two year engineer position to work on building tools around Moose. If you are interested or know someone that can be interested let me know. 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

May 31, 2021

Re: Fuel projects, anyone?

by Max Leske

Thanks Gabriel, that's great! I've added Launchpad to the list. On 27 May 2021, at 22:15, Gabriel Cotelli wrote: > We're using Fuel to serialize the stack on unexpected errors to ease > further debugging. See > https://github.com/ba-st/Launchpad/blob/release-candidate/source/Launchpad/…. > > So any project using ba-st/Launchpad <https://github.com/ba-st/Launchpad> > is indirectly using Fuel. For the record, the Pharo components running in > the backend of https://mercapabbaco.com are using this technique. > > Cheers, > Gabriel > > On Thu, May 27, 2021 at 5:09 PM Max Leske <maxleske(a)gmail.com> wrote: > >> Hi everyone, >> >> I was made aware that there actually *are* people who use Fuel :) I >> rarely get feedback, apart from the spare bug report, so I was thrilled to >> hear about people who use it actively or even have applications in >> production that rely on Fuel. >> >> To celebrate that (and boost my own ego of course...) I've added a >> "Projects using Fuel" section to the readme on GitHub and I'd love to see >> more entries in that list! So please let me know (or open a PR!) if you >> think your project deserves some exposure ;) >> >> Here's the link: https://github.com/theseion/Fuel. >> >> Stay awesome and positive! >> >> Cheers, >> Max >>

May 28, 2021

This week (21/2021) on the Pharo Issue Tracker

by Marcus Denker

We merged 7 Pull Requests and closed 5 issues in the main issue tracker. Focus this week was the merge of the latest newtools/spec2. Merge newtools 0.6.6 ==================== - playground ensures content is flushed to disk when closed (to prevent data lost for fast closing it) - inspector adds extensions for: integer, morph, baselines. - removes all dependencies with old GTSpotter - several fixes on debugger - lots of tests - CI infrastructure improvements - https://github.com/pharo-spec/NewTools/releases/tag/v0.6.6 Merge spec2 0.8.13 =================== - general: menu items now print correctly shortcuts (using KMShortcutPrinter) - general: buttons disabled now "gray" icons. - fixed SpGridLayout homogeneous and span properties. - fixed trees selected paths and items when using multiple selection. - fixed wrong accumulation of selected elements in multiple selection. - fixed pharo-spec/Spec#1070 (thanks @jordanmontt) - SpTextPresenter now implements lineAtCursorPosition method, which will enhance the selected based commands. - fixes #9121 - replace usages of newVertical/newHorizontal when possible (we prefer newTopToBottom/newLeftToRight) - SpNotebookPresenter fix a problem when setting pages directly with anything that is not an OrderedCollection (remove of pages was failing). - SpCodePresenter now allow selecting a particular syntax highlight theme (default is still the one selected on settings). - SpApplication implements showWaitCursorWhile: to allow different backend functionality (and start removing usages of UIManager). - fixed hidden dependencies in baseline and demos - lots of cleanups - lots of renames to make things more understandable (thanks @NourDjihan) - lots of new tests Cleanups / Tests ================= - ReleaseTest-DocComments #9325 This turns existing doc-comments into 892 tests https://github.com/pharo-project/pharo/pull/9325 - 9114-Locale-seem-to-use-two-class-vars-for-the-same-thing #9216 https://github.com/pharo-project/pharo/pull/9216 - Add comment to collection package #9301 https://github.com/pharo-project/pharo/pull/9301 Fixes ===== - Another fix for unescapeCharacter #9303 https://github.com/pharo-project/pharo/pull/9303 - 9299-Method-classification-in-the-list-of-implementors-causes-DNU #9304 https://github.com/pharo-project/pharo/pull/9304

May 28, 2021

Re: Fuel projects, anyone?

by Gabriel Cotelli

Yes, it's here https://pharo.org/success/Abbacco. There are a couple of new components since this was published On Thu, May 27, 2021 at 5:27 PM Esteban Lorenzano <estebanlm(a)netc.eu> wrote: > Hola Gabriel! > > I will be curious... which components are those? > Do we have a success story with them? ;) > > Esteban > On May 27 2021, at 10:15 pm, Gabriel Cotelli <g.cotelli(a)gmail.com> wrote: > > We're using Fuel to serialize the stack on unexpected errors to ease > further debugging. See > https://github.com/ba-st/Launchpad/blob/release-candidate/source/Launchpad/…. > > So any project using ba-st/Launchpad <https://github.com/ba-st/Launchpad> is > indirectly using Fuel. For the record, the Pharo components running in the > backend of https://mercapabbaco.com are using this technique. > > Cheers, > Gabriel > > On Thu, May 27, 2021 at 5:09 PM Max Leske <maxleske(a)gmail.com> wrote: > > Hi everyone, > > I was made aware that there actually *are* people who use Fuel :) I > rarely get feedback, apart from the spare bug report, so I was thrilled to > hear about people who use it actively or even have applications in > production that rely on Fuel. > > To celebrate that (and boost my own ego of course...) I've added a > "Projects using Fuel" section to the readme on GitHub and I'd love to see > more entries in that list! So please let me know (or open a PR!) if you > think your project deserves some exposure ;) > > Here's the link: https://github.com/theseion/Fuel. > > Stay awesome and positive! > > Cheers, > Max > >

May 27, 2021

Re: Fuel projects, anyone?

by Esteban Lorenzano

Hola Gabriel! I will be curious... which components are those? Do we have a success story with them? ;) Esteban On May 27 2021, at 10:15 pm, Gabriel Cotelli <g.cotelli(a)gmail.com> wrote: > We're using Fuel to serialize the stack on unexpected errors to ease further debugging. See https://github.com/ba-st/Launchpad/blob/release-candidate/source/Launchpad/…. > > So any project using ba-st/Launchpad (https://github.com/ba-st/Launchpad) is indirectly using Fuel. For the record, the Pharo components running in the backend of https://mercapabbaco.com are using this technique. > > Cheers, > Gabriel > > > > On Thu, May 27, 2021 at 5:09 PM Max Leske <maxleske(a)gmail.com (mailto:maxleske@gmail.com)> wrote: > > Hi everyone, > > > > I was made aware that there actually are people who use Fuel :) I rarely get feedback, apart from the spare bug report, so I was thrilled to hear about people who use it actively or even have applications in production that rely on Fuel. > > To celebrate that (and boost my own ego of course...) I've added a "Projects using Fuel" section to the readme on GitHub and I'd love to see more entries in that list! So please let me know (or open a PR!) if you think your project deserves some exposure ;) > > Here's the link: https://github.com/theseion/Fuel. > > Stay awesome and positive! > > Cheers, > > Max > > > > > > > > > >

May 27, 2021

Re: Fuel projects, anyone?

by Gabriel Cotelli

We're using Fuel to serialize the stack on unexpected errors to ease further debugging. See https://github.com/ba-st/Launchpad/blob/release-candidate/source/Launchpad/…. So any project using ba-st/Launchpad <https://github.com/ba-st/Launchpad> is indirectly using Fuel. For the record, the Pharo components running in the backend of https://mercapabbaco.com are using this technique. Cheers, Gabriel On Thu, May 27, 2021 at 5:09 PM Max Leske <maxleske(a)gmail.com> wrote: > Hi everyone, > > I was made aware that there actually *are* people who use Fuel :) I > rarely get feedback, apart from the spare bug report, so I was thrilled to > hear about people who use it actively or even have applications in > production that rely on Fuel. > > To celebrate that (and boost my own ego of course...) I've added a > "Projects using Fuel" section to the readme on GitHub and I'd love to see > more entries in that list! So please let me know (or open a PR!) if you > think your project deserves some exposure ;) > > Here's the link: https://github.com/theseion/Fuel. > > Stay awesome and positive! > > Cheers, > Max >

May 27, 2021

Fuel projects, anyone?

by Max Leske

Hi everyone, I was made aware that there actually *are* people who use Fuel :) I rarely get feedback, apart from the spare bug report, so I was thrilled to hear about people who use it actively or even have applications in production that rely on Fuel. To celebrate that (and boost my own ego of course...) I've added a "Projects using Fuel" section to the readme on GitHub and I'd love to see more entries in that list! So please let me know (or open a PR!) if you think your project deserves some exposure ;) Here's the link: https://github.com/theseion/Fuel. Stay awesome and positive! Cheers, Max

May 27, 2021

Pharo Progress Report 2021-05-26

by Esteban Lorenzano

(I changed the date format of this mails to something that is clear also in north america :) ) No much change since last week, with one task entering short term goals (in bold) and the rest unchanged (there was movement... just none of the tasks was finished :P). Short-term goals: - Improve integration infrastructure for Spec2 and NewTools frameworks. - Improve quality and quantity of tests in Spec2 and NewTools frameworks. - Improve quality of class comments in Spec2 framework. - Since we are in freeze mode: fixing important bugs on Pharo9 and its components (this issue will stay here until release). - include M1 in PharoLauncher Medium-term goals: - Removal of GTTools - M1 VM release. - Release 9.0 ## Last week - working on infrastructure (github actions and improving baselines and merge). - Some enhancements to SpApplication (UI interactions), SpCodePresenter - Added more tests to StInspector - merged Spec2 0.9.13 (lots of improvements, see https://github.com/pharo-spec/Spec/releases/tag/v0.8.13) - Pablo was working on improvements in the Test Runner and some experiments for future work on GC. - Guille was working on profiling (a time consuming task, pun intended ;)) and metalinks - Christophe is back and resuming the work on PharoLauncher (command line) - Marcus was sketching some future clean ups and refactors (for Pharo 10) and as always, processing PRs :) ## This week - finish a pass on NewTools (v0.6.6) - start a clean up pass on Spec - improve testing of NewTools (Infrastructure in general, StInspector if time). - Resume plans for Pakbot (old Cargo)

May 26, 2021

Re: Open Sound Control Package for Pharo 9.0

by ducasse

Thanks for the PR. I do not know if you saw but there is also the Tuio package (I added a smoke test) because there was no test. But normally it uses OSC. s > On 22 May 2021, at 00:54, GÃ¼nter Khyo via Pharo-dev <pharo-dev(a)lists.pharo.org> wrote: > > Thanks to Sven's tips I fixed the package and ditched the hacky Stream class. I also cleaned up some messy parts in the implementation. I noticed that the current implementation does not handle blobs and the server packet processing logic could be improved. Also, I am not sure whether recursive bundles are handled correctly (more test cases needed) and to which extent they are used in OSC applications, so one would have to do a fair bit of polishing for an "industry grade" implementation. > > In any case, if there are any users that would like to use and test OSC, I am happy to take feedback and make necessary additions/modifications. > > Stef, I'll send you a pull request tomorrow, now I have to catch some sleep. > > On 5/21/21 6:23 PM, ducasse wrote: >> Thanks. >> I do not think that it is good to reintroduce this super ugly class. at the minimum it should be in a separate branch. >> >> S >> >>> On 21 May 2021, at 18:06, GÃ¼nter Khyo via Pharo-dev <pharo-dev(a)lists.pharo.org <mailto:pharo-dev@lists.pharo.org>> wrote: >>> >>> Hi Stef, >>> >>> Great! I'll send you a pull-request for the "hotfix" this evening. As I mentioned to Sven, I'll do some rework on the implementation and documentation when I find the time. >>> >>> GÃ¼nter >>> >>> On 5/21/21 5:55 PM, ducasse wrote: >>>> I checked and all the tests pass on Pharo80. >>>> Now I did a little pass on the tests. >>>> I do not have the time to migrate this lib to P9. >>>> But I would accept Pull Requests :) >>>> >>>> S. >>>> >>>>> On 21 May 2021, at 17:46, ducasse <stepharo(a)netcourrier.com <mailto:stepharo@netcourrier.com>> wrote: >>>>> >>>>> The old travis was telling that the code works in 6.1, 7 and 8.0 >>>>> I added GithubActions for Pharo 80 and I will see. >>>>> >>>>> S >>>>> >>>>>> On 21 May 2021, at 17:40, ducasse <stepharo(a)netcourrier.com <mailto:stepharo@netcourrier.com>> wrote: >>>>>> >>>>>> Hi gunter >>>>>> >>>>>> Iâm maintaining OSC >>>>>> https://github.com/Ducasse/OSC <https://github.com/Ducasse/OSC> >>>>>> and TUIO >>>>>> https://github.com/Ducasse/TUIO <https://github.com/Ducasse/TUIO> >>>>>> >>>>>> Please do some PR if something does not work. >>>>>> >>>>>> S >>>>>> >>>>>>> On 21 May 2021, at 14:02, GÃ¼nter Khyo via Pharo-dev <pharo-dev(a)lists.pharo.org <mailto:pharo-dev@lists.pharo.org>> wrote: >>>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> I have ported the Open Sound Control package to Pharo 9.0. Since the Catalog Browser is marked as legacy, I was wondering how to submit the patch. Is there a git repository? I attached the fileout to this email in case anybody wants to take a look at the package or knows how/where to add it to Pharo 9.0, >>>>>>> >>>>>>> Patch Note: >>>>>>> >>>>>>> OSC relies on the removed RWTextOrBinaryStream class which has very specific behavior that I could not emulate using the available stream and codec classes, so I pulled in the class from Squeak 5, renamed it to OSCStream and added it to the OSC package. This seemed to be the easiest way to do it without changing the OSC implementation, but I welcome any suggestions for a cleaner solution. >>>>>>> >>>>>>> GÃ¼nter >>>>>>> >>>>>>> <OSC.st <http://osc.st/>> >>>>>> >>>>> >>>> >> > <OSC.st>

May 22, 2021