May 2021 - Pharo-users - lists.pharo.org

Re: Looking for more non-trivial example application based on Spec2 to learn from...

by Russ Whaley

Great, Sebastian, thanks. Iâll take a (braver) look into the code soon. Iâll touch base on discord :) On Thu, May 13, 2021 at 10:39 AM Sebastian Jordan <sebastianjmt(a)hotmail.com> wrote: > Hi Russ, > Do not scarry of the WorldMenu item. Any tool can appear in the WorldMenu > if it has a class side method `menuCommandOn:`. Just load the code with > the script that appears in the README. Look at the classes in the packages > and you will see that a lot of them are children of SpPresenter. I do not > know if my tools is a complete example of all Spec framework. But at least > it has all the basics covered. > Let me know if you have any question ð We can talk on Discord too. > > Sebastian > ------------------------------ > *From:* Russ Whaley <whaley.russ(a)gmail.com> > *Sent:* 12 May 2021 12:52 > *To:* Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > > *Subject:* [Pharo-users] Re: Looking for more non-trivial example > application based on Spec2 to learn from... > > Mark & Sebastian, > Sebastian, the link you provided is to a RewriteToolsSet... I don't > understand how this provides insights into a Spec2 solution? - but > admittedly I didn't dig too deep - I saw WorldMenu items and went > 'woah-stop!', lol. I'm hoping there was another link Mark referenced that > perhaps didn't come through my email chain :) > > I REALLY want to learn how others use Spec2 in an integrated way > (interconnected presenters, model refreshes, etc.). I've written 6 apps in > Pharo (all with Spec2 GUI) and I still don't feel as if I'm doing things > correctly. I can 'get things to work' and I'm pretty pleased with them in > general, but I usually run up against the same 'refresh' issues, especially > around notebooks. > > Esteban is a wealth of information and has been very helpful for my basic > understanding - but I can envision him shaking his head at my feeble > attempts and questions (just kidding Esteban!). > > I am VERY interested to review Spec2 code others are successfully using, > so I can hopefully get past whatever brainblock I have in my Spec2 designs. > > ... and I would very much like to be involved in a Spec2 > workshop/session/whatever! > > Happy Pharo-ing! > Russ (whalehead on discord) > > On Wed, May 12, 2021 at 5:32 AM <mark.odonoghue.2010(a)gmail.com> wrote: > > Hi Tim > > Thanks for the suggestion - Iâm aware of the alternative of using a web > application architecture using something like Seaside (and now CodeParadise > too - thanks). > > But Iâm more interested at the moment in getting on top of a more > traditional application for these personal apps I want to build for my > desktop PC. > > My needs may change of course - and Iâm sure will look at doing some web > apps in the future... > > More importantly - YES - it is great to be back in a ST environment again > , and of course it is still so very very addictive !! > > [ Before resuming I spent some time familiarising myself with the > mainstream tools the industry seems to have adopted in the last 10-20 > years. I must say I was quite surprised and even disappointed about the > complexity, verbosity and incomprehensible syntax of some, and the > sloppiness (or is it flexibility?) of others. I really was not keen to have > to pick up one of those again. I had somehow hoped or expected that > language and environment design would have been much slicker and more fully > evolved by nowâ¦] > > Cheers Tim, and thanks for the suggestionâ¦ > > Mark > > > > -- > Russ Whaley > whaley.russ(a)gmail.com > -- Russ Whaley whaley.russ(a)gmail.com

May 13, 2021

Re: Looking for more non-trivial example application based on Spec2 to learn from...

by Sebastian Jordan

