- Pharo-dev - lists.pharo.org

[Pharo 8.0] Build #127: 2740-do-not-zap-method-dict-when-making-classes-obsolete
by ci-pharo-ci-jenkins2＠inria.fr March 11, 2019

March 11, 2019

There is a new Pharo build available! The status of the build #127 was: SUCCESS. The Pull Request #2741 was integrated: "2740-do-not-zap-method-dict-when-making-classes-obsolete" Pull request url: https://github.com/pharo-project/pharo/pull/2741 Issue Url: https://pharo.fogbugz.com/f/cases/2740 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Esteban's ChangeLog week of 4 March 2019
by estebanlm＠gmail.com March 11, 2019

March 11, 2019

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

3 2

[Pharo 8.0] Build #126: 2769-add-Slot-example-write-once-slot
by ci-pharo-ci-jenkins2＠inria.fr March 11, 2019

March 11, 2019

There is a new Pharo build available! The status of the build #126 was: SUCCESS. The Pull Request #2770 was integrated: "2769-add-Slot-example-write-once-slot" Pull request url: https://github.com/pharo-project/pharo/pull/2770 Issue Url: https://pharo.fogbugz.com/f/cases/2769 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #125: 2790-standalone-Tool-Registry
by ci-pharo-ci-jenkins2＠inria.fr March 11, 2019

March 11, 2019

There is a new Pharo build available! The status of the build #125 was: SUCCESS. The Pull Request #2787 was integrated: "2790-standalone-Tool-Registry" Pull request url: https://github.com/pharo-project/pharo/pull/2787 Issue Url: https://pharo.fogbugz.com/f/cases/2786 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #124: Revert "2759-Spec-Deprecated-should-be-removed-from-Pharo-8"
by ci-pharo-ci-jenkins2＠inria.fr March 11, 2019

March 11, 2019

There is a new Pharo build available! The status of the build #124 was: SUCCESS. The Pull Request #2788 was integrated: "Revert "2759-Spec-Deprecated-should-be-removed-from-Pharo-8"" Pull request url: https://github.com/pharo-project/pharo/pull/2788 Issue Url: https://pharo.fogbugz.com/f/cases/revert Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #123: Revert "Adds a new exception for a missing class error (ClassNotUnderstood) andâ¦"
by ci-pharo-ci-jenkins2＠inria.fr March 10, 2019

March 10, 2019

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…

1 0

[Pharo 8.0] Build #122: Adds a new exception for a missing class error (ClassNotUnderstood) andâ¦
by ci-pharo-ci-jenkins2＠inria.fr March 10, 2019

March 10, 2019

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…

1 0

DrTests and enhancing testing experience in Pharo
by Dayne Lorena Guerra Calle March 8, 2019

March 8, 2019

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

2 1

Re: [Pharo-dev] Migrating XML support to github/PharoContributions/
by ducasse March 8, 2019

March 8, 2019

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 > > >

1 0

Re: [Pharo-dev] Migrating XML support to github/PharoContributions/
by ducasse March 8, 2019

March 8, 2019

> On 8 Mar 2019, at 11:08, 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 11:08:44 CET > To: pharo-dev(a)lists.pharo.org > > > I thought xml support is already migrated by Sven? > > https://github.com/svenvc/XML-Support-Pharo <https://github.com/svenvc/XML-Support-Pharo> > > Or do I mix something up here? > > ------------- > Something else: > 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 started trying to do the same migration process for ... > http://www.smalltalkhub.com/#!/~Pier/Pier3 <http://www.smalltalkhub.com/#!/~Pier/Pier3> > ... but I failed on errors loading older mcz files: > > "instance of ByteString did not understand #peek" > on: MCMczReader >> contentsForMember: > (ZnInvalidUTF8: Illegal leading byte for utf-8 encoding) > > Is this wrong encoding or corrupted files > > How to treat these files ? -> Is just ignoring this majority of failing mcz files via migration ignoredFileNames: #() > ok ? > I wonder if the MCMCZ was not about the delta between two commits but may be Iâm wrong. BTW this is great to see someone pushing pier. I would like to see how a new version of pillar can be pushed back into pier. > > ------------- > As a workaround I then left the history versions behind and took only the newest mcz files. But I am not sure which package version "is in harnmony" with the other ones... ;-) > -> While trying out which versions of the ConfigurationOfPier3 load in a p7 image only the #stable one loaded without problems. The newer ones didnât. > Seriously for Pier I would first focus on making it work with the latest version and we can always say that the historuy is in another repo. > > I did this by first loading as much pier3 dependencies (seaside, magritte, ...) from the new github repos. So I can then say ... > onConflict: [ :e | e useLoaded ]; > ... when loading pier3 from smaltalkhub. > > Can someone who knows pier3 better than me, give me a hint on which package versions combinations are the ones to go with ? > -> Is to just start with the newest mcz files the way to go? Or should I use the #stable ConfigurationOfPier3 ? > Use the configuration because I have no clue. Esteban was extending pier in the past. > > best, > Albrecht > On 08.03.19 08:10, Peter Uhnak wrote: >> > It has the full history - but no reference to your username (because I guess Peter did not know your github name/mail address). >> >> That's not the case, maybe you are confused by the latest handful of commits that I made directly. >> The rest is migrated with monty's mail; you can see "monty authored and peteruhnak committed", or look at the patch of any commit https://github.com/pharo-contributions/OrderPreservingDictionary/commit/e41… <https://github.com/pharo-contributions/OrderPreservingDictionary/commit/e41…> >> >> Associating the mail with a github account should be enough. >> >> Peter >> >> On Thu, Mar 7, 2019 at 11:06 PM Torsten Bergmann <astares(a)gmx.de <mailto:astares@gmx.de>> wrote: >> Stef wrote: >> > > Note that Peter seem to have converted already one of the projects the XMLParser is dependent on: "OrderPreservingDictionary" >> > > which lives at: https://github.com/pharo-contributions/OrderPreservingDictionary <https://github.com/pharo-contributions/OrderPreservingDictionary> >> > > It has the full history - but no reference to your username (because I guess Peter did not know your github name/mail address). >> > >> > Ah cool I was about to do it. >> >> From the history I guess Peter did it. >> >> But we should redo it once we know Monty's github user account name to have him linked in the >> history of commits and honour his authorship. >> >> @Monty: can you tell us your github account user name/ github home? >> >> Thx >> T. > >

2 2