June 2019 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Strange 'Connection closed while waiting for data.' Zinc error
by Christopher Fuhrman June 7, 2019

June 7, 2019

Hi - I'm resurrecting an old question <http://forum.world.st/Strange-Connection-closed-while-waiting-for-data-Zinc…> I found on forum.world.st (sorry for the formatting) Dec 26, 2017; 10:14am Sven wrote: > > On 26 Dec 2017, at 08:21, Yuriy Tymchuk wrote: > > > > Hi Sven, > > > > No, Iâm on Mac (OS 10.13). > That is not good then, Uko, but again, there is no way to start debugging > this without a reliable test case that I can run too. > I hit this today while testing on localhost: a PlantUML server. I think I can give you a simple(ish) way to recreate: - clone the repo at https://github.com/plantuml/plantuml-server - install Java - install maven - In the clone directory, run: *mvn jetty:run* In Pharo, it's just: ZnEasy getPng: 'http://localhost:8080/plantuml/img/IzIrIm80'. Cheers, Christopher p.s. the workaround with *ZnNetworkingUtils default socketStreamClass: SocketStream.* is OK for me. I'm running Pharo 8 on Windows 10 (WSL) and the server's running on the Windows part. Sven > > Cheers. > > Uko

1 0

GPCE 2019: 2nd Call for Papers - Athens, Greece; October 21-22
by Rodin Aarssen June 6, 2019

June 6, 2019

CALL FOR PAPERS 18th International Conference on Generative Programming: Concepts & Experiences (GPCE 2019) October 21-22, 2019 Athens, Greece (co-located with SPLASH 2019) https://conf.researchr.org/home/gpce-2019 http://twitter.com/GPCECONF http://www.facebook.com/GPCEConference IMPORTANT DATES * Submission of abstracts: June 14, 2019 * Submission of papers: June 21, 2019 * Paper notification: August 9, 2019 Submission site: https://gpce19.hotcrp.com/ -------------------------------------------------------------------------- SCOPE GPCE is a venue for researchers and practitioners interested in techniques and tools for code generation, language implementation, and metaprogramming. GPCE seeks conceptual, theoretical, empirical, and technical contributions to its topics of interest, which include but are not limited to: * program transformation, staging, macro systems, preprocessors, program synthesis, and code-recommendation systems, * domain-specific languages, language embedding, language design, and language workbenches, * feature-oriented programming, domain engineering, and feature interactions, * applications and properties of code generation, language implementation, and product-line development. Authors are welcome to check with the program co-chairs whether their planned papers are in scope. PAPER SELECTION The GPCE program committee will evaluate each submission according to the following selection criteria: * Novelty. Papers must present new ideas or evidence 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 to the state of the art or practice in significant ways. * Evidence. The paper must present evidence supporting its claims. Examples of evidence include formalizations and proofs, implemented systems, experimental results, statistical analyses, and case studies. * Clarity. The paper must present its contributions and results clearly. PAPER CATEGORIES GPCE solicits three kinds of submissions. * Full Papers reporting original and unpublished results of research that contribute to scientific knowledge in any GPCE topic listed above. Full paper submissions must not exceed 12 pages excluding bibliography. * Short Papers presenting unconventional ideas or visions about any GPCE topic listed above. Short papers do not always require complete results as in the case of a full paper. In this way, authors can introduce new ideas to the community and get early feedback. Please note that short papers are not intended to be position statements. Short papers are included in the proceedings and will be presented at the conference. Short paper submissions must not exceed 6 pages excluding bibliography. * Tool Demonstrations presenting tools for any GPCE topic listed above. Tools must be available for use and must not be purely commercial. Submissions must provide a tool description not exceeding 6 pages excluding bibliography and a separate demonstration outline including screenshots also not exceeding 6 pages. Tool demonstrations must have the keywords "Tool Demo" or "Tool Demonstration" in their title. If the submission is accepted, the tool description will be published in the proceedings. The demonstration outline will only be used by the program committee for evaluating the submission. PAPER SUBMISSION All submissions must use the ACM SIGPLAN Conference Format "acmart", using the "sigplan" sub-format, and 10 point font. Additional details and links to templates and the LaTeX class file can be found on the conference web site: https://conf.researchr.org/home/gpce-2019. To increase fairness in reviewing, a double-blind review process has become standard across SIGPLAN conferences. GPCE will follow a very lightweight model, where author identities are revealed to reviewers after submitting their initial reviews. Hence, the purpose is not to conceal author identities at all cost, but merely to provide reviewers with an unbiased first look at a submission. Author names and institutions should be omitted from submitted papers, and references to the authors' own related work should be in the third person. No other changes are necessary, and authors will not be penalized if reviewers are able to infer their identities in implicit ways. Papers must be submitted using HotCRP: https://gpce19.hotcrp.com/ For additional information, clarification, or answers to questions please contact the program co-chairs. ORGANIZATION Chairs * General chair: Ina Schaefer (TU Braunschweig) * Program co-chair: Christoph Reichenbach (Lund University) * Program co-chair: Tijs van der Storm (CWI / University of Groningen) Program Committee * Jonathan Aldrich (CMU) * Juliana Alves Pereira (University of Rennes, INRIA) * Marsha Chechik (University of Toronto) * Shigeru Chiba (University of Tokyo) * Thomas Degueule (CWI) * Sebastian Erdweg (TU Delft) * Matthew Flatt (University of Utah) * Robert GlÃ¼ck (University of Copenhagen) * Elisa Gonzalez Boix (VUB) * Geoffrey Mainland (Drexel University) * Chris Martens (NCSU) * Maryam Mehri Dehnavi (University of Toronto) * Peter Mosses (Swansea University / TU Delft) * David Pearce (Victoria University of Wellington) * Alex Potanin (Victoria University of Wellington) * Larissa Rocha Soares (Federal University of Bahia) * Ulrik Schultz (University of Southern Denmark) * Sandro Schulze (University of Magdeburg) * Christoph Seidl (TU Braunschweig) * Michel Steuwer (University of Glasgow) * Sam Tobin Hochstadt (Indiana University) * Kanae Tsushima (National Institute of Informatics) * Philip Wadler (University of Edinburgh) * Eric Walkingshaw (Oregon State University) * Adam Welc (Uber) * Peng Wu (Huawei)