Hi Russ, Do not scarry of the WorldMenu item. Any tool can appear in the WorldMenu if it has a class side method `menuCommandOn:`. Just load the code with the script that appears in the README. Look at the classes in the packages and you will see that a lot of them are children of SpPresenter. I do not know if my tools is a complete example of all Spec framework. But at least it has all the basics covered. Let me know if you have any question ð We can talk on Discord too. Sebastian ________________________________ From: Russ Whaley <whaley.russ(a)gmail.com> Sent: 12 May 2021 12:52 To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> Subject: [Pharo-users] Re: Looking for more non-trivial example application based on Spec2 to learn from... Mark & Sebastian, Sebastian, the link you provided is to a RewriteToolsSet... I don't understand how this provides insights into a Spec2 solution? - but admittedly I didn't dig too deep - I saw WorldMenu items and went 'woah-stop!', lol. I'm hoping there was another link Mark referenced that perhaps didn't come through my email chain :) I REALLY want to learn how others use Spec2 in an integrated way (interconnected presenters, model refreshes, etc.). I've written 6 apps in Pharo (all with Spec2 GUI) and I still don't feel as if I'm doing things correctly. I can 'get things to work' and I'm pretty pleased with them in general, but I usually run up against the same 'refresh' issues, especially around notebooks. Esteban is a wealth of information and has been very helpful for my basic understanding - but I can envision him shaking his head at my feeble attempts and questions (just kidding Esteban!). I am VERY interested to review Spec2 code others are successfully using, so I can hopefully get past whatever brainblock I have in my Spec2 designs. ... and I would very much like to be involved in a Spec2 workshop/session/whatever! Happy Pharo-ing! Russ (whalehead on discord) On Wed, May 12, 2021 at 5:32 AM <mark.odonoghue.2010(a)gmail.com<mailto:mark.odonoghue.2010@gmail.com>> wrote: Hi Tim Thanks for the suggestion - Iâm aware of the alternative of using a web application architecture using something like Seaside (and now CodeParadise too - thanks). But Iâm more interested at the moment in getting on top of a more traditional application for these personal apps I want to build for my desktop PC. My needs may change of course - and Iâm sure will look at doing some web apps in the future... More importantly - YES - it is great to be back in a ST environment again , and of course it is still so very very addictive !! [ Before resuming I spent some time familiarising myself with the mainstream tools the industry seems to have adopted in the last 10-20 years. I must say I was quite surprised and even disappointed about the complexity, verbosity and incomprehensible syntax of some, and the sloppiness (or is it flexibility?) of others. I really was not keen to have to pick up one of those again. I had somehow hoped or expected that language and environment design would have been much slicker and more fully evolved by nowâ¦] Cheers Tim, and thanks for the suggestionâ¦ Mark -- Russ Whaley whaley.russ(a)gmail.com<mailto:whaley.russ@gmail.com>

May 13, 2021

CFP: SLE 2021 - 14th ACM SIGPLAN International Conference on Software Language Engineering

by Andrei Chis

