- Pharo-dev - lists.pharo.org

extract method refactoring with assignment

by Eliot Miranda

Hi All, I tried an extract to method refactoring yesterday that failed. The method looked like | ... v1 v2 v3 | .... v1 := self m1. v2 := self m2. v3 := v3 collect: [:e| ...]. .... such that v1 and v2 were only used in the block, and the block was complex enough and did something useful e Pugh that I wanted to refactor as | ... v1 v2 v3 | .... v3 := self complexCollect: v3. .... complexCollect: a | v1 v2 | v1 := self m1. v2 := self m2. ^a collect: [:e| ...] So I was forced by the fact that assignment is written with the variable on the LHS to include "v3 := " in the selection to extract to method, even though my intent was for it not to be included. And of course the refactoring attempt fails precisely because the assignment /is/ included :-) Shouldn't this case be specially handled do that and trailing assignment is left behind in the refactored original method? Ifso, how would one go about it? Note that part of the prerequisite checks should also check that the variables v1 & v2 are not used elsewhere in the origins nail method and whether the refactoring is smart enough to remove them from the refactored origins nap is optional but definitely preferred. _,,,^..^,,,_ (phone)

Jan. 5, 2018

[Pharo 7.0-dev] Build #411: 20925 Super setUp need to be called in UnifiedFFI tests

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

There is a new Pharo build available! The status of the build #411 was: FAILURE. The Pull Request #645 was integrated: "20925 Super setUp need to be called in UnifiedFFI tests" Pull request url: https://github.com/pharo-project/pharo/pull/645 Issue Url: https://pharo.fogbugz.com/f/cases/20925 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Jan. 5, 2018

[Pharo 7.0-dev] Build #410: 20926-Super-setUp-need-to-be-called-in-MCWorkingCopyBrowserTest

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

There is a new Pharo build available! The status of the build #410 was: SUCCESS. The Pull Request #646 was integrated: "20926-Super-setUp-need-to-be-called-in-MCWorkingCopyBrowserTest" Pull request url: https://github.com/pharo-project/pharo/pull/646 Issue Url: https://pharo.fogbugz.com/f/cases/20926 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Jan. 5, 2018

[Pharo 7.0-dev] Build #409: 20924 Fix unused var tutorial in TutorialPlayerTestWithMockTutorial>>setUp

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

There is a new Pharo build available! The status of the build #409 was: SUCCESS. The Pull Request #644 was integrated: "20924 Fix unused var tutorial in TutorialPlayerTestWithMockTutorial>>setUp" Pull request url: https://github.com/pharo-project/pharo/pull/644 Issue Url: https://pharo.fogbugz.com/f/cases/20924 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Jan. 5, 2018

Re: [Pharo-dev] gtInspector+FastTable enhancement requests

by Ben Coman

On 5 January 2018 at 15:38, Ben Coman <btc(a)openinworld.com> wrote: > > > On 10 December 2017 at 16:51, Ben Coman <btc(a)openinworld.com> wrote: > >> Feedback for GT'ers... >> >> I'm probably ab-using FastTable support in gtInspector, >> but as a quick hack during initial prototyping it was *very* nice >> to be able review retrieved data as a table of instances >> with a column per instance variable. >> >> Some enhancements that would make this even better... >> 1. Horizontal scroll bar - There are columns past the right margin that I >> can't get to for lack of one. >> > > I'm having a go at this. The easy part adding the scrollbar morph is done > and before proceeding further I'm seeking advice on the recommended > approach > to translating the columns. > > I've uploaded Morphic-Widgets-FastTable-BenComan.223 to Pharo6InBox. > Could someone familiar with FastTable internals review this on top of 60528 > and advise the next step I should take. > I should have mentioned, run... FTExample>>exampleTableHorizontalScroll to see demo of what I've done so far. btw, to make it safer to trial this horizontal scroll bar UI code all modifications are guarded by... trialHSB ifNil: [ ] ifNotNil: [] cheers -ben

Jan. 5, 2018

Re: [Pharo-dev] gtInspector+FastTable enhancement requests

by Ben Coman

