- Pharo-dev - lists.pharo.org

ECOOP'20 Berlin - Call for Papers
by Fabio Niephaus Nov. 29, 2019

Nov. 29, 2019

============================================================ The 34th Edition of ECOOP Call for Papers 13th-17th July 2020 Berlin, Germany https://2020.ecoop.org/ ============================================================ ECOOP is a conference about programming. Originally its primary focus was on object orientation, but now it looks at a much broader range of programming topics. Areas of interest include, at least, the design, implementation, optimization, analysis, and theory of programs, programming languages, and programming environments. It solicits both innovative and creative solutions to real problems as well as evaluations of existing solutionsâevaluations that provide new insights. It also encourages the submission of reproduction studies. ECOOP 2020 solicits high-quality submissions describing original, unpublished results. The program committee will evaluate the technical contribution of each submission as well as its general relevance and accessibility to the ECOOP audience according to the following criteria: - Originality. Papers must present new ideas and place them appropriately within the context established by previous research in the field. - Significance. The results in the paper must have the potential to add significantly to the state of the art or practice. - Evidence. The paper must present evidence supporting its claims. Examples of evidence include implemented systems, experimental results, statistical analyses, case studies, formalizations, and proofs. - Clarity. The paper must present its contributions and results clearly. On submission, authors will be asked to identify their paper with one of the following categories: - Research Paper. This is the most traditional category and solicits high quality research papers that demonstrate advances in the field. (As an alternative to being published in the conference proceedings, authors may wish to submit research papers to be considered for publication in ACM TOPLAS or Science of Computer Programming.) - Tool Insights Paper. These submissions focus on the practical details of the design and implementation of PL toolsâdetails that are often omitted from regular research papers, despite being fascinating and worthy of communication. A strong Tool Insights Paper should communicate engineering experience and insights that are likely to be useful to other members of the PL community, who may face similar problems in future. Examples of issues that Tool Insights Papers might focus on include, but are not limited to: performance, reliability, portability, inter-tool integration, infrastructure re-use, evaluation issues, theory/practice gaps, precision/efficiency, and soundness/efficiency trade-offs. - Reproduction Study. A Reproduction Study is an empirical evaluation. It reconstructs an already published experiment but in a different context (for example, using a different virtual machine or platform, or in a different class of applications) in order to validate or refute important results of earlier work. A good Reproduction Study includes thorough empirical evaluation as well as a detailed comparison with the previous results, providing reasons for possible disagreements. (A thoroughly-conducted Reproduction Study that perfectly replicates an existing experiment and reaches the same conclusions will be regarded as significant, so long as said experiment is significant enough to be worthy of reproduction.) - Experience Report. Such reports focus on noteworthy applications of known PL techniques, tools, and ideas in interesting domains and by other communities. Examples include, but are not limited to, applications of PL techniques in industry, open source, education, and other academic disciplines. We welcome reports on successful applications of PL ideas and reports that shed light on limitations and problems that may provide inspiration for future research. - Pearl. This category solicits articles that explain a known idea in a new and elegant way, to the benefit of the PL community. A Pearl may well be shorter than a regular research paper, but there is no hard requirement on this. - Brave New Idea. The Brave New Idea category solicits forward-looking articles on ideas in the field of PL that may take some time to substantiate, but for which early communication to the community is likely to be of benefit. For this category we welcome papers that are particularly conceptually novel or unconventional and that as a result may be harder to back up by traditional evaluation methods. A Brave New Idea paper may well be shorter than a regular research paper, but there is no requirement for it to be so. Paper Submission ================ Only papers that have not been published and are not under review for publication elsewhere may be submitted. Double submissions will be rejected without review. If major parts of an ECOOP submission have appeared elsewhere in any form, authors are required to notify the ECOOP program chair and explain the overlap and relationship. Authors are also required to inform the program chair about closely related work submitted to another conference while the ECOOP submission is under review. Papers must be no longer than 25 pages, excluding references. See below for information about appendices. Authors will not be penalized for papers that are shorter than the page limit. Submissions will be carried out electronically via the conference website [1]. ECOOP Proceedings are published by Dagstuhl LIPIcs. Papers must be written in English and follow the Dagstuhl LIPIcs LaTeX-style template [2]. Authors retain ownership of their content. Note: Submitted papers do not need to include the ACM classification or keywords. Also, please DO NOT put your name in either the \author or \Copyright macro, in order to maintain anonymity for double-blind reviewing (see below). Anonymity ========= ECOOP will use light double-blind reviewing: authorsâ identities are withheld until a reviewer submits his or her review (as usual, reviews are anonymous). To facilitate this, submitted papers must adhere to two rules: - Author names and institutions must be omitted. - References to authorsâ own other work should be in the third person (for example, not âWe build on our previous workâ¦â but rather âWe build on the work ofâ¦â). When in doubt, contact the Program Chair. Additional Material =================== Clearly marked additional appendices containing analyses, statistics, supporting proofs, etc. of possible value to reviewers but not published in the final publication, may be included beyond the page limit. The submission system provides an option to submit supplementary material; for example, a technical report including proofs, or web pages and repositories that cannot easily be anonymized. This supplementary material will be made available to reviewers after the initial reviews have been completed, when author names are revealed. Reviewers are under no obligation to examine such appendices and supplementary material. Therefore, the paper must be a stand-alone document - the appendices and supplementary material are a way of providing useful information that cannot fit in the page limit; they are not a means to extend the page limit. Authors of papers that have been submitted but not accepted by previous conferences may optionally submit a Note to Reviewers. The Note to Reviewers should provide the following information: - the identity of the previous venue(s) (for example, ESOP 2020, â¹Programmingâº 2020, POPL 2020, OOPSLA 2019) - a list the major issues identified by the reviews at those venues - a description of the changes made to the paper in response to those reviews These notes will be made available to reviewers after their initial reviews have been completed and author names have been revealed. Response Period =============== Authors will be given a three-day period to read and respond to the reviews of their papers before the program committee meeting. Responses have no formal length limit, but concision is likely to be effective. Artifact Evaluation =================== To reward the creation of artifacts and support replication of experiments, authors of accepted research papers may submit artifacts (such as tools, data, models, or videos) to be evaluated by an Artifact Evaluation Committee. Artifacts that pass muster will be recognized officially. Important Dates =============== - Paper submission: 10 January 2020 (Fri) - Author response: 16â18 March 2020 (Mon-Wed) - Author notification: 8 April 2020 (Wed) Journal First ============= We have Journal First arrangements with ACM Transactions on Programming Languages and Systems and Elsevier Science of Computer Programming. Common to both routes --------------------- Only new research papers are eligible for the Journal First routes to ECOOP 2020. That is, it is not acceptable to submit an extension of a previous conference paper, even if the associated journal solicits extended papers via its standard submission route. Authors of all accepted Journal First papers will be invited to submit a short abstract for their paper to appear in the ECOOP 2020 conference proceedings. Journal First papers will be included along with research papers submitted directly to the conference when a Distinguished Paper is selected. Science of Computer Programming route ------------------------------------- See this dedicated web page [3] for full details of how to submit to the ECOOP 2020 Science of Computer Programming (SCP) special issue. Submission deadline: December 2, 2019 (Mon) ACM Transactions on Programming Languages and Systems route ----------------------------------------------------------- See this announcement [4] for details of the TOPLAS scheme whereby papers submitted to TOPLAS can be presented at selected conferences. Authors interested in this route should submit their paper to TOPLAS via its usual submission system and mark it as an ECOOP 2020 submission. The ECOOP Program Chair will then be informed of this submission and will have some input into the review process. Submission deadline: October 10, 2019 (Thu) More Information ================ For additional information, please contact the ECOOP Program Chair, Robert Hirschfeld [5]. [1] https://2020.ecoop.org/track/ecoop-2020-papers [2] https://www.dagstuhl.de/en/publications/lipics/instructions-for-authors/ [3] https://www.journals.elsevier.com/science-of-computer-programming/call-for-… [4] https://toplas.acm.org/announcements.cfm#submit-a-paper-for-pldi-2016 [5] https://www.hpi.uni-potsdam.de/hirschfeld/people/hirschfeld/