------------------------------------------------------------------------ 14th ACM SIGPLAN International Conference on Software Language Engineering (SLE 2021) October 17-19, 2021 Chicago, Illinois https://conf.researchr.org/home/sle-2021 http://www.sleconf.org/2021 Follow us on twitter: https://twitter.com/sleconf ------------------------------------------------------------------------ We are pleased to invite you to submit papers to the 14th ACM SIGPLAN International Conference on Software Language Engineering (SLE 2021), held in conjunction with SPLASH, GPCE and SAS 2021. Based on the future developments the conference will be hosted in Chicago, Illinois, United States on October 17-19, 2021 or will be held as a virtual event. --------------------------- Scope --------------------------- The ACM SIGPLAN International Conference on Software Language Engineering (SLE) is devoted to the principles of software languages: their design, their implementation, and their evolution. With the ubiquity of computers, software has become the dominating intellectual asset of our time. In turn, this software depends on software languages, namely the languages it is written in, the languages used to describe its environment, and the languages driving its development process. Given that everything depends on software and that software depends on software languages, it seems fair to say that for many years to come, everything will depend on software languages. Software language engineering (SLE) is the discipline of engineering languages and their tools required for the creation of software. It abstracts from the differences between programming languages, modelling languages, and other software languages, and emphasizes the engineering facet of the creation of such languages, that is, the establishment of the scientific methods and practices that enable the best results. While SLE is certainly driven by its metacircular character (software languages are engineered using software languages), SLE is not self-satisfying: its scope extends to the engineering of languages for all and everything. Like its predecessors, the 14th edition of the SLE conference, SLE 2021, will bring together researchers from different areas united by their common interest in the creation, capture, and tooling of software languages. It overlaps with traditional conferences on the design and implementation of programming languages, model-driven engineering, and compiler construction, and emphasizes the fusion of their communities. To foster the latter, SLE traditionally fills a two-day program with a single track, with the only temporal overlap occurring between co-located events. --------------------------- Topics of Interest --------------------------- SLE 2021 solicits high-quality contributions in areas ranging from theoretical and conceptual contributions, to tools, techniques, and frameworks in the domain of software language engineering. Broadly speaking, SLE covers software language engineering rather than engineering a specific software language. Topics of interest include, but are not limited to: * 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. * Mon 5 Jul 2021 - Abstract Submissions * Fri 9 Jul 2021 - Paper Submissions * Wed 1 Sep 2021 - Review Notification * Wed-Fri 1-3 Sep 2021 - Author Response Period * Mon 13 Sep 2021 - Notification * Wed 15 Sept 2021 - Artifact Submissions * Tue 28 Sep 2021 - Artifact Kick-the-tires Author Response * Tue 12 Oct 2021 - Artifact Notification * Sun-Tue 17-19 Oct 2021 - SLE Conference --------------------------- Types of Submissions --------------------------- SLE 2021 solicits three types of papers: * Research papers These are "traditional" papers detailing research contributions to SLE. These papers have a limit of 12 pages, and may optionally include 8 further pages of bibliography/appendices * Tool papers These are papers which focus on the tooling aspects which are often forgotten or neglected in research papers. A good tool paper focuses on practical insights that are likely to be useful to other implementers or users in the future. Any of the SLE topics of interest are appropriate areas for tool demonstrations. Submissions must not exceed 5 pages and may optionally include 1 further page of bibliography / appendices. They may optionally come with an appendix with a demo outline / screenshots and/or a short video/screencast illustrating the tool. The title of a Tool paper must start with "Tool Demo:". *New ideas / vision papers These are papers on forward-looking, innovative research in software language engineering. Our aim here is to accelerate the exposure of the software language engineering community to early yet potentially ground-breaking research results, or to techniques and perspectives that challenge the status quo in the discipline. New ideas / vision papers must not exceed 5 pages, and may optionally include 1 further page of bibliography / appendices. The title of a new ideas / vision papers must start with "New Ideas:" or "Vision:". --------------------------- Artifact Evaluation --------------------------- For the sixth year, SLE will 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 (http://www.sleconf.org/2021/ArtifactEvaluation.html) --------------------------- Submission --------------------------- Submissions have to use the ACM SIGPLAN Conference Format âacmartâ ( http://sigplan.org/Resources/Author/#acmart-format) please make sure that you always use the latest ACM SIGPLAN acmart LaTeX template( https://www.acm.org/binaries/content/assets/publications/consolidated-tex-t…) and that the document class definition is \documentclass[sigplan,anonymous,review]{acmart}. Do not make any changes to this format! 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. In this line, 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 ( http://www.sigplan.org/Resources/Policies/Republication) Submitters should also be aware of ACMâs Policy and Procedures on Plagiarism ( http://www.acm.org/publications/policies/plagiarism_policy) Submissions that violate these policies will be desk-rejected. Submission Site: Submissions will be accepted at https://sle21.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: Eelco Visser, Delft University of Technology, Netherlands * Program co-chair: Dimitris Kolovos, University of York, United Kingdom * Program co-chair: Emma SÃ¶derberg, Lund University, Sweden * Artefact Evaluation co-chair: Elias Castegren, KTH, Sweden * Artefact Evaluation co-chair: Andreas Wortmann, RWTH Aachen University, Germany Program Committee: Vincent Aranega, University of Lille, France Mikhail Barash, University of Bergen, Norway Melanie Bats, Obeo, France David Broman, KTH, Sweden Shigeru Chiba, University of Tokyo, Japan Alfonso de la Vega, University of York, United Kingdom Juan De Lara, Universidad AutÃ³noma de Madrid, Spain Davide Di Ruscio, University of L'Aquila, Italy Marcos Didonet del Fabro, Universidade Federal do ParanÃ¡, Brazil Juergen Dingel, Queen's University, Canada Michalis Famelis, University of Montreal, Canada Bernd Fischer, Stellenbosch University, South Africa Niklas Fors, Lund University, Sweden Antonio Garcia Dominguez, Aston University, United Kingdom Esther Guerra, Universidad AutÃ³noma de Madrid, Spain GÃ¶rel Hedin, Lund University, Sweden Stuart Hutchesson, Independent, United Kingdom Adrian Johnstone, Royal Holloway, United Kingdom Paddy Krishnan, Oracle Labs, Australia James Noble, Victoria University of Wellington, New Zealand Carlos Olarte, ECT UFRN, Brazil JoÃ£o Saraiva, HASLab / INESC TEC and Universidade do Minho, Portugal Anthony Sloane, Macquarie University, Australia Daniel StrÃ¼ber, Radboud University , Netherlands Ulyana Tikhonova, CWI, Netherlands Mark van der Brand, TU Eindhoven, Netherlands Juan Manuel Vara, Universidad Rey Juan Carlos, Spain Ran Wei, Dalian University of Technology, China Bahman Zamani, University of Isfahan, Iran --------------------------- Contact --------------------------- For additional information, clarification, or answers to questions, please contact the Program Chairs (Emma SÃ¶derberg and Dimitris Kolovos).

