May 2017 - Esug-list - lists.esug.org

Software Engineer vacancy at Yesplan

by Johan Brichau

Dear all, Yesplan is looking for a new colleague to join the software engineering team. The position is required to be full-time and on-site in Gent, Belgium. Do you fancy working with Pharo and GemStone/S but also with Javascript / ReactJS and other technologies to build intuitive event venue management software? Read our vacancy in the link below and let me know! http://yesplan.be/docs/yesplan-software-engineer-en.pdf <http://yesplan.be/docs/yesplan-software-engineer-en.pdf> Best regards Johan

May 10, 2017

2nd CfP: SLE 2017 (10th ACM SIGPLAN International Conference on Software Language Engineering)

by Andrei Chis

======================================================================== **Call for Papers** 10th ACM SIGPLAN International Conference on Software Language Engineering (SLE 2017) 23-24 October 2017, Vancouver, Canada (Co-located with SPLASH 2017) General chair: Benoit Combemale, University of Rennes 1, France Program co-chairs: Marjan Mernik, University of Maribor, Slovenia Bernhard Rumpe, RWTH Aachen University, Germany Artifact evaluation chairs: Tanja Mayerhofer, TU Wien, Austria Laurence Tratt, King's College London, UK Keynote Speaker: Peter D. Mosses, Swansea University, UK (http://cs.swan.ac.uk/~cspdm/) http://conf.researchr.org/track/sle-2017/sle-2017-papers http://www.sleconf.org/2017 Follow us on twitter: https://twitter.com/sleconf ======================================================================== Software Language Engineering (SLE) is the application of systematic, disciplined, and measurable approaches to the development, use, deployment, and maintenance of software languages. The term "software language" is used broadly, and includes: general-purpose programming languages; domain-specific languages (e.g. BPMN, Simulink, Modelica); modeling and metamodeling languages (e.g. SysML and UML); data models and ontologies (e.g. XML-based and OWL-based languages and vocabularies). ### Important Dates Fri 2 Jun 2017 - Abstract Submission Fri 9 Jun 2017 - Paper Submission Fri 4 Aug 2017 - Author Notification Thu 10 Aug 2017 - Artifact Submission Fri 1 Sep 2017 - Artifact Notification Fri 8 Sep 2017 - Camera Ready Deadline Sun 22 Oct - SLE workshops Mon 23 Oct - Tue 24 Oct 2017 - SLE Conference ### Topics of Interest SLE aims to be broad-minded and inclusive about relevance and scope. We solicit high-quality contributions in areas ranging from theoretical and conceptual contributions to tools, techniques, and frameworks in the domain of 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 principled engineering approaches and techniques in the following areas: * Language Design and Implementation * Approaches and methodologies for language design * Static semantics (e.g., design rules, well-formedness constraints) * Techniques for behavioral / executable semantics * Generative approaches (incl. code synthesis, compilation) * Meta-languages, meta-tools, language workbenches * Language Validation * Verification and formal methods for languages * Testing techniques for languages * Simulation techniques for languages * 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 * 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 ### Types of Submissions * **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 including bibliography in ACM SIGPLAN acmart conference style (http://www.sigplan.org/Resources/Author/) * **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 including bibliography in ACM SIGPLAN acmart conference style (http://www.sigplan.org/Resources/Author/) 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. * **Industrial papers**: These should describe real-world application scenarios of SLE in industry, explained in their context with an analysis of the challenges that were overcome and the lessons which the audience can learn from this experience. Industry paper submissions must not exceed 6 pages including bibliography in ACM SIGPLAN acmart conference style (http://www.sigplan.org/Resources/Author/) * **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 including bibliography in ACM SIGPLAN acmart conference style (http://www.sigplan.org/Resources/Author/) ### Artifact evaluation SLE will for the second year use an evaluation process for assessing the quality of artifacts on which papers are based. The aim of this evaluation process is to foster a culture of experimental reproducibility as well as a higher quality in the research area as a whole. Authors of papers accepted for SLE 2017 will be invited to submit artifacts. Any kind of artifact that is presented in the paper, supplements the paper with further details, or underlies the paper can be submitted. This includes, for instance, tools, grammars, metamodels, models, programs, algorithms, scripts, proofs, datasets, statistical tests, checklists, surveys, interview scripts, visualizations, annotated bibliographies, and tutorials. The submitted artifacts will be reviewed by a dedicated Artifact Evaluation Committee (AEC). Artifacts that live up to the expectations created by the paper will receive a badge of approval from the AEC. The approved artifacts will be invited for inclusion in the electronic conference proceedings published in the ACM Digital Library. This will ensure the permanent and durable storage of the artifacts alongside the published papers fostering the repeatability of experiments, enabling precise comparison with alternative approaches, and helping the dissemination of the author’s ideas in detail. Participating in the artifact evaluation and publishing approved artifacts in the ACM Digital Library is voluntary. However, we strongly encourage authors to consider this possibility as the availability of artifacts will greatly benefit readers of papers and increase the impact of the work. Note that the artifact evaluation cannot affect the acceptance of the paper, because it only happens after the decision about acceptance has been made. ### Publications All submitted papers will be reviewed by at least three members of the program committee. All accepted papers, including tool papers, industrial papers and new ideas / vision papers will be published in ACM Digital Library. Selected accepted papers will be invited to a special issue of the Computer Languages, Systems and Structures (COMLAN) journal. ### Awards * **Distinguished paper**: Award for most notable paper, as determined by the PC chairs based on the recommendations of the program committee. * **Distinguished reviewer**: Award for distinguished reviewer, as determined by the PC chairs using feedback from the authors. * **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. ### Program Committee Marjan Mernik (co-chair), University of Maribor, Slovenia Bernhard Rumpe (co-chair), RWTH Aachen University, Germany Christian Berger, Chalmers, Sweden Mark van den Brand, TU Eindhoven, The Netherlands Ruth Breu, University of Innsbruck, Austria Jordi Cabot, ICREA, Spain Walter Cazzola, University of Milan, Italy Marsha Chechik, University of Toronto, Canada Tony Clark, Middlesex University, UK Tom Dinkelaker, Ericsson, Germany Bernd Fischer, Stellenbosch University, South Africa Sebastian Gerard, CEA, France Jeff Gray, University of Alabama, USA Esther Guerra, Autonomous University of Madrid, Spain Michael Homer, Victoria University of Wellington, New Zealand Ralf Lämmel, University of Koblenz-Landau, Germany Tihamer Levendovszky, Microsoft, USA Gunter Mussbacher, McGill University, Canada Terence Parr, University of San Francisco, USA Jaroslav Porubän, University of Košice, Slovakia Jan Ringert, Tel Aviv University, Israel Julia Rubin, University of British Columbia, Canada Tony Sloane, Macquarie University, Australia Eugene Syriani, University of Montreal, Canada Emma Söderberg, Google, Denmark Eric Van Wyk, University of Minnesota, USA Jurgen Vinju, CWI, Netherlands Eric Walkingshaw, Oregon State University, USA Andreas Wortmann, RWTH Aachen University, Germany Tian Zhang, Nanjing University, China ### Contact For any question, please contact the organizers via email: sle2017(a)inria.fr

