- Pharo-users - lists.pharo.org

Text presenter autosave features
by Offray Vladimir Luna CÃ¡rdenas March 29, 2019

March 29, 2019

Hi, While migrating Grafoscopio from Pharo 6.x to Pharo 7.x., I noticed that auto save for text fields is not enabled. Previously, when I wrote something in a text field, the dirty mark in the upper right corner appeared and if autoAccept was enabled, the text was automatically saved. Now with Pharo 7.x the dirty mark don't appear at all, and is not making any auto-saving. * I see that TextPresenter is the one who is responsible for such text objects. There is any minimal example I can use to test the proper behavior? * There is any way to use WelcomeHelp class to get a similar behavior? Thanks, Offray

2 2

First Call for Papers: 12th ACM SIGPLAN International Conference on Software Language Engineering (SLE 2019)
by Andrei Chis March 29, 2019

March 29, 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,screen]{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

Any desire to have/adapt ClyBrowserMorph>>#confirmDiscardChanges to be a little more informative?
by PAUL DEBRUICKER March 29, 2019

March 29, 2019

Right now with Calypso I often have so many windows open with multiple tabs that when it asks me if I want to discard changes I have a hard time seeing or remembering what its even talking about. Would it be hard to change it from a simple confirmation to a diff viewer of some kind with DiffMorph? I'd be particularly interested in seeing diffs between the pre-edited version and current. If that were a thing that were developed would it be integrated or not? Thanks

3 2

Re: [Pharo-users] Zinc and Oauth2
by Sven Van Caekenberghe March 28, 2019

March 28, 2019

Davide, The main Zinc repository is now https://github.com/svenvc/zinc (although the old ones are also still good). You should look at the baseline, but loading group SSO will get you started. I am not actively using OAuth, but several people have, so it should work (the code did not change in a long while). This is not such a simple subject though (there are several demos that used to work). Good luck, Sven > On 28 Mar 2019, at 20:54, Davide Varvello via Pharo-users <pharo-users(a)lists.pharo.org> wrote: > > > From: Davide Varvello <varvello(a)yahoo.com> > Subject: Zinc and Oauth2 > Date: 28 March 2019 at 20:54:05 GMT+1 > To: pharo-users(a)lists.pharo.org > > > Hi Guys, > I'm trying to play with Outh2, but I'm wondering how to download it in > Pharo. > > If I use the Gofer as indicated here: > https://github.com/svenvc/docs/blob/master/zinc/zinc-sso-paper.md > > Gofer it > url: 'http://mc.stfx.eu/ZincHTTPComponents'; > package: 'ConfigurationOfZincHTTPComponents'; > load. > ConfigurationOfZincHTTPComponents project latestVersion load: 'SSO'. > > > It returns an error. > Can you help me please? > > TIA > Davide > > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > > >

2 1

Zinc and Oauth2
by Davide Varvello March 28, 2019

March 28, 2019

Hi Guys, I'm trying to play with Outh2, but I'm wondering how to download it in Pharo. If I use the Gofer as indicated here: https://github.com/svenvc/docs/blob/master/zinc/zinc-sso-paper.md Gofer it url: 'http://mc.stfx.eu/ZincHTTPComponents'; package: 'ConfigurationOfZincHTTPComponents'; load. ConfigurationOfZincHTTPComponents project latestVersion load: 'SSO'. It returns an error. Can you help me please? TIA Davide -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

1 0

[ANN] Pharo Launcher 1.8.1 released
by Christophe Demarey March 28, 2019

March 28, 2019

Hi all, Pharo Launcher 1.8.1 has just been released! It is available from http://pharo.org/download <http://pharo.org/download>. Here is the changelog: Bug fixes: #326 Edit image description doesn't update when editing existing description #325 Instance of MacProcess did not understand #waitForCommand: #324 sources file not found for Pharo < 3.0 #321 abort process if not responding. Uses TaskIt Improvements: #239 Mac OS menus display "SqueakOSXApp" instead of Â« PharoLauncher Â» #323 Check if pharo-version.st should be updated #322 do not try to run image without preferences if not supported by the image Thanks to all contributors, including issue reports. Regards, The Pharo team.

1 0

Re: [Pharo-users] how to -- buffered read / write to stdio
by Alistair Grant March 27, 2019

March 27, 2019

Hi Isaac, On Wed, 27 Mar 2019 at 17:18, Isaac Gouy via Pharo-users <pharo-users(a)lists.pharo.org> wrote: > > From â "Pharo 7 file streams guideline" > > https://github.com/pavel-krivanek/pharoMaterials/blob/master/Filestreams.MD > > > I have some ideas like â > > in := ZnFastLineReader on: (ZnCharacterReadStream on: Stdio stdin). out := ZnBufferedWriteStream on: > (ZnCharacterWriteStream on: Stdio stdout). > > > What would be faster / better / more Pharo ways to do buffered reads and buffered writes to stdio ? This is heading in the right direction. The buffered wrappers are normally placed on the underlying binary stream, and then wrapped with the encoder / decoder. Follow through FileReference>>writeStream and FileReference>>readStream to see how it is done for files. in := ZnFastLineReader on: (ZnCharacterReadStream on: (ZnBufferedReadStream on: Stdio stdin)). out := ZnCharacterWriteStream on: (ZnBufferedWriteStream on: Stdio stdout). Note that if you're doing terminal IO you'll need to handle stdin differently. If you're writing to a terminal on Linux / MacOS you'll need to use LFs instead of Pharo's standard CRs, so it may be worthwhile adding ZnNewLineWriterStream on: out. HTH, Alistair

1 0

Re: [Pharo-users] More info & examples on MAAdaptiveModel ?
by Sean P. DeNigris March 27, 2019

March 27, 2019

Pharo Smalltalk Users mailing list wrote > I am looking for more info or usage examples of MAAdaptiveModel. The Nabble mirror site provides convenient search across many Smalltalk MLs. I don't know if any of these help, but there are several hits: http://forum.world.st/template/NamlServlet.jtp?macro=search_page&node=12947… ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

1 0

how to -- buffered read / write to stdio
by Isaac Gouy March 27, 2019

March 27, 2019

>From â "Pharo 7 file streams guideline" https://github.com/pavel-krivanek/pharoMaterials/blob/master/Filestreams.MD I have some ideas like â Â Â in := ZnFastLineReader on: Â Â Â Â Â (ZnCharacterReadStream on: Stdio stdin).Â Â out := ZnBufferedWriteStream on: Â Â Â Â Â (ZnCharacterWriteStream on: Stdio stdout). What would be faster / better / more Pharo ways to do buffered reads and buffered writes to stdio ?

1 0

Smalltalk CI - anyone have any luck excluding tests?
by Tim Mackinnon March 27, 2019

March 27, 2019

As part of Exercism we have to show our language track can build and run tests - and they use Travis - so, pretty awesome we have that tooling. So it was pretty straightforward t hook in - and there are enough examples around to support the docs for the .yml and .ston file - however I hit an issue with the inclusion and exclusion of test files. I put an issue on SmalltalkCI - but its sat there for 8days (https://github.com/hpi-swa/smalltalkCI/issues/417) so Iâm wondering if anyone has experience with this? Essentially if I include my other packages âExercismDevâ and âExercismToolsâ (see sample below - Iâve removed them from the include list) then some of my tests run twice (I believe because the exclude of #AllExercismTests doesnât work). I also have some environmental tests that need improving to run more generically (Submit/Download) and again those donât seem to be excluded. Itâs like âexclude" simply doesnât work - but I would think this would be reported more widely if this was the case. So maybe I donât understand the overlap of include/exclude etc. Anyone have any thoughts? Tim SmalltalkCISpec { #loading : [ SCIMetacelloLoadSpec { #baseline : 'Exercism', #directory : 'dev/src', #load : [ 'dev' ], #platforms : [ #pharo ] } ], #testing : { #include : { #packages : [ 'Exercism' ] }, #exclude : { #classes : [ #AllExercismTests, #ExercismTest, #ExercismSubmitTest, #ExercismDownloadTest ], #packages : [ 'ExercismWIP'] } } }

2 2