May 13, 2021

Re: Looking for more non-trivial example application based on Spec2 to learn from...

by Kasper Osterbye

My sheep project - Ovina2 - is now public for other to be scared about. I am on my way out the door, so databases will have to wait until monday when I am back from kayaking. This is the link: https://github.com/kasperosterbye/ovina2 The two main presenters are OvinaHistoryPresenter and OvinaAllSheepsPresenter, I expect they end up living in a single app window in the end. In my view it is about 80% done. Best, Kasper >

May 13, 2021

Re: Looking for more non-trivial example application based on Spec2 to learn from...

by Samuel Teixeira Santos

It would be great ð Em ter., 11 de mai. de 2021 Ã s 13:38, Esteban Lorenzano <estebanlm(a)netc.eu> escreveu: > I am playing with the idea of setting a bunch of techtalk sessions to > "build an application from scratch". > I need to book the time but I think it can be a good idea. > > Esteban >

May 13, 2021

Re: Looking for more non-trivial example application based on Spec2 to learn from...

by Russ Whaley

Mark & Sebastian, Sebastian, the link you provided is to a RewriteToolsSet... I don't understand how this provides insights into a Spec2 solution? - but admittedly I didn't dig too deep - I saw WorldMenu items and went 'woah-stop!', lol. I'm hoping there was another link Mark referenced that perhaps didn't come through my email chain :) I REALLY want to learn how others use Spec2 in an integrated way (interconnected presenters, model refreshes, etc.). I've written 6 apps in Pharo (all with Spec2 GUI) and I still don't feel as if I'm doing things correctly. I can 'get things to work' and I'm pretty pleased with them in general, but I usually run up against the same 'refresh' issues, especially around notebooks. Esteban is a wealth of information and has been very helpful for my basic understanding - but I can envision him shaking his head at my feeble attempts and questions (just kidding Esteban!). I am VERY interested to review Spec2 code others are successfully using, so I can hopefully get past whatever brainblock I have in my Spec2 designs. ... and I would very much like to be involved in a Spec2 workshop/session/whatever! Happy Pharo-ing! Russ (whalehead on discord) On Wed, May 12, 2021 at 5:32 AM <mark.odonoghue.2010(a)gmail.com> wrote: > Hi Tim > > Thanks for the suggestion - Iâm aware of the alternative of using a web > application architecture using something like Seaside (and now CodeParadise > too - thanks). > > But Iâm more interested at the moment in getting on top of a more > traditional application for these personal apps I want to build for my > desktop PC. > > My needs may change of course - and Iâm sure will look at doing some web > apps in the future... > > More importantly - YES - it is great to be back in a ST environment again > , and of course it is still so very very addictive !! > > [ Before resuming I spent some time familiarising myself with the > mainstream tools the industry seems to have adopted in the last 10-20 > years. I must say I was quite surprised and even disappointed about the > complexity, verbosity and incomprehensible syntax of some, and the > sloppiness (or is it flexibility?) of others. I really was not keen to have > to pick up one of those again. I had somehow hoped or expected that > language and environment design would have been much slicker and more fully > evolved by nowâ¦] > > Cheers Tim, and thanks for the suggestionâ¦ > > Mark > -- Russ Whaley whaley.russ(a)gmail.com