1 0

[Pharo 8.0] Build #1025: CompletionFallBack
by ci-pharo-ci-jenkins2＠inria.fr Nov. 28, 2019

Nov. 28, 2019

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

1 0

Re: [Pharo-dev] BlueInk removal
by Torsten Bergmann Nov. 28, 2019

Nov. 28, 2019

To me it certainly looks like a <before we freeze Pharo 8 we have to speed up with features> to get things in by all means. Have to admit I had this kind of "panic mode" myself several times in the past too ;) Stef writes he now does not have the time nor energy - which I guess (including his reactions) is a tribute to his workload. But then it would have been better to change to new Elumineire or getting rid of GTEventRecorder in Pharo 9 and now just marking them for later exclusion. Because often we all underestimate the depencies, side effects, migration costs - even the reactions. Meanwhile Pharo is not only the base image - it is the full ecosystem around it which is good and a positive sign and something we IMHO need to respect more and more. One has to understand that by just removing and not using deprecation the situation is getting worse and now pulling more time and energy from other parts of the community too. Because broken stuff like Spotter, Settings, Roassal, Moose, ... would need repair - either directly (to help contributors who use them in P8 alpha already to give quick feedback) - together with the Pharo 8 release so they can be used - after Pharo 8 is released (which would be very late and might include migration surprises) Depreaction would help us better managing such transitions and is something that is standard in other languages too. The alternative would be to say this is OPP (other peoples problem) and completely ignoring that projects are built on top of Pharo base. We all know removing leads to being incompatible and is not helpful in offering a transition path - therefore not a good option. Because then users would always need to start from scratch with each Pharo release and loose interest quickly. Users want to do both: use Pharo and move their projects without having to focus on changed infrastructure too often. Deprecation would give more room to fixing it- we have theses mechanisms like deprecations and we should really use them. In the past we were able to move more freely - but now we should really accept that with more users we have to follow certain backwards compatibility and more clear rules. This slows us down yes and requires more time and energy. But it is still a good thing because Pharo is actually used and the community can grow. We can not move Pharo into the "perfect" future with a crowbar as this would mean to loose users and especially trust into the system. We might then still come up with an improved (but still imperfect) system in a few years - but nobody would be interested anymore. If we fail to see things from the POV of the user then we will fail overall and loose them. I agree with Benoit that especially business users first have to solve the customers problems before they can juggle with migrations. So lets support the overall community and not being ignorant to it. So far we all managed it quite good: moving from Pharo 6 to 7 and even Pharo 8 is working because things over the last releases stabilized and also because we added more rules, depreactions, transformations and helping users. I personally would prefer to see that "Pharo is not perfect but strong and widely used" than "look how cool it could have been", so lets not get too impatient. Step by step - sometimes faster sometimes slower... Thanks T.