On 10 December 2017 at 16:51, Ben Coman <btc(a)openinworld.com> wrote: > Feedback for GT'ers... > > I'm probably ab-using FastTable support in gtInspector, > but as a quick hack during initial prototyping it was *very* nice > to be able review retrieved data as a table of instances > with a column per instance variable. > > Some enhancements that would make this even better... > 1. Horizontal scroll bar - There are columns past the right margin that I > can't get to for lack of one. > I'm having a go at this. The easy part adding the scrollbar morph is done and before proceeding further I'm seeking advice on the recommended approach to translating the columns. For what I've done so far, I was going to submit for review via the latest Pharo 7 Contribution process, but I hit a blocker... http://forum.world.st/IMPORTANT-PHARO-CONTRIBUTION-PROCESS-UPDATED-PLEASE-R… so I've uploaded Morphic-Widgets-FastTable-BenComan.223 to Pharo6InBox. Could someone familiar with FastTable internals review this on top of 60528 and advise the next step I should take. cheers -ben P.S. I expect to integrate this in Pharo 7 rather than Pharo 6, but this moment its easier for me to ask for help this way.

Jan. 5, 2018

Re: [Pharo-dev] [IMPORTANT] PHARO CONTRIBUTION PROCESS UPDATED! PLEASE READ!

by Ben Coman

On 14 December 2017 at 20:19, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > Hi! > > Iâm working on simplifying the contribution process, after collecting > opinions/experiences last couple of months. > As you know, Pharo contribution process is still WIP and we aim to have it > as smooth as possible for Pharo 7.0 release. Now, after observe the idea of > the âsystem repositoriesâ was a bad idea because it introduced extra and > non standard âpathâ to contribution, I managed to remove that to > reestablish âthe regular wayâ: you will now need to add pharo repository > just as any other repository you add, by cloning or adding local repository. > > I took Guilleâs doc and moved it to pharo project (it does not has sense > to have it living in a contributorâs repository when is so important). You > can find it here: > > https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo > > This document is also updated to reveal this new process, please read it. > > How to update your startup scripts? > Some people has added startup scripts to easy the first part of > contribution. Instead enabling system repositories, etc. you now need to > replace that with this: > > (IceRepositoryCreator new > location: '/path/to/pharo-project/pharo' asFileReference; > subdirectory: 'src'; > createRepository) > register > > PLEASE, PLEASE, PLEASEâ¦ take a moment to read and try the document. Is > very important that document reflects new process and works reliable in > different scenarios (I validated it on macOS and Windows, and assumed it > worked fine on linux but you knowâ¦ bad assumptions is the base of failure > ;) ) > > Iâm eager to hear your feedback and continue enhancing the process. > > (yes, Stef, I know UI is still cumbersomeâ¦ Iâm working on that :) ) > > cheers! > Esteban > Using https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo with my pharo branch "22 commits behind pharo-project:master" https://github.com/bencoman/pharo/tree/master >From PharoLauncher, I created fresh latest image from Pharo-7.0.0-alpha.build.408.sha.5369e34.arch.64bit (btw, download took about 30 seconds which was reasonably good) Opened image WorldMenu > Iceberg Iceberg > Clone Repository Remote URL = git@github.com:bencoman/pharo.git Local Directory (default) = /home/ben/Pharo/images/FastTable-Pharo-7.0.0-alpha.build.402.sha.d5d4c99.arch.64bit-01/pharo-local/iceberg Code subdirectory = src <Create Repository> A bit disconcerting that for about 1.5 minutes the UI is frozen, but eventually "pharo" entry appears in IceBerg with... Name = *pharo Current branch = master Loaded version = fc92bbe (7 July 2017) Status = uncommitted changes Right-clicked on *pharo > Synchronise repository up popped dialog "Synchronising" on tab [Commit your changes] with about 800 changes with all items ticked. (btw, I clicked <Refresh Tree> all the changes are unticked, and only the three toplevel items GT-Spotter, Kernel & Reflectivity are ticked. Is that ideal? What is the typical use case of that button. Anyway, I close the dialog, and again right-click on *pharo > Synchronise repository) (btw, reviewing change here is nice.) A bit disconcerting that buttons <Commit onto master> and <Commit and push onto master> are both disabled so there is no action I can do from this default, so I proceed to [Push] tab. I'm feel unsure whether there should be some item listed under "New local commits to be published" (there are none) but pushing <Publish all> seems the only thing possible, so I do that. That seems to complete after 10 seconds, but still status = "Uncommitted changes" in the main Iceberg window. Opening a new IceBerg window shows the same thing. So what more do I need to do to get my Pharo repo "Up to date" ? cheers -ben

Jan. 5, 2018

Re: [Pharo-dev] New Year Wishlist (2018) ?

by Ben Coman