May 8, 2017

Re: [Esug-list] [Moose-dev] Re: [ann] gt4gemstone

by Mariano Martinez Peck

On Wed, May 3, 2017 at 1:55 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > > On May 3, 2017, at 1:00 AM, Mariano Martinez Peck <marianopeck(a)gmail.com> > wrote: > > > > Hi Doru, > > > > That's very cool! I am on vacation now so I don't have much time to take > a deeper look. > > Quick questions: > > 1) is this using the CGI FFI port I did for Pharo 5 UFFI? > > Of course :). > Cool! I am glad that is being used and that it was worth! I still remember the skype call we had some time ago :) > > > 2) Which pharo and gemstone versions are supported? Does this work for > Pharo 5.0 and GemStone 3.3.3 ? > > - Pharo 5.0, Pharo 6.0. > - GemStone 3.3.3 > > Excellent. That fits my client app. I will try to test it when I am back. Best, > Cheers, > Doru > > > > Thanks! > > > > > > On Tue, May 2, 2017 at 6:29 PM, Tudor Girba <tudor(a)tudorgirba.com> > wrote: > > Hi, > > > > feenk.com is proud to announce gt4gemstone, a version of the Glamorous > Toolkit aimed at supporting remote development with GemStone/S from Pharo. > gt4gemstone is released as an open-source project under the MIT license and > was built primarily by Andrei Chis with some marginal contributions from me. > > > > The project is hosted at: > > https://github.com/feenkcom/gt4gemstone > > > > The toolkit currently offers several features: > > • Remote Playground > > • Remote Inspector with extensions that can be coded exactly > like the ones in Pharo > > • Remote Debugger with mixed stacks (Pharo and GemStone) > > • Basic Remote Code Browser > > • Remote Session Handler > > • Integration with Roassal > > • A Glamour-specific proxy model for efficient serialization of > Glamour presentations > > • A basic proxy model for working with any remote objects from > GemStone > > > > One particular aspect that we focused on is performance. So much so, > that at one point inspecting objects in gt4gemstone was faster than doing > them locally. In the meantime, the GT inspector from Pharo also received an > upgrade. > > > > But, perhaps the most exciting thing about this project is that most > extensions of the inspector can be expressed exactly in the same way both > in Pharo and in GemStone, and this makes the scenario of building in Pharo > and deploying in GemStone even more appealing. > > > > The official announcement with some extra details can be found here: > > http://www.humane-assessment.com/blog/introducing-gt4gemstone/ > > > > Cheers, > > Tudor > > > > -- > > www.tudorgirba.com > > www.feenk.com > > > > "There are no old things, there are only old ways of looking at them." > > > > > > > > > > _______________________________________________ > > Moose-dev mailing list > > Moose-dev(a)list.inf.unibe.ch > > https://www.list.inf.unibe.ch/listinfo/moose-dev > > > > > > > > -- > > Mariano > > http://marianopeck.wordpress.com > > _______________________________________________ > > Moose-dev mailing list > > Moose-dev(a)list.inf.unibe.ch > > https://www.list.inf.unibe.ch/listinfo/moose-dev > > -- > www.tudorgirba.com > www.feenk.com > > “Live like you mean it." > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev > -- Mariano http://marianopeck.wordpress.com