3 2

[Pharo 8.0] Build #1024: CompletionFallBack
by ci-pharo-ci-jenkins2＠inria.fr Nov. 28, 2019

Nov. 28, 2019

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

1 0

[Pharo 8.0] Build #1023: 5102-FastTable-Horizontal-Scrolling-not-implemented
by ci-pharo-ci-jenkins2＠inria.fr Nov. 28, 2019

Nov. 28, 2019

There is a new Pharo build available! The status of the build #1023 was: SUCCESS. The Pull Request #5107 was integrated: "5102-FastTable-Horizontal-Scrolling-not-implemented" Pull request url: https://github.com/pharo-project/pharo/pull/5107 Issue Url: https://github.com/pharo-project/pharo/issues/5102 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[ANN] freezing Pharo 8.0 development
by Esteban Lorenzano Nov. 28, 2019

Nov. 28, 2019

Hi, After talk about current situation of P8 development, we decided we have already a version that is very stable (with some remaining problems, we know) and we think this is something we can release before start the new batch of breaking changes (move to headless vm by default, new object centric debugger, etc, etc, etc.) So, I am declaring the development status on âcode freezeâ and we will start working on stabilisation hoping to have a releasable version by end December, beginning of January (yes, this will be a short cycle, but that will allow us to make some iterations needed without the pressure of releasing on April). Enjoy, Esteban

1 0

MDLApplication
by Sven Van Caekenberghe Nov. 28, 2019

Nov. 28, 2019

Hi, I am trying to use MaterialDesignLite (master branch in Pharo 7). The demo works perfectly. Now, I thought I would start writing a small web app by subclassing MDLApplication, since that seems to set up things properly. Is that class finished ? How am I supposed to use it ? There are screens, but how are these rendered ? Do I have to do this myself ? Must there not be an idea of a current screen ? MDLScreen is in fact an empty class. Although there are units tests for MDLApplication, there is no subclass, so no actual user. It feels a bit as if the demo should/could use it. Sven

3 5

[Pharo 8.0] Build #1022: In bootstrap: Preparing heap before writing the image to shrink its size
by ci-pharo-ci-jenkins2＠inria.fr Nov. 28, 2019

Nov. 28, 2019

There is a new Pharo build available! The status of the build #1022 was: SUCCESS. The Pull Request #5255 was integrated: "In bootstrap: Preparing heap before writing the image to shrink its size" Pull request url: https://github.com/pharo-project/pharo/pull/5255 Issue Url: https://github.com/pharo-project/pharo/issues/Pharo8.0 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

BlueInk removal
by Cyril Ferlicot Nov. 28, 2019

Nov. 28, 2019

Hi, Can we revert the removal of blueink the time the new formatter is in the image please? (And maybe deprecate it instead of removing it). I ask this because: - If we work with Pharo 8 we need to format the code by hand because the format option is currently messing the code - The current formatter is removing all method comment - Currently removing it without deprecation is breaking the setting system (And since I push the setting system further than most people, I cannot even open an image with settings now...) I remind that the formatter is called by the refactorings. Imagine my surprise when I wanted to commit refactorings and I saw all the formatting messed up and all my method comments missing. I really do not appreciate to lose comments I spent time to write like this... -- Cyril Ferlicot https://ferlicot.fr

6 12

[Pharo 8.0] Build #1021: 5246--AST-Core-Tests-package-disappeared
by ci-pharo-ci-jenkins2＠inria.fr Nov. 27, 2019

Nov. 27, 2019

There is a new Pharo build available! The status of the build #1021 was: FAILURE. The Pull Request #5254 was integrated: "5246--AST-Core-Tests-package-disappeared" Pull request url: https://github.com/pharo-project/pharo/pull/5254 Issue Url: https://github.com/pharo-project/pharo/issues/5246 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0