On 24 December 2017 at 00:58, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > Hi everybody, > > This looks like a good moment of the year to ask all of you what would you > want to see in Pharo next year. > Features, improvements, radical changes, etcâ¦. whatever you want. > > Of course, this list will not be a roadmap and it does not means we will > implement all of it (as always, time drives our possibilities), but is a > good moment for us a a community to check where we are and where we wan to > go next :) > > So, letâs those wishes come! Small enhancement that arises as I'm trying to design a Morph, Initially forgetting which corner of the screen is 0@0, raises the idea that in the GTInspector Morph tab, showing the coordinates of the mouse as it tracks over the morph would be useful. Maybe this would be less useful for Morphic using absolute co-ordinates, but good for Bloc using relative co-ordinates (IIUC). cheers -ben

Jan. 5, 2018

Soup Bug? Pre Tags Should Be Nestable

by Sean P. DeNigris

I did some research and don't see any restriction on nested pre tags, yet Soup includes <pre> in "NonNestableBlockTagsForHtml". This causes the following to be parsed as two sibling <pre> tags: <pre> Hi there <pre> This act shall take effect immediately. </pre> </pre> Moving <pre> from NonNestableBlockTagsForHtml to NestableBlockTagsForHtml seems to be The Right Thing To Do. Any objection (I'm certainly not an HTML expert). If not, I'll commit to my GH fork and feel free to merge back to StHub or wherever. ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Jan. 4, 2018

[MoreVMs'18] Call for Contributions: 2nd Workshop on Modern Language Runtimes, Ecosystems, and VMs at <Programming> 2018

by Stefan Marr

============================================================================ Call for Papers: MoreVMs'18 2nd Workshop on Modern Language Runtimes, and Ecosystems Co-located with <Programming>'18 April 9th, 2018, Nice, France https://2018.programming-conference.org/track/MoreVMs-2018 ============================================================================ The MoreVMs'18 workshop aims to bring together industrial and academic programmers to discuss the design, implementation, and usage of modern languages and runtimes. This includes aspects such as reuse of language runtimes, modular implementation, language design and compilation strategies. The workshop aims to enable a diverse discussion on how languages and runtimes are currently being utilized, and where they need to improve further. We welcome presentation proposals in the form of extended abstracts discussing experiences, work-in-progress, as well as future visions, from either an academic or industrial perspective. Relevant topics include, but are definitely not limited to, the following: - Extensible VM design (compiler- or interpreter-based VMs) - Reusable components (e.g. interpreters, garbage collectors, ...) - Static and dynamic compilation techniques - Techniques for targeting high-level languages such as JavaScript - Interoperability between languages - Tooling support (e.g. debugging, profiling, etc.) - Programming language development environments - Case studies of existing language implementation approaches - Language implementation challenges and trade-offs - Surveys and usage reports to understand usage in the wild - Ideas for more predictable performance - Ideas for how VMs could take advantage of new hardware features - Ideas for how we should build languages in the future Workshop Format and Submissions ------------------------------- Submissions should use the ACM Conference acmart Format with the âsigconfâ option with a font size of 10 point and the font family Times New Roman. All submissions should be in PDF format. If you use LaTeX or Word, please use the provided ACM acmart templates. Otherwise, please follow the ACM author instructions. https://www.acm.org/publications/proceedings-template If you are formatting your paper using LaTeX, you will need to set the 10pt option in the \documentclass command. If you are formatting your paper using Word, you may wish to use the provided Word template that supports this font size. Please include page numbers in your submission for review using the LaTeX command \settopmatter{printfolios=true} (see examples in template). Please also ensure that your submission is legible when printed on a black and white printer. In particular, please check that colors remain distinct and font sizes are legible. Submission Site: https://easychair.org/conferences/?conf=morevms18 Important Dates --------------- Extended abstract submission: 2018-01-26 Author notification: 2018-02-23 Workshop: 2018-04-09 All deadlines are Anywhere on Earth (AoE), i.e. GMT/UTC-12:00 hour. Program Committee ----------------- ClÃ©ment Bera, Inria Lille Nord Europe, France Maxime Chevalier-Boisvert, University of Montreal, Canada SÃ©bastien Doeraene, EPFL, Switzerland Johan Fabry, Raincode Labs, Belgium Juliana Franco, Imperial College London, United Kingdom Tobias Grosser, ETH Zurich, Switzerland Ben L. Titzer, Google, Germany Niko Matsakis, Mozilla Research, United States Armin Rigo, PyPy, Switzerland Maoni Stephens, Microsoft, United States GaÃ«l Thomas, Telecom SudParis, France Mario Wolczko, Oracle Labs, United States Workshop Organizers ------------------- Edd Barrett, King's College London, United Kingdom Adam Welc, Uber Technologies, United States Stefan Marr, University of Kent, United Kingdom

Jan. 4, 2018