- Pharo-dev - lists.pharo.org

[Pharo 8.0] Build #654: SUCCESS

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

There is a new Pharo build available! The status of the build #654 was: SUCCESS. Could not extract further issue information from commit message: Point to pharo-project Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Aug. 21, 2019

[ANN] Pharo Newsletter August 2019

by Marcus Denker

The Pharo Newsletter August 2019 has been sent to subscribers one week ago. https://mailchi.mp/pharo/pharo-newsletter-august-2019 To get it as soon as it is released, please subscribe!

Aug. 21, 2019

Re: [Pharo-dev] Epicea Feedback

by ducasse

Are you in P8? Stef > On 18 Aug 2019, at 21:21, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > Not complaining at all and appreciate everyone's hard (mostly-unpaid) work, > but providing raw feedback in case it's helpful... > > - Browser awkward: filters disappear whenever left selection changed; no > multi-select of sessions, which led to a host of difficulties described > below. > - What is the heuristic to find API access points? Epicea package has no > comment, 'Browser' tag doesn't seem to have an XyzBrowser class, no > particular class in the 'Model' tag jumps out at me as an access point; as > above Browser about text not set. I finally bring up Morphic halos on the > browser and after flopping around, find subclasses of EpLogNode; I browse it > and find EpLogNodeGraphModel, which sounds interesting and turns out to be a > spec. I figure out how to list the log files, but not how to get the entries > - I was expecting a term like that and the relevant method (#log it turns > out) has no comment to indicate it's what I'm looking for. Now that I'm > starting to understand the project organization, back to the browser to > explore EpUnifiedBrowserModel. After a bit of poking around, I suspect > (correctly) that #log is what I'm after. > > Based on code I extract from the browsers and a bit of experimenting in GT, > I come up with the following seemingly very complex script: > > nodes := EpFileLogNode fromAllLogsIn: EpMonitor current sessionStore > baseLocator. > nodes do: [ :node | node populateReferencedNodesWith: nodes ]. > nodes flatCollect: [ :n | n log events select: [ :e | e affectedPackageName > beginsWith: 'Magritte' ] ] > > I now run into a series of problems because, although EpCodeChange declares > #affectedPackageName as an abstract method, not all events are > EpCodeChanges. I exclude EpUndos. Easy enough. Now I come to an > EpGenericRefactoring. This one is harder because > > p.s. <rant>Code names for internal projects seem extremely > counterproductive. Hiedra tells me absolutely nothing about functionality. > It might as well be called XyzWidgetThing</rant> > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html >

Aug. 21, 2019

Re: [Pharo-dev] Epicea Feedback

by ducasse

Thanks sean for the feedback Now pay attention that we cannot digest fast non PRs because we are super busy with P8 alpha. Can you open an issue so that martin can get an idea of what should be improved? Stef > On 18 Aug 2019, at 21:41, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > In case it helps anyone in the future, here is the "poor man's" browser I > hacked together to find all Magritte changes that needed to be rescued from > an image where those changes got out-of-sync so I couldn't use Iceberg: > > nodes := EpFileLogNode fromAllLogsIn: EpMonitor current sessionStore > baseLocator. > relevantNodes := nodes reject: [ :n | (n globalName endsWith: 'g3') or: [ n > globalName endsWith: 'ng' ] ]. > relevantNodes do: [ :node | node populateReferencedNodesWith: relevantNodes > ]. > entries := relevantNodes flatCollect: [ :n | n log entries ]. > filter := EpAndFilter withAll: { > EpImpactCodeChangeFilter new environment: self class environment; yourself. > EpPluggableFilter new condition: [ :e | > e content isCodeChange and: [ > e content affectedPackageName beginsWith: 'Magritte' ] ]. > EpPluggableFilter noTriggerFilter }. > filteredEntries := entries select: [ :e | filter accepts: e ]. > filteredEntries sort: [ :a :b | (a tagAt: #time) > (b tagAt: #time) ]. > groups := filteredEntries groupedBy: [ :e | (e content respondsTo: > #methodAffected) ifFalse: [ '?' ] ifTrue: [ e content methodAffected ] ]. > events := groups collect: [ :col | col first content ] as: > OrderedCollection. > events collect: [ :e | "{ e." DiffModel new > showOptions: true; > leftText: (e accept: EpOldStateVisitor new); > rightText: (e accept: EpNewStateVisitor new); > contextClass: e class; > buildWithSpec "}" ]. > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html >

Aug. 21, 2019

[Pharo 8.0] Build #653: 4080-remove-the-class-instance-var-in-NECController

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

There is a new Pharo build available! The status of the build #653 was: FAILURE. The Pull Request #4368 was integrated: "4080-remove-the-class-instance-var-in-NECController" Pull request url: https://github.com/pharo-project/pharo/pull/4368 Issue Url: https://github.com/pharo-project/pharo/issues/4080 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Aug. 21, 2019

[Pharo 8.0] Build #652: Traits-tests-should-work-with-slots-definitions

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

There is a new Pharo build available! The status of the build #652 was: FAILURE. The Pull Request #4375 was integrated: "Traits-tests-should-work-with-slots-definitions" Pull request url: https://github.com/pharo-project/pharo/pull/4375 Issue Url: https://github.com/pharo-project/pharo/issues/Traits Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Aug. 21, 2019

Code Completion: GSoC project summary

by Myroslava Romaniuk

Hi i just published a summary of my work on code completion during Google Summer of Code, for those who are interested. It's a 5 min overview of the progress that was made and some further plans (i do intend to continue working on it, as there's still cool things to be done). Here's a link to the blog post: https://medium.com/@myroslavarm/code-completion-in-pharo-gsoc-project-summa…, and the tweet: https://twitter.com/myroslavarm/status/1164059233073147905, if anyone feels like spreading the word. Thanks so much, Myroslava PS there's going to be a talk at ESUG Marcus and I are doing, please come!

Aug. 21, 2019

[Pharo 8.0] Build #651: Smaller Initial World Extent for osWindow World

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

There is a new Pharo build available! The status of the build #651 was: FAILURE. The Pull Request #4369 was integrated: "Smaller Initial World Extent for osWindow World" Pull request url: https://github.com/pharo-project/pharo/pull/4369 Issue Url: https://github.com/pharo-project/pharo/issues/smaller Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Aug. 20, 2019

[Pharo 8.0] Build #650: Add command for inline all senders of a method

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

There is a new Pharo build available! The status of the build #650 was: FAILURE. The Pull Request #4362 was integrated: "Add command for inline all senders of a method" Pull request url: https://github.com/pharo-project/pharo/pull/4362 Issue Url: https://github.com/pharo-project/pharo/issues/AddCommandInlineSenders Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Aug. 19, 2019

[Pharo 8.0] Build #649: 4335-DateAndTime-comments-could-take-advantage-of-executable-comments

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

There is a new Pharo build available! The status of the build #649 was: FAILURE. The Pull Request #4336 was integrated: "4335-DateAndTime-comments-could-take-advantage-of-executable-comments" Pull request url: https://github.com/pharo-project/pharo/pull/4336 Issue Url: https://github.com/pharo-project/pharo/issues/4335 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Aug. 19, 2019