May 3, 2017

Re: [Esug-list] [Moose-dev] [ann] gt4gemstone

by Tudor Girba

Hi, > On May 3, 2017, at 1:00 AM, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > > Hi Doru, > > That's very cool! I am on vacation now so I don't have much time to take a deeper look. > Quick questions: > 1) is this using the CGI FFI port I did for Pharo 5 UFFI? Of course :). > 2) Which pharo and gemstone versions are supported? Does this work for Pharo 5.0 and GemStone 3.3.3 ? - Pharo 5.0, Pharo 6.0. - GemStone 3.3.3 Cheers, Doru > Thanks! > > > On Tue, May 2, 2017 at 6:29 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > feenk.com is proud to announce gt4gemstone, a version of the Glamorous Toolkit aimed at supporting remote development with GemStone/S from Pharo. gt4gemstone is released as an open-source project under the MIT license and was built primarily by Andrei Chis with some marginal contributions from me. > > The project is hosted at: > https://github.com/feenkcom/gt4gemstone > > The toolkit currently offers several features: > • Remote Playground > • Remote Inspector with extensions that can be coded exactly like the ones in Pharo > • Remote Debugger with mixed stacks (Pharo and GemStone) > • Basic Remote Code Browser > • Remote Session Handler > • Integration with Roassal > • A Glamour-specific proxy model for efficient serialization of Glamour presentations > • A basic proxy model for working with any remote objects from GemStone > > One particular aspect that we focused on is performance. So much so, that at one point inspecting objects in gt4gemstone was faster than doing them locally. In the meantime, the GT inspector from Pharo also received an upgrade. > > But, perhaps the most exciting thing about this project is that most extensions of the inspector can be expressed exactly in the same way both in Pharo and in GemStone, and this makes the scenario of building in Pharo and deploying in GemStone even more appealing. > > The official announcement with some extra details can be found here: > http://www.humane-assessment.com/blog/introducing-gt4gemstone/ > > Cheers, > Tudor > > -- > www.tudorgirba.com > www.feenk.com > > "There are no old things, there are only old ways of looking at them." > > > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev > > > > -- > Mariano > http://marianopeck.wordpress.com > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev -- www.tudorgirba.com www.feenk.com “Live like you mean it."

