- Pharo-dev - lists.pharo.org

[Pharo 8.0] Build #192: 3059-TestAsserterassertdescriptionresumable-should-be-refactored-to-use-guard-clause

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

There is a new Pharo build available! The status of the build #192 was: FAILURE. The Pull Request #3060 was integrated: "3059-TestAsserterassertdescriptionresumable-should-be-refactored-to-use-guard-clause" Pull request url: https://github.com/pharo-project/pharo/pull/3060 Issue Url: https://github.com/pharo-project/pharo/issues/3059 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 29, 2019

[Pharo 8.0] Build #191: 3044-tests-for-ComputedSlot

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

There is a new Pharo build available! The status of the build #191 was: SUCCESS. The Pull Request #3045 was integrated: "3044-tests-for-ComputedSlot" Pull request url: https://github.com/pharo-project/pharo/pull/3045 Issue Url: https://github.com/pharo-project/pharo/issues/3044 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 29, 2019

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

by Marcus Denker

I moved them all to the Project level https://github.com/orgs/pharo-project/projects <https://github.com/orgs/pharo-project/projects> >>> >>>> On 18 Mar 2019, at 08:27, Marcus Denker <marcus.denker(a)inria.fr <mailto:marcus.denker@inria.fr>> wrote: >>>> >>>> Hi, >>>> >>>> We enabled the GitHub âProjectsâ feature for the pharo repo: >>>> >>>> https://github.com/pharo-project/pharo/projects <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 <https://github.com/pharo-project/pharo/projects/11> >>>> -> "Pharo7 Backportingâ >>>> https://github.com/pharo-project/pharo/projects/12 <https://github.com/pharo-project/pharo/projects/12> >>>> -> "Simple Issues for Beginnersâ >>>> https://github.com/pharo-project/pharo/projects/14 <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 29, 2019

Re: [Pharo-dev] Variables in auto-completion

by Marcus Denker

The globals are in the list first... I think this can be fixed by moving the adding from #initializeSelectors to #addVariables (class NECUntypedModel). The whole NEC code is far too complexâ¦ we have some experiments for an AST based version, we should dig that out again. (I added the note to the issue) > On 28 Mar 2019, at 15:32, Tim Mackinnon <tim(a)testit.works> wrote: > > Yes - I noticed that too and raised a similar issue: https://github.com/pharo-project/pharo/issues/2855 > >> On 28 Mar 2019, at 10:48, Julien <julien.delplanque(a)inria.fr> wrote: >> >> >> >> --- >> Julien Delplanque >> Doctorant Ã lâUniversitÃ© de Lille >> http://juliendelplanque.be/phd.html >> Equipe Rmod, Inria >> BÃ¢timent B 40, Avenue Halley 59650 Villeneuve d'Ascq >> NumÃ©ro de tÃ©lÃ©phone: +333 59 35 86 40 >> >>> Le 28 mars 2019 Ã 11:15, Cyril Ferlicot <cyril.ferlicot(a)gmail.com> a Ã©crit : >>> >>> Hi, >>> >>> I remember that in old Pharo versions, the auto-completion added the >>> variables at the top of the completion list. Now they are at the >>> bottom under the classes. >>> >>> The original version worked better for me. >> >> I preferred previous version as well. >> >> Cheers, >> >> Julien >> >>> The current version really >>> annoys me since most of the time I would prefer to have a variables >>> completed. Is there a setting somewhere to get the old behavior back? >>> If not, does someone knowing the implementation of the auto-completion >>> knows where I could put a metalink to get the old behavior back for >>> me? >>> >>> -- >>> Cyril Ferlicot >>> https://ferlicot.fr >>> >> >

March 28, 2019

Re: [Pharo-dev] Variables in auto-completion

by Tim Mackinnon

Yes - I noticed that too and raised a similar issue: https://github.com/pharo-project/pharo/issues/2855 <https://github.com/pharo-project/pharo/issues/2855> > On 28 Mar 2019, at 10:48, Julien <julien.delplanque(a)inria.fr> wrote: > > > > --- > Julien Delplanque > Doctorant Ã lâUniversitÃ© de Lille > http://juliendelplanque.be/phd.html <http://juliendelplanque.be/phd.html> > Equipe Rmod, Inria > BÃ¢timent B 40, Avenue Halley 59650 Villeneuve d'Ascq > NumÃ©ro de tÃ©lÃ©phone: +333 59 35 86 40 > >> Le 28 mars 2019 Ã 11:15, Cyril Ferlicot <cyril.ferlicot(a)gmail.com <mailto:cyril.ferlicot@gmail.com>> a Ã©crit : >> >> Hi, >> >> I remember that in old Pharo versions, the auto-completion added the >> variables at the top of the completion list. Now they are at the >> bottom under the classes. >> >> The original version worked better for me. > > I preferred previous version as well. > > Cheers, > > Julien > >> The current version really >> annoys me since most of the time I would prefer to have a variables >> completed. Is there a setting somewhere to get the old behavior back? >> If not, does someone knowing the implementation of the auto-completion >> knows where I could put a metalink to get the old behavior back for >> me? >> >> -- >> Cyril Ferlicot >> https://ferlicot.fr <https://ferlicot.fr/> >> >