1 0

Smalltalk-Bolivia at ICSE SRC 2019
by Juan Pablo Sandoval Alcocer June 6, 2019

June 6, 2019

Hi, We would like to share good news from Bolivia. Our student Alejandra Siles participated in the ICSE Student Research Competition (Undergrad category). She present a tool called TOAD, which is a tool for recommending source code selection alternatives for the extract method refactoring. TOAD was developed in Pharo. You may find the prototype on http://smalltalkhub.com/#!/~juampi/Toad Alejandra was selected by the ACM SRC (Student Research Competition) as the best undergrad student. After 3 rounds (writing a short paper, writing and defending a poster, and presenting her results), she finished 1st in the undergrad category. This is a fantastic results that really show the quality of the research being done in Bolivia. You might find some pictures in the attached files. Regards, Juan Pablo Sandoval A. jpsandoval.github.io [image: IMG_6322.jpeg]

7 6

Re: [Pharo-users] Smalltalk-Bolivia at ICSE SRC 2019
by Mariano Martinez Peck June 5, 2019

June 5, 2019

Hi Juan Pablo, That's really great news. Specially congratulations to her and for all of you. BTW, was she part of the Summer Smalltalk we did in Bolivia back in 2014? https://marianopeck.wordpress.com/2014/12/07/my-presentations-at-summer-sch… It's nice to see Smalltalk still being pushed in Bolivia. I wish you the best. Cheers, -- Mariano Martinez Peck Email: marianopeck(a)gmail.com Twitter: @MartinezPeck LinkedIn: www.linkedin.com/in/mariano-martinez-peck <https://www.linkedin.com/in/mariano-mart%C3%ADnez-peck/> Blog: https://marianopeck.wordpress.com/

