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

Re: [Pharo-dev] Issue Tracker: enabled Projects (Boards)

by Marcus Denker

Hi, it seems that the account / access model of GitHub forces us to move the boards to the organisation level (where we can have a user group with write access for the boards). This means I will move them slowly to https://github.com/orgs/pharo-project/projects <https://github.com/orgs/pharo-project/projects> So lets treat all this as a testâ¦ as soon as it is really working I will send another mail. > On 18 Mar 2019, at 08:27, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Hi, > > We enabled the GitHub âProjectsâ feature for the pharo repo: > > https://github.com/pharo-project/pharo/projects > > > The idea is that one can add as many âKanbanâ style boards as one wants. > issues and pull requests can be added, as well as simple cards that are not yet issues. > > This is quite nice as an issue tracker gets very confusing and overwhelming as soon as there > are >500 issues. > > With these boards, we can create âviewsâ on this sea of issues. > > I created for now: > > -> some board related to specific parts of the system (e.g. Traits or Reflectivity) > example: https://github.com/pharo-project/pharo/projects/11 > -> "Pharo7 Backportingâ > https://github.com/pharo-project/pharo/projects/12 > -> "Simple Issues for Beginnersâ > https://github.com/pharo-project/pharo/projects/14 > Here the feature to be able to put things that are not yet issue tracker entries seems very useful > > > I think this can be quite niceâ¦ we should add more Projects as soon as we find that they make sense > and should move issues there. > > Marcus

March 19, 2019

Re: [Pharo-dev] About a better filedialog

by Guillermo Polito