May 12, 2021

Re: Bootstrap4 package or Willow

by Sanjay Minni

Thank you Gabriel, As of now I do not have partial page updates to auto push back / sync. Any section of the page update / refresh is triggered explicitly by a button. I will take a shot at Willow for future possibility, hopefully it will not be a steep learning curve though the code in examples are at times daunting (Particularly to find out the overall application flow). gcotelli wrote > I think it mostly depends on the kind of app you're envisioning. > If you're going to do a lot of AJAX and partial updates to the page > without > navigating to new pages I must say that Willow is aimed to ease this kind > of interaction. > If you're thinking of not using so much AJAX, then stick with plain > Seaside > + astares/B4. > > For charting, you can also use ba-st/HighchartsSt wrapper with or without > Willow, or DuneSt/ChartJs. > > Regards, > Gabriel > > On Wed, May 12, 2021 at 7:02 AM Sanjay Minni < > sm@ > > wrote: > >> Hi >> >> this is a slightly open question but I want to have views to help me on >> choose the more appropriate Bootstrap4 package for a large Business >> Application: >> >> A. gh:astares/Seaside-Bootstrap4 ... and ... >> B. gh:ba-st/willow >> >> The application will have mostly >> - single form like UI >> - Form + Multi line UI >> - Flat reports (mostly Tabular text data) but export to PDF/Xlsx >> - Some graphs >> >> >> Thanks >> >> >> >> ----- >> cheers, >> Sanjay >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >> ----- cheers, Sanjay -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

May 12, 2021

Re: Bootstrap4 package or Willow

by Gabriel Cotelli

I think it mostly depends on the kind of app you're envisioning. If you're going to do a lot of AJAX and partial updates to the page without navigating to new pages I must say that Willow is aimed to ease this kind of interaction. If you're thinking of not using so much AJAX, then stick with plain Seaside + astares/B4. For charting, you can also use ba-st/HighchartsSt wrapper with or without Willow, or DuneSt/ChartJs. Regards, Gabriel On Wed, May 12, 2021 at 7:02 AM Sanjay Minni <sm(a)planage.com> wrote: > Hi > > this is a slightly open question but I want to have views to help me on > choose the more appropriate Bootstrap4 package for a large Business > Application: > > A. gh:astares/Seaside-Bootstrap4 ... and ... > B. gh:ba-st/willow > > The application will have mostly > - single form like UI > - Form + Multi line UI > - Flat reports (mostly Tabular text data) but export to PDF/Xlsx > - Some graphs > > > Thanks > > > > ----- > cheers, > Sanjay > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >

May 12, 2021

Bootstrap4 package or Willow

by Sanjay Minni

Hi this is a slightly open question but I want to have views to help me on choose the more appropriate Bootstrap4 package for a large Business Application: A. gh:astares/Seaside-Bootstrap4 ... and ... B. gh:ba-st/willow The application will have mostly - single form like UI - Form + Multi line UI - Flat reports (mostly Tabular text data) but export to PDF/Xlsx - Some graphs Thanks ----- cheers, Sanjay -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

May 12, 2021

Re: Looking for more non-trivial example application based on Spec2 to learn from...

by mark.odonoghue.2010＠gmail.com

Hi Tim Thanks for the suggestion - Iâm aware of the alternative of using a web application architecture using something like Seaside (and now CodeParadise too - thanks). But Iâm more interested at the moment in getting on top of a more traditional application for these personal apps I want to build for my desktop PC. My needs may change of course - and Iâm sure will look at doing some web apps in the future... More importantly - YES - it is great to be back in a ST environment again , and of course it is still so very very addictive !! \[ Before resuming I spent some time familiarising myself with the mainstream tools the industry seems to have adopted in the last 10-20 years. I must say I was quite surprised and even disappointed about the complexity, verbosity and incomprehensible syntax of some, and the sloppiness (or is it flexibility?) of others. I really was not keen to have to pick up one of those again. I had somehow hoped or expected that language and environment design would have been much slicker and more fully evolved by nowâ¦\] Cheers Tim, and thanks for the suggestionâ¦ Mark

May 12, 2021