1 0

Second Call for Papers: 12th ACM SIGPLAN International Conference on Software Language Engineering (SLE 2019)
by Andrei Chis June 4, 2019

June 4, 2019

------------------------------------------------------------------------ Call for Papers: 12th ACM SIGPLAN International Conference on Software Language Engineering (SLE 2019) co-located with SPLASH 2019 Athens, Greece October 21-22, 2019 https://conf.researchr.org/home/sle-2019 http://www.sleconf.org/2019 Follow us on twitter: https://twitter.com/sleconf ------------------------------------------------------------------------ We are pleased to invite you to submit papers to the 12th ACM SIGPLAN International Conference on Software Language Engineering (SLE 2019), held in conjunction with SPLASH 2019 at Athens, Greece on October 21-22, 2019. --------------------------- Topics of Interest --------------------------- SLE 2019 solicits high-quality contributions in areas ranging from theoretical and conceptual contributions, to tools, techniques, and frameworks in the domain of software language engineering. Topics relevant to SLE cover generic aspects of software languages development rather than aspects of engineering a specific language. In particular, SLE is interested in contributions from the following areas: * Software Language Design and Implementation - Approaches to and methods for language design - Static semantics (e.g., design rules, well-formedness constraints) - Techniques for specifying behavioral / executable semantics - Generative approaches (incl. code synthesis, compilation) - Meta-languages, meta-tools, language workbenches * Software Language Validation - Verification and formal methods for languages - Testing techniques for languages - Simulation techniques for languages * Software Language Integration and Composition - Coordination of heterogeneous languages and tools - Mappings between languages (incl. transformation languages) - Traceability between languages - Deployment of languages to different platforms * Software Language Maintenance - Software language reuse - Language evolution - Language families and variability * Domain-specific approaches for any aspects of SLE (design, implementation, validation, maintenance) * Empirical evaluation and experience reports of language engineering tools - User studies evaluating usability - Performance benchmarks - Industrial applications --------------------------- Important Dates --------------------------- All dates are Anywhere on Earth. * Fri 14 Jun 2019 - Abstract Submission * Fri 21 Jun 2019 - Paper Submission * Fri 9 Aug 2019 - Author Notification * Fri 16 Aug 2019 - Artifact Submission * Fri 30 Aug 2019 - Artifact Kick-the-tires Author Response (7 days) * Fri 20 Sep 2019 - Camera ready deadline * Wed 25 Sep 2019 - Artifact notification * Fri 27 Sep 2019 - Artifact-related paper updates * Mon-Tue 21-22 Oct 2018 - SLE Conference --------------------------- Types of Submissions --------------------------- SLE 2019 solicits three types of contributions: Research Papers, Tools Papers, and New Ideas/Vision papers. * Research papers These should report a substantial research contribution to SLE or successful application of SLE techniques or both. Full paper submissions must not exceed 12 pages, excluding bibliography. * Tool papers Because of SLEâs interest in tools, we seek papers that present software tools related to the field of SLE. Selection criteria include originality of the tool, its innovative aspects, and relevance to SLE. Any of the SLE topics of interest are appropriate areas for tool demonstrations. Submissions must provide a tool description of 4 pages excluding bibliography, and a demonstration outline including screenshots of up to 6 pages. Tool demonstrations must have the keywords âTool Demoâ or âTool Demonstrationâ in the title. The 4-page tool description will, if the demonstration is accepted, be published in the proceedings. The 6-page demonstration outline will be used by the program committee only for evaluating the submission. *New ideas / vision papers New ideas papers should describe new, non-conventional SLE research approaches that depart from standard practice. They are intended to describe well-defined research ideas that are at an early stage of investigation. Vision papers are intended to present new unifying theories about existing SLE research that can lead to the development of new technologies or approaches. New ideas / vision papers must not exceed 4 pages, excluding bibliography. *Workshops Workshops will be organized by SPLASH. Please inform us and contact the SPLASH organizers if you would like to organize a workshop of interest to the SLE audience. Information on how to submit workshops can be found at the SPLASH 2019 Website. --------------------------- Artifact Evaluation --------------------------- SLE will continue to use an evaluation process for assessing the quality of the artifacts on which papers are based to foster the culture of experimental reproducibility. Authors of accepted papers are invited to submit artifacts. For more information, please have a look at the Artifact Evaluation page. --------------------------- Submission Details --------------------------- Paper Format: Submissions must conform to the ACM SIGPLAN Conference Format âacmartâ; please make sure that you always use the latest ACM SIGPLAN acmart LaTeX template, and that the document class definition is \documentclass[sigplan,anonymous,review]{acmart}. Do not make any changes to this format! Using the Word template is strongly discouraged. 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 in figures and tables are legible. To increase fairness in reviewing, a double-blind review process has become standard across SIGPLAN conferences. For the first time, SLE will follow the double-blind process. Author names and institutions should be omitted from submitted papers, and references to the authorsâ own related work should be in the third person. No other changes are necessary, and authors will not be penalized if reviewers are able to infer their identities in implicit ways. All submissions must be in PDF format. Concurrent Submissions: Papers must describe unpublished work that is not currently submitted for publication elsewhere as described by SIGPLANâs Republication Policy. Submitters should also be aware of ACMâs Policy and Procedures on Plagiarism. Submissions that violate these policies will be desk-rejected. Submission Site: Submissions will be accepted at https://sle19.hotcrp.com/ --------------------------- Reviewing Process --------------------------- All submitted papers will be reviewed by at least three members of the program committee. Research papers and tool papers will be evaluated concerning novelty, correctness, significance, readability, and alignment with the conference call. New ideas / vision papers will be evaluated primarily concerning novelty, significance, readability, and alignment with the conference call. For fairness reasons, all submitted papers must conform to the above instructions. Submissions that violate these instructions may be rejected without review, at the discretion of the PC chairs. --------------------------- Awards --------------------------- * Distinguished paper: Award for most notable paper, as determined by the PC chairs based on the recommendations of the programme committee. * Distinguished reviewer: Award for distinguished reviewer, as determined by the PC chairs. * Distinguished artifact: Award for the artifact most significantly exceeding expectations, as determined by the AEC chairs based on the recommendations of the artifact evaluation committee. --------------------------- Publication --------------------------- All accepted papers will be published in the ACM Digital Library. AUTHORS TAKE NOTE: The official publication date is the date the proceedings are made available in the ACM Digital Library. This date may be up to two weeks prior to the first day of the conference. The official publication date affects the deadline for any patent filings related to published work. --------------------------- Organisation --------------------------- Chairs: * General chair: Oscar Nierstrasz (University of Bern, Switzerland) * Program co-chair: Bruno Oliveira (University of Hong Kong, China) * Program co-chair: Jeff Gray (University of Alabama, USA) * Artefact Evaluation co-chair: Emma SÃ¶derberg (Lund University, Sweden) * Artefact Evaluation co-chair: Abel Gomez (Universitat Oberta de Catalunya, Spain) Program Committee: Xuan Bi (Standard Chartered Bank) Erwan Bousse (TU Wien) Loli Burgeuno (Open University of Catalonia) Marsha Chechik (University of Toronto) Matteo Cimini (University of Massachusetts, Lowell) Thomas Degueule (CWI) Juan de Lara (Universidad AutÃ³noma de Madrid) Juergen Dingel (Queen's University) Romina Eramo (University of L'Aquila) Sebastian Gerard (CEA) Paolo Giarusso (TU Delft) Esther Guerra (Universidad AutÃ³noma de Madrid) Pablo Inostroza (CWI) Dimitris Kolovos (University of York) Marjan Mernik (University of Maribor) Alfonso Pierantonio (University of L'Aquila) Jaroslav PorubÃ¤n (University of KoÅ¡ice) Casper Poulsen (TU Delft) Yann Regis-Gianas (Paris 7/INRIA) Bernhard Rumpe (RWTH Aachen University) Markus Schordan (Lawrence Livermore National Laboratory) Neil Sculthorpe (Nottingham Trent University) Marco Servetto (Victoria University of Wellington) Elizabeth Scott (Royal Holloway) Eugene Syriani (University of Montreal) Ulyana Tikhonova (CWI) Juha-Pekka Tolvanen (MetaCase) Antonio Valecillo (University of Malaga) Mark van den Brand (TU Eindhoven) Vadim Zaytsev (Raincode Labs) Tian Zhang (Nanjing University) --------------------------- Contact --------------------------- For additional information, clarification, or answers to questions, please contact the organizers by email (bruno(a)cs.hku.hk and gray(a)cs.ua.edu)