May 3, 2017

Re: [Esug-list] [Moose-dev] [ann] gt4gemstone

by Mariano Martinez Peck

Hi Doru, That's very cool! I am on vacation now so I don't have much time to take a deeper look. Quick questions: 1) is this using the CGI FFI port I did for Pharo 5 UFFI? 2) Which pharo and gemstone versions are supported? Does this work for Pharo 5.0 and GemStone 3.3.3 ? Thanks! On Tue, May 2, 2017 at 6:29 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > feenk.com is proud to announce gt4gemstone, a version of the Glamorous > Toolkit aimed at supporting remote development with GemStone/S from Pharo. > gt4gemstone is released as an open-source project under the MIT license and > was built primarily by Andrei Chis with some marginal contributions from me. > > The project is hosted at: > https://github.com/feenkcom/gt4gemstone > > The toolkit currently offers several features: > • Remote Playground > • Remote Inspector with extensions that can be coded exactly like > the ones in Pharo > • Remote Debugger with mixed stacks (Pharo and GemStone) > • Basic Remote Code Browser > • Remote Session Handler > • Integration with Roassal > • A Glamour-specific proxy model for efficient serialization of > Glamour presentations > • A basic proxy model for working with any remote objects from > GemStone > > One particular aspect that we focused on is performance. So much so, that > at one point inspecting objects in gt4gemstone was faster than doing them > locally. In the meantime, the GT inspector from Pharo also received an > upgrade. > > But, perhaps the most exciting thing about this project is that most > extensions of the inspector can be expressed exactly in the same way both > in Pharo and in GemStone, and this makes the scenario of building in Pharo > and deploying in GemStone even more appealing. > > The official announcement with some extra details can be found here: > http://www.humane-assessment.com/blog/introducing-gt4gemstone/ > > Cheers, > Tudor > > -- > www.tudorgirba.com > www.feenk.com > > "There are no old things, there are only old ways of looking at them." > > > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev > -- Mariano http://marianopeck.wordpress.com

May 2, 2017

[ann] gt4gemstone

by Tudor Girba

Hi, feenk.com is proud to announce gt4gemstone, a version of the Glamorous Toolkit aimed at supporting remote development with GemStone/S from Pharo. gt4gemstone is released as an open-source project under the MIT license and was built primarily by Andrei Chis with some marginal contributions from me. The project is hosted at: https://github.com/feenkcom/gt4gemstone The toolkit currently offers several features: • Remote Playground • Remote Inspector with extensions that can be coded exactly like the ones in Pharo • Remote Debugger with mixed stacks (Pharo and GemStone) • Basic Remote Code Browser • Remote Session Handler • Integration with Roassal • A Glamour-specific proxy model for efficient serialization of Glamour presentations • A basic proxy model for working with any remote objects from GemStone One particular aspect that we focused on is performance. So much so, that at one point inspecting objects in gt4gemstone was faster than doing them locally. In the meantime, the GT inspector from Pharo also received an upgrade. But, perhaps the most exciting thing about this project is that most extensions of the inspector can be expressed exactly in the same way both in Pharo and in GemStone, and this makes the scenario of building in Pharo and deploying in GemStone even more appealing. The official announcement with some extra details can be found here: http://www.humane-assessment.com/blog/introducing-gt4gemstone/ Cheers, Tudor -- www.tudorgirba.com www.feenk.com "There are no old things, there are only old ways of looking at them."

May 2, 2017

Looking for contacts in Taiwan

by Stéphane Ducasse

Hi Smalltalkers I’m preparing a trip to taiwan for the fall 2017 and I would like to get some contacts with Universities, engineer schools, developers that could interested in advanced design, Pharo, Smalltalk. Let me know. Stef -------------------------------------------- Stéphane Ducasse http://stephane.ducasse.free.fr http://www.synectique.eu / http://www.pharo.org 03 59 35 87 52 Assistant: Julie Jonas FAX 03 59 57 78 50 TEL 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, Bât.A, Park Plaza Villeneuve d'Ascq 59650 France

May 1, 2017