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

Calypso openOnGroup?
by HernÃ¡n Morales Durand March 16, 2019

March 16, 2019

Hi, Is there any way to open a browser on a method group in Claypso? This was possible in Nautilus: Smalltalk tools browser openOnCategory: #compiling ofClass: Class Cheers, HernÃ¡n

2 2

Per project code formatting settings and policy
by Holger Freyther March 16, 2019

March 16, 2019

Hi! I found myself doing codereview and commenting on style (e.g. missing indention). It seems like a task that can be easily automated and in fact we have RBFormmatter/BlueInk to do it. What I didn't see is if a project can supply the style (instead of the image configuration)? How could this be achieved? holger

4 4

TelePharo in Tonel
by Torsten Bergmann March 15, 2019

March 15, 2019

Hi Denis, would it be possible to convert TelePharo to Tonel? https://github.com/pharo-ide/TelePharo Currently one gets load problem on Windows due to long file names and Tonel would solve that. Thanks T.

2 1

GPCE 2019: 1st Call for Papers - Athens, Greece; October 21-22
by Rodin Aarssen March 15, 2019

March 15, 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 Rennes) * 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

Pharo 7.0.2 is starting to appear suspect to me
by Tim Mackinnon March 15, 2019

March 15, 2019

I donât know if others are using Pharo 7.0.2 in anger - I was previously using 7.0.1 - but Iâm finding that having used it for a few hours now (doing things Iâve been doing for weeks in the older version) that its not as stable. I used to be able to delete a hundred classes a few times a day (when doing some testing) and it didnât blink - but 7.0.2 is now having announcement issues. I also keep getting the font problems much more frequently and Iâve had some strange lockups (which could be associated with the Mirage task switcher). But anyway - Iâm just calling it outâ¦ Tim

1 0

Corrupted fonts in P7 after loading Glamorous Toolkit
by Tim Mackinnon March 14, 2019

March 14, 2019

Hi - I just noticed that when I loaded the Glamorous toolkit and was playing around, when I went to look in the Pharo menus they are all corrupted (the odd character is some type of glyph). Opening a playground and doing some code completion shows that method names have the same random character glyphed. Anyone else seen this? Is is it something about loading GT? This is on OSX Tim

6 10

Pharo 7.0.2 osx from launcher has corrupted welcome screen?
by Tim Mackinnon March 14, 2019

March 14, 2019

Has anyone else noticed that the the newer 7.0.2 image (from launcher) has a corrupted welcome screen? This is on osx (high Sierra) from today. The image seems to work fine, its just that initial welcome screen? Did something get corrupted on the deployment? Tim

2 2

Is epicea on the roadmap for 8?
by Tim Mackinnon March 14, 2019

March 14, 2019

A few times now when trying to sort out issue, Iâve wanted to search for a particular class to understand what has happened and also to recover source code for it - the current epicea only has very general search and as it replaces the change.log (which was text and searchable) we need better search tools - unless Iâm missing something obvious. Tim

1 0

can I add a class to material design ?
by Roelof Wobben March 14, 2019

March 14, 2019

Hello, I wonder if I can add a custom class to a material design card so I can have a image on the left or a image on the top based on the dimisions of the image. Roelof

2 1

Does the blue ink formatter setting: 'Selector and argument combined in method signature max size' work?
by Tim Mackinnon March 14, 2019

March 14, 2019

Having done a bunch of refactoring on my code - I realised that the default settings for the code formatter arenât the greatest (and I know this is quite personal). So Iâve tweaked a few things (the default settings arenât bad but I donât understand why "retain black lines between statements" isnât on by default - as the alternative really gives us bad looking code. Ideally, there should be a number you can set - for max blanks to preserve, but the current 0 is not great). However - my question is how to stop smaller keyword messages from being wrapped? If I have the setting âmethod signature on multiple linesâ NOT checked (default), I understood that "Selector and argument combined in method signature max sizeâ would then be used to determine if a statement is wrapped or not? However even with big numbers a statement like: exercismSubmission := ExercismSubmission data: (self class sampleDataFor: 'test-ex' filenames: actualNames baseUrl: baseUrl). Always gets wrapped to: exercismSubmission := ExercismSubmission data: (self class sampleDataFor: 'test-ex' filenames: actualNames baseUrl: baseUrl). Is there some other setting I am missing? Or is this just a bug? Tim

1 0