1 0

Block/Brick
by Steve Quezadas June 4, 2019

June 4, 2019

I am trying to experiment with Bloc and Brick. I downloaded the packages, and want to "play around with it" by experimenting with the examples in it. But how do I open the examples? The github page for both Block and Brick doesn't really list much documentation. Taking from an arbitrary Brick example, these things don't work: foo := BrExamplesShowroom new. foo openInWorld. - or - BrExamplesShowroom openPlayer Sorry for the naive quesiton. - Steve PS Is Brick/Block the thing to learn these days? Is this where development is heading?

2 2

Does anyone know Spec?
by Steve Quezadas June 3, 2019

June 3, 2019

I created a simple listbox. It looks like this: https://s3.amazonaws.com/steverstuff/items.png If I hit a specific selection, say "Item B", how can I make smalltalk run an arbitrary piece of code? (ie: "Transcript show: 'got here'"). Method "whenSelectedItemChanged" should, in theory, do this. It is mentioned in the [[ https://benjamin.vanryseghem.com/projects/spec/docs/example/#protocolList][…]] tutorial, but for some reason it's not executing. Did a new verion of spec change things since the documentation was written? There doesn't seem to be a spec community where I can ask the question.

4 4

Find after in strings?
by Tim Mackinnon June 3, 2019

