March 2019 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] OSProcess for Pharo 7

by ducasse

Max ifNotNilDo: was probably deprecated in Pharo 50 so this is a bit normal that it got removed in P7. But we should check this. I do not have the time today for this. normally ifNotNilDo: should be covered by a migrator automatic rewrite rules (can you check?): Ducasse/Migrator because in such case you load the migrator packages and execute the tests of the OSProcess (if any) then you execute OSProcess and the user of ifNotNilDo: will be automatically rewritten and you are just left to check the senders that are left and commit a new version. If IfNotNilDo: is not covered by a automated migration we should add one. It was deprecated before the automated migrations were introduced. Now about your question: yes a new version of OSProcess should be produced for P7. The best would be to migrate it to github. Let me know if it helps. Stef > On 11 Mar 2019, at 08:00, Max Leske <maxleske(a)gmail.com> wrote: > > Hi all, > > Pharo 7 no longer includes #ifNotNilDo:, meaning that OSProcess loading fails. I volunteer to update OSProcess for Pharo 7 but I need someone to tell me what the expected workflow is. AFAICT, we've simply copied the current ConfigurationOf to the MetaRepoForXX in the past without making any changes specific to Pharo. That will not work this time. > So, should I create a new version of OSProcess for all platforms, where #ifNotNilDo: has been replaced with #ifNotNil:? Or should I add a compatibility package for Pharo? Or something else? > > Cheers, > Max >

March 11, 2019

OSProcess for Pharo 7

by Max Leske

Hi all, Pharo 7 no longer includes #ifNotNilDo:, meaning that OSProcess loading fails. I volunteer to update OSProcess for Pharo 7 but I need someone to tell me what the expected workflow is. AFAICT, we've simply copied the current ConfigurationOf to the MetaRepoForXX in the past without making any changes specific to Pharo. That will not work this time. So, should I create a new version of OSProcess for all platforms, where #ifNotNilDo: has been replaced with #ifNotNil:? Or should I add a compatibility package for Pharo? Or something else? Cheers, Max

March 11, 2019

Esteban's ChangeLog week of 4 March 2019

by estebanlm＠gmail.com

Hello! This is my weekly ChangeLog, from 4 March 2019 to 10 March 2019. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=4/3/2019&to=10/3/2019 ChangeLog ========= 6 March 2019: ------------- * I spent last two days trying approaches to make the introduction of +Application+ concept less intrusive. Thing is, since several applications can be alive at the same time (in general at least two: Pharo and the application the user is developing, but there can be more), when you create a window, is mandatory to know the application it belongs to. And this is a problem. Why? Well, because there are two ways to do it: It can be: ---- MyWindowClass newApplication: myApplication. ---- or: ---- myApplication new: MyWindowClass. ---- And well... both approaches require that you are in possesion of an application when you create a window. In an application of certain complexity (not to talk about Pharo complexity itself), this can be a problem (hello, singletons!). I explored the approach of having one active application at a time... but what happens when you are running application A and you need to pop a debugger? How to choose the right application? After some consideration, I came to the conclusion that is not possible, and that decision needs to be binded to the development itself. So, how to solve this? Is a matter of each application. * It is possible for some applications to pass the application between components. One can arwe UI decisions need to be taken at UI level, and is fine to have the application available at that level. * Is possible to have *for your application* a "runningApplication"... a class variable in your SpecApplication override. This is a singleton, yes, but sometimes you need it... Maybe Pharo will go this way. 4 March 2019: ------------- * Today I completed the first step on the introduction of +Application+ for Spec2. As we have told, an application is the entry point of any Spec Application. It will handle the creation and flow of windows and the resources used by it (long term goal: no more UIManager, UITheme, ThemeIcons and other singletons that pollute the system). Anyway, for now I just managed to introduce a generic application and refactored the +ComposablePresenter+, extracting the window functionality from them and moving it to a default +Application+. It sounds simple, but it was a big change. A diagram of how this has changed: ---- Before: ComposablePresenter -> WindowPresenter \ ComposablePresenter* ---- ---- Now: Application -> WindowPresenter -> ComposablePresenter -> ComposablePresenter* ---- This way of handling windows allows a tight control of what is open and in what order, and a way to handle resources other tghan a singleton in the system. cheers! Esteban

March 11, 2019

Re: [Pharo-dev] [ANN] Pharo Consortium New Academic Member: CIRAD

by askoh

It would be very interesting if there is a list showing what each consortium member uses Pharo or Smalltalk for. Thanks, Aik-Siong Koh -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

March 11, 2019

[Pharo 8.0] Build #123: Revert "Adds a new exception for a missing class error (ClassNotUnderstood) andâ¦"

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #123 was: FAILURE. The Pull Request #2784 was integrated: "Revert "Adds a new exception for a missing class error (ClassNotUnderstood) andâ¦"" Pull request url: https://github.com/pharo-project/pharo/pull/2784 Issue Url: https://pharo.fogbugz.com/f/cases/revert Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 10, 2019

[Pharo 8.0] Build #122: Adds a new exception for a missing class error (ClassNotUnderstood) andâ¦

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #122 was: FAILURE. The Pull Request #2783 was integrated: "Adds a new exception for a missing class error (ClassNotUnderstood) andâ¦" Pull request url: https://github.com/pharo-project/pharo/pull/2783 Issue Url: https://pharo.fogbugz.com/f/cases/2776 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 10, 2019

Re: [Pharo-dev] DrTests and enhancing testing experience in Pharo

by ducasse

Thanks Dayne and DrTest is the work of Julien that is supervising Dayne with Guille. She is lucky to work with great guys. > On 8 Mar 2019, at 18:16, Dayne Lorena Guerra Calle <guerra.dayne(a)gmail.com> wrote: > > Hello everyone! > > My name is Dayne Guerra, Iâm a bachelor student in computer science in Bolivia. > > Iâm working on Pharo for my bachelorâs final project. My mentors are StÃ©phane Ducasse and Juan Pablo Sandoval. > Iâve started by commenting methods and later I worked on a plugin that creates tests from executable comments (e.g. â(4+1)>>>5â) > I have a video demo: https://youtu.be/DgR2YETzjfA <https://youtu.be/DgR2YETzjfA> Itâs a plugin for DrTests (https://github.com/juliendelplanque/DrTests <https://github.com/juliendelplanque/DrTests>) > > DrTests project aims to provide a plugin-based UI to deal with tests in Pharo. It will provide the same features as the actual SUnit UI (i.e., running tests, profiling tests and computing code-coverage) but will allow to plug additional analysis on unit tests such as for example: the mutation testing framework and the rotten tests finder. > > Once my work on DrTest is done, I will probably work on enhancing SUnit API as well. > New ideas and feedback is always welcome. > > Regards, > > Dayne Guerra

March 8, 2019

DrTests and enhancing testing experience in Pharo

by Dayne Lorena Guerra Calle

Hello everyone! My name is Dayne Guerra, Iâm a bachelor student in computer science in Bolivia. Iâm working on Pharo for my bachelorâs final project. My mentors are StÃ©phane Ducasse and Juan Pablo Sandoval. Iâve started by commenting methods and later I worked on a plugin that creates tests from executable comments (e.g. â(4+1)>>>5â) I have a video demo: https://youtu.be/DgR2YETzjfA Itâs a plugin for DrTests (https://github.com/juliendelplanque/DrTests) DrTests project aims to provide a plugin-based UI to deal with tests in Pharo. It will provide the same features as the actual SUnit UI (i.e., running tests, profiling tests and computing code-coverage) but will allow to plug additional analysis on unit tests such as for example: the mutation testing framework and the rotten tests finder. Once my work on DrTest is done, I will probably work on enhancing SUnit API as well. New ideas and feedback is always welcome. Regards, Dayne Guerra

March 8, 2019

Re: [Pharo-dev] Migrating XML support to github/PharoContributions/

by ducasse

Thanks. I sent you an invit. Stef > On 8 Mar 2019, at 14:22, Albrecht Baur <baur.albrecht(a)googlemail.com> wrote: > > > From: Albrecht Baur <baur.albrecht(a)googlemail.com> > Subject: Re: [Pharo-dev] Migrating XML support to github/PharoContributions/ > Date: 8 March 2019 at 14:22:43 CET > To: pharo-dev(a)lists.pharo.org > > > On 08.03.19 13:51, ducasse wrote: >>>> In case someone wants to use it: I used Peters nice migration tool for ... >>>> http://smalltalkhub.com/#!/~PharoExtras/LDAP/ <http://smalltalkhub.com/#!/~PharoExtras/LDAP/> >>>> ... and put it to: >>>> https://github.com/a2b-alb/PharoExtras-LDAP <https://github.com/a2b-alb/PharoExtras-LDAP> >>>> I don't know if this is the right place or if you would rather have it under ... >>>> https://github.com/pharo-contributions/ <https://github.com/pharo-contributions/> >>>> ... or somewhere else. >>> Thanks >>> and it would be good. >> >> I do not know what is the best process to add something to pharo-contributions. >> May be we should fork your version and put it there and that people continue to contribute >> using PRs. >> What do you think? > We could fork my version as you described or we could do the migration again to have a clean push into an new repo e.g. github.com/pharo-contributions/LDAP > > (I can do this if you want - I have still the snippets here... I just wanted to have LDAP on a save place because I need it and decided not to place it in my private gitlab instance...) > If someone (CyrilFerlicot I think?) creates github.com/pharo-contributions/LDAP or something and adds me (a2b-alb) I'll push it > > >

March 8, 2019

Re: [Pharo-dev] Migrating XML support to github/PharoContributions/

by Albrecht Baur

On 08.03.19 13:51, ducasse wrote: >>> >>> In case someone wants to use it: I used Peters nice migration tool >>> for ... >>> http://smalltalkhub.com/#!/~PharoExtras/LDAP/ >>> ... and put it to: >>> https://github.com/a2b-alb/PharoExtras-LDAP >>> >>> I don't know if this is the right place or if you would rather have >>> it under ... >>> https://github.com/pharo-contributions/ >>> ... or somewhere else. >>> >> Thanks >> and it would be good. > > I do not know what is the best process to add something to > pharo-contributions. > May be we should fork your version and put it there and that people > continue to contribute > using PRs. > What do you think? We could fork my version as you described or we could do the migration again to have a clean push into an new repo e.g. github.com/pharo-contributions/LDAP (I can do this if you want - I have still the snippets here... I just wanted to have LDAP on a save place because I need it and decided not to place it in my private gitlab instance...) If someone (CyrilFerlicot I think?) creates github.com/pharo-contributions/LDAP or something and adds me (a2b-alb) I'll push it

March 8, 2019