March 28, 2019

Re: [Pharo-dev] Variables in auto-completion

by Sven Van Caekenberghe

> On 28 Mar 2019, at 15:10, Alistair Grant <akgrant0710(a)gmail.com> wrote: > > On Thu, 28 Mar 2019 at 11:16, Cyril Ferlicot <cyril.ferlicot(a)gmail.com> wrote: >> >> Hi, >> >> I remember that in old Pharo versions, the auto-completion added the >> variables at the top of the completion list. Now they are at the >> bottom under the classes. >> >> The original version worked better for me. The current version really >> annoys me since most of the time I would prefer to have a variables >> completed. Is there a setting somewhere to get the old behavior back? >> If not, does someone knowing the implementation of the auto-completion >> knows where I could put a metalink to get the old behavior back for >> me? > > And me... :-) > > It's even more annoying because I can type the entire variable name > and then continue typing only to get the variable replaced with some > random class name. Haha, yes, I hate that too ... that is code completion that makes you less productive ;-) > Cheers, > Alistair

March 28, 2019

Re: [Pharo-dev] Variables in auto-completion

by Alistair Grant

On Thu, 28 Mar 2019 at 11:16, Cyril Ferlicot <cyril.ferlicot(a)gmail.com> wrote: > > Hi, > > I remember that in old Pharo versions, the auto-completion added the > variables at the top of the completion list. Now they are at the > bottom under the classes. > > The original version worked better for me. The current version really > annoys me since most of the time I would prefer to have a variables > completed. Is there a setting somewhere to get the old behavior back? > If not, does someone knowing the implementation of the auto-completion > knows where I could put a metalink to get the old behavior back for > me? And me... :-) It's even more annoying because I can type the entire variable name and then continue typing only to get the variable replaced with some random class name. Cheers, Alistair

March 28, 2019

[Pharo 8.0] Build #190: 3023-Some-cleanups-in-Slots

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

There is a new Pharo build available! The status of the build #190 was: SUCCESS. The Pull Request #3024 was integrated: "3023-Some-cleanups-in-Slots" Pull request url: https://github.com/pharo-project/pharo/pull/3024 Issue Url: https://github.com/pharo-project/pharo/issues/3023 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 28, 2019

Re: [Pharo-dev] Variables in auto-completion

by Julien

--- Julien Delplanque Doctorant Ã lâUniversitÃ© de Lille http://juliendelplanque.be/phd.html Equipe Rmod, Inria BÃ¢timent B 40, Avenue Halley 59650 Villeneuve d'Ascq NumÃ©ro de tÃ©lÃ©phone: +333 59 35 86 40 > Le 28 mars 2019 Ã 11:15, Cyril Ferlicot <cyril.ferlicot(a)gmail.com> a Ã©crit : > > Hi, > > I remember that in old Pharo versions, the auto-completion added the > variables at the top of the completion list. Now they are at the > bottom under the classes. > > The original version worked better for me. I preferred previous version as well. Cheers, Julien > The current version really > annoys me since most of the time I would prefer to have a variables > completed. Is there a setting somewhere to get the old behavior back? > If not, does someone knowing the implementation of the auto-completion > knows where I could put a metalink to get the old behavior back for > me? > > -- > Cyril Ferlicot > https://ferlicot.fr >

March 28, 2019

Variables in auto-completion

by Cyril Ferlicot

Hi, I remember that in old Pharo versions, the auto-completion added the variables at the top of the completion list. Now they are at the bottom under the classes. The original version worked better for me. The current version really annoys me since most of the time I would prefer to have a variables completed. Is there a setting somewhere to get the old behavior back? If not, does someone knowing the implementation of the auto-completion knows where I could put a metalink to get the old behavior back for me? -- Cyril Ferlicot https://ferlicot.fr

March 28, 2019