June 3, 2019

Maybe this is a dumb question - and often Iâm surprised when asking these, but why is there no way to âfind afterâ a string. I find it rather boring to try and parse a string, after a known marker - thus: (loc := aString findString: âmarkerâ) > 0 ifTrue: [ loc := loc + âmarkerâ size ]. Is there a better way? This whole pattern seems very old and clunky and not smalltalk like? Couldnât we have: findAfter: aString ifAbsent: aBlock ? Or is there a whole better pattern for string searching that Iâm missing ? Tim

4 11

More Morphic snags
by Markus Stumptner June 2, 2019

June 2, 2019

I have been trying to replicate the behaviour of an existing (non-Pharo, non-Smalltalk) application with Morphic. This provides grouping images in a workspace, and then switching between laying them out separately or "stacked" by double clicking on the group (or an image in it). When the group is stacked, it can be moved around as a single drag and drop operation. When the group is separated, dragging an image out of it removes it from the group. On the surface this looked like a perfect fit to the submorph tree.Â Unfortunately, as both the Morphic chapter in Pharo by Example and the intro document by Maloney make clear, if you enable double clicking (by answering true to #handlesMouseDown:), you are interfering with what Maloney calls the "default behaviour" of being able to drag a Morph around. How do I reinstate that behaviour if a group is clicked on and the double click does not happen? Neither document helps in explaining where that "default" can be found in the code. Thanks Markus

3 2