YES! On Mon, Mar 18, 2019 at 11:13 PM ducasse <stepharo(a)netcourrier.com> wrote: > Yes I had to rename ComposableModel into ComposablePresenter so this is > probably that > > On 18 Mar 2019, at 23:09, Peter Uhnak <i.uhnak(a)gmail.com> wrote: > > Thanks Stef! > > The build is failing for Pharo 6.1 for some reason (I can't reproduce it > locally), but I can look at that during the weekend... > > Peter > > On Mon, Mar 18, 2019 at 9:23 PM ducasse <stepharo(a)netcourrier.com> wrote: > >> Alex >> >> Have a look at the one I propose and play with it. >> Let me know what you think. >> >> Stef >> >> On 18 Mar 2019, at 21:20, Alexandre Bergel <alexandre.bergel(a)me.com> >> wrote: >> >> >> *From: *Alexandre Bergel <alexandre.bergel(a)me.com> >> *Subject: **Re: [Pharo-dev] About a better filedialog* >> *Date: *18 March 2019 at 21:20:35 CET >> *To: *Pharo Development List <pharo-dev(a)lists.pharo.org> >> >> >> I do not have time to personally work on this. But yes, having a better >> file dialog would be fantastic >> >> Alexandre >> >> On Mar 18, 2019, at 4:31 PM, ducasse <stepharo(a)netcourrier.com> wrote: >> >> Hi guys >> >> I did a pass (ported to P7, tonel, some little fixes) on the file-dialog >> developed by Peter Uhnak and I think that it would be good to propose it by >> default in the image. >> what do you think? >> >> https://github.com/Ducasse/file-dialog >> >> I would also like that the filedialog remembers the last list of visited >> directory. (I will see if I can add this). >> When Spec2 is out I would like to port it to Spec2. >> >> Does anybody want to help? Because it would be super nice and Iâm full >> with cleaning textEditor and pluggableTextMorph. >> >> Stef >> >> >> >> >> >> >> >> >> > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

March 19, 2019

[Pharo 8.0] Build #153: 2879-removeInstVarNamed-on-MetaClass-needs-to-use-removeSlot-like-the-implementation-on-Class

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

There is a new Pharo build available! The status of the build #153 was: FAILURE. The Pull Request #2890 was integrated: "2879-removeInstVarNamed-on-MetaClass-needs-to-use-removeSlot-like-the-implementation-on-Class" Pull request url: https://github.com/pharo-project/pharo/pull/2890 Issue Url: https://pharo.fogbugz.com/f/cases/2879 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 19, 2019

[Pharo 8.0] Build #152: 2891-fix-whichSelectorsRead-and-whichSelectorsStoreInto-for-Slots

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

There is a new Pharo build available! The status of the build #152 was: SUCCESS. The Pull Request #2894 was integrated: "2891-fix-whichSelectorsRead-and-whichSelectorsStoreInto-for-Slots" Pull request url: https://github.com/pharo-project/pharo/pull/2894 Issue Url: https://pharo.fogbugz.com/f/cases/2891 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 19, 2019

[Pharo 8.0] Build #151: 2852-CodeCompletion-should-not-be-managed-via-common-tools-but-via-a-TextArea-registration

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

There is a new Pharo build available! The status of the build #151 was: SUCCESS. The Pull Request #2857 was integrated: "2852-CodeCompletion-should-not-be-managed-via-common-tools-but-via-a-TextArea-registration" Pull request url: https://github.com/pharo-project/pharo/pull/2857 Issue Url: https://pharo.fogbugz.com/f/cases/2852 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 18, 2019

Re: [Pharo-dev] About a better filedialog

by ducasse

Yes I had to rename ComposableModel into ComposablePresenter so this is probably that > On 18 Mar 2019, at 23:09, Peter Uhnak <i.uhnak(a)gmail.com> wrote: > > Thanks Stef! > > The build is failing for Pharo 6.1 for some reason (I can't reproduce it locally), but I can look at that during the weekend... > > Peter > > On Mon, Mar 18, 2019 at 9:23 PM ducasse <stepharo(a)netcourrier.com <mailto:stepharo@netcourrier.com>> wrote: > Alex > > Have a look at the one I propose and play with it. > Let me know what you think. > > Stef > >> On 18 Mar 2019, at 21:20, Alexandre Bergel <alexandre.bergel(a)me.com <mailto:alexandre.bergel@me.com>> wrote: >> >> >> From: Alexandre Bergel <alexandre.bergel(a)me.com <mailto:alexandre.bergel@me.com>> >> Subject: Re: [Pharo-dev] About a better filedialog >> Date: 18 March 2019 at 21:20:35 CET >> To: Pharo Development List <pharo-dev(a)lists.pharo.org <mailto:pharo-dev@lists.pharo.org>> >> >> >> I do not have time to personally work on this. But yes, having a better file dialog would be fantastic >> >> Alexandre >> >>> On Mar 18, 2019, at 4:31 PM, ducasse <stepharo(a)netcourrier.com <mailto:stepharo@netcourrier.com>> wrote: >>> >>> Hi guys >>> >>> I did a pass (ported to P7, tonel, some little fixes) on the file-dialog developed by Peter Uhnak and I think that it would be good to propose it by default in the image. >>> what do you think? >>> >>> https://github.com/Ducasse/file-dialog <https://github.com/Ducasse/file-dialog> >>> >>> I would also like that the filedialog remembers the last list of visited directory. (I will see if I can add this). >>> When Spec2 is out I would like to port it to Spec2. >>> >>> Does anybody want to help? Because it would be super nice and Iâm full with cleaning textEditor and pluggableTextMorph. >>> >>> Stef >>> >>> >>> >> >> >> >> >

March 18, 2019

Re: [Pharo-dev] About a better filedialog

by Peter Uhnak

Thanks Stef! The build is failing for Pharo 6.1 for some reason (I can't reproduce it locally), but I can look at that during the weekend... Peter On Mon, Mar 18, 2019 at 9:23 PM ducasse <stepharo(a)netcourrier.com> wrote: > Alex > > Have a look at the one I propose and play with it. > Let me know what you think. > > Stef > > On 18 Mar 2019, at 21:20, Alexandre Bergel <alexandre.bergel(a)me.com> > wrote: > > > *From: *Alexandre Bergel <alexandre.bergel(a)me.com> > *Subject: **Re: [Pharo-dev] About a better filedialog* > *Date: *18 March 2019 at 21:20:35 CET > *To: *Pharo Development List <pharo-dev(a)lists.pharo.org> > > > I do not have time to personally work on this. But yes, having a better > file dialog would be fantastic > > Alexandre > > On Mar 18, 2019, at 4:31 PM, ducasse <stepharo(a)netcourrier.com> wrote: > > Hi guys > > I did a pass (ported to P7, tonel, some little fixes) on the file-dialog > developed by Peter Uhnak and I think that it would be good to propose it by > default in the image. > what do you think? > > https://github.com/Ducasse/file-dialog > > I would also like that the filedialog remembers the last list of visited > directory. (I will see if I can add this). > When Spec2 is out I would like to port it to Spec2. > > Does anybody want to help? Because it would be super nice and Iâm full > with cleaning textEditor and pluggableTextMorph. > > Stef > > > > > > > > >

March 18, 2019

Re: [Pharo-dev] Font resources not flushed on session

by Sven Van Caekenberghe

Seriously, how many years now have we these errors with the FT plugin, it is really terrible. > On 18 Mar 2019, at 21:30, ducasse <stepharo(a)netcourrier.com> wrote: > > Hi > > I tried to open an image saved by damien on Mojave. I got the following fatal error. > After fighting I could by chance disable and reenable the freetype pluggin and it worked. > I think that the font cache was not flushed on something like that. > > Stef > > <Screen Shot 2019-03-18 at 21.22.56.png>

March 18, 2019

Re: [Pharo-dev] Esteban's ChangeLog week of 11 March 2019

by Esteban Lorenzano

Hi, > On 18 Mar 2019, at 20:27, ducasse <stepharo(a)netcourrier.com> wrote: > > > >> On 18 Mar 2019, at 18:00, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> >> Hi Sean, >> >> This is how the menus are done ultimately, not âthe wayâ of doing it. >> In general, you will do menus using something like Commander: you define commands, then you dynamically build the menus based on a context given (this is how Pharo itself will doit). >> - Or you build your own command library and build menus your way (see this experiment: https://github.com/estebanlm/Lieutenant/tree/try-superlight-version and its clases LtMenuBarBuilder, LtContextMenuBuilder). >> - Or you collect the items (MenuItemPresenter) from a pragma and you sort them some way. >> >> You are free to do as you want, but at the end, it has to have the structure described in the log :) > > > I think that Spec should propose a nice default way. We will have a default way. But everybody can do whatever they want after that :) > And as Sean mentioned it, Iâm not unable to nicely extend Epicea menu so Iâm hacking inside and this is not good. Because it was not designed to be extensible (as nothing was before we started to pay attention to that) Esteban >> >> One important things I didnât remarked, is that in Spec, all menu accessors are âvaluablesâ. Means that for example ListPresenter>>contextMenu: will receive anything that understands value and it will be executed on demand: >> >> self newList >> contextMenu: [ self collectMyContextMenu ]; >> etcâ¦. >> >> Will work as expected. >> (I hope this helps to understand the design better). >> >> Cheers! >> Esteban >> >> >>> On 18 Mar 2019, at 17:06, Sean P. DeNigris <sean(a)clipperadams.com> wrote: >>> >>> EstebanLM wrote >>>> addGroup: [ :group | >>>> group >>>> addItem: [ :item | item name: 'Something 1'; action: [ >>>> "doSomething"] ]; >>> >>> How would one extend a menu with this approach e.g. add an item to the group >>> from elsewhere (outside the block)? Is it even possible? >>> >>> >>> >>> ----- >>> Cheers, >>> Sean >>> -- >>> Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html >>> >> >> > > >

March 18, 2019

Font resources not flushed on session

by ducasse

Hi I tried to open an image saved by damien on Mojave. I got the following fatal error. After fighting I could by chance disable and reenable the freetype pluggin and it worked. I think that the font cache was not flushed on something like that. Stef

March 18, 2019