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

2nd CfP: SLE 2024 - 17th ACM SIGPLAN International Conference on Software Language Engineering

by Andrei Chis

17th ACM SIGPLAN International Conference on Software Language Engineering (SLE 2024) October 20-21, 2024 Pasadena, California, United States --------------------------- Important Dates --------------------------- * Abstract Submissions: Fri 14 Jun, 2024 * Paper Submissions: Mon 24 Jun, 2024 * Authors Response Period: Mon 12 Aug - Sat 17 Aug, 2024 * Authors Notification: Fri 30 Aug 2024 * Conference: Sun 20 October - Mon 21 October 2024 (co-located with SPLASH) All dates are Anywhere on Earth (https://en.wikipedia.org/wiki/Anywhere_on_Earth) ------------------------------------------------------------------------ We are pleased to invite you to submit papers to the 17th ACM SIGPLAN International Conference on Software Language Engineering (SLE 2024), held in conjunction with SPLASH 2024. The conference will be hosted in Pasadena, California, United States on October 20-21, 2024. https://www.sleconf.org/2024/ https://2024.splashcon.org/track/sle-2024 Follow us on X: https://x.com/sleconf --------------------------- Topics of Interest --------------------------- SLE covers software language engineering in general, 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 * Validation of Software Language Tools and Implementations - Verification and formal methods for language tools and implementations - Testing techniques for language tools and implementations - Simulation techniques for language tools and implementations * Software Language Maintenance - Software language reuse - Language evolution - Language families and variability, language and software product lines * 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 * Domain-Specific Approaches for Any Aspects of SLE (analysis, design, implementation, validation, maintenance) * Empirical Studies and Experience Reports of Tools - User studies evaluating usability - Performance benchmarks - Industrial applications * Synergies between Language Engineering and Emerging/Promising Research Areas - AI and ML language engineering (e.g., ML compiler testing, code classification) - Quantum language engineering (e.g., language design for quantum machines) - Language engineering for cyber-physical systems, IoT, digital twins, etc. - Socio-technical systems and language engineering (e.g., language evolution to adapt to social requirements) - Etc. --------------------------- Types of Submissions --------------------------- SLE accepts the following types of papers: Research papers: These are âtraditionalâ papers detailing research contributions to SLE. Papers may range from 6 to 12 pages in length and may optionally include 2 further pages of bibliography/appendices. Papers will be reviewed with an understanding that some results do not need 12 full pages and may be fully described in fewer pages. New ideas/vision papers: These papers may describe new, unconventional software language engineering research positions or approaches that depart from standard practice. They can describe well-defined research ideas that are at an early stage of investigation. They could also provide new evidence to challenge common wisdom, present new unifying theories about existing SLE research that provides novel insight or that can lead to the development of new technologies or approaches, or apply SLE technology to radically new application areas. New ideas/vision papers must not exceed 5 pages and may optionally include 1 further page of bibliography/appendices. SLE Body of Knowledge: The SLE Body of Knowledge (SLEBoK) is a community-wide effort to provide a unique and comprehensive description of the concepts, best practices, tools, and methods developed by the SLE community. These papers can focus on, but are not limited to, methods, techniques, best practices, and teaching approaches. Papers in this category can have up to 20 pages, including bibliography/appendices. Tool papers: These papers focus on the tooling aspects often forgotten or neglected in research papers. A good tool paper focuses on practical insights that will likely 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 include an appendix with a demo outline/screenshots and/or a short video/screencast illustrating the tool. **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 on the SPLASH 2024 Website. --------------------------- Submission --------------------------- SLE 2024 has a single submission round for papers, including a rebuttal phase, where all authors of research papers will have the possibility of responding to the reviews on their submissions. Authors of accepted research papers will be invited to submit artifacts. --------------------------- Format --------------------------- Submissions have to use the ACM SIGPLAN Conference Format âacmartâ (https://sigplan.org/Resources/Author/#acmart-format) 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! 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. Accordingly, SLE will follow the double-blind process. Author names and institutions must 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. The submission website is: https://sle24.hotcrp.com --------------------------- Concurrent Submissions --------------------------- Papers must describe unpublished work that is not currently submitted for publication elsewhere as described by SIGPLANâs Republication Policy (https://www.sigplan.org/Resources/Policies/Republication/) Submitters should also be aware of ACMâs Policy and Procedures on Plagiarism (https://www.acm.org/publications/policies/plagiarism-overview) Submissions that violate these policies will be desk-rejected. --------------------------- Policy on Human Participant and Subject Research --------------------------- Authors conducting research involving human participants and subjects must ensure that their research complies with their local governing laws and regulations and the ACMâs general principles, as stated in the ACMâs Publications Policy on Research Involving Human Participants and Subjects (https://www.acm.org/publications/policies/research-involving-human-particip…) If submissions are found to be violating this policy, they will be rejected. --------------------------- 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 soundness, relevance, novelty, presentation, and replicability. New ideas/vision papers will be evaluated primarily concerning soundness, relevance, novelty, and presentation. SLEBoK papers will be reviewed on their soundness, relevance, originality, and presentation. Tool papers will be evaluated concerning relevance, presentation, and replicability. 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. For research papers, authors will get a chance to respond to the reviews before a final decision is made. --------------------------- Artifact Evaluation --------------------------- SLE will use an evaluation process to assess the quality of artifacts on which papers are based to foster the culture of experimental reproducibility. Authors of accepted research papers are invited to submit artifacts. For more information, please see the Artifact Evaluation (https://2024.splashcon.org/track/sle-2024#Artifact-Evaluation) page. --------------------------- Awards --------------------------- Distinguished paper: Award for the most notable paper, as determined by the PC chairs based on the recommendations of the program committee. 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. --------------------------- SLE and Doctoral Students --------------------------- SLE encourages students to submit to the SPLASH doctoral symposium. Authors of accepted doctoral symposium papers on SLE topics will also have the chance to present their work to the SLE audience. --------------------------- Organisation --------------------------- Chairs: * General chair: Ralf LÃ¤mmel, UniversitÃ¤t Koblenz, Germany * PC co-chair: Peter Mosses, Swansea University and Delft University of Technology, Netherlands * PC co-chair: Juliana Alves Pereira, PontifÃcia Universidade CatÃ³lica do Rio de Janeiro, Brazil * Artifact Evaluation co-chair: Johannes HÃ¤rtel, Software Languages Lab, Vrije Universiteit Brussel * Artifact Evaluation co-chair: Sergio Queiroz de Medeiros, Universidade Federal do Rio Grande do Norte * Publicity chair: Andrei Chis, feenk gmbh, Switzerland Program committee * Andrzej WÄsowski, IT University of Copenhagen * Anthony Anjorin, ZÃ¼hlke Engineering GmbH * Benoit Combemale, University of Rennes, Inria, CNRS, IRISA * Bernd Fischer, Stellenbosch University * Di Wang, Peking University * Dimitris Kolovos, University of York * Elias Castegren, Uppsala University * Elizabeth Scott, Royal Holloway University of London * Esther Guerra, Universidad AutÃ³noma de Madrid * Faezeh Khorram, Huawei Technologies * Fernando Magno QuintÃ£o Pereira, Federal University of Minas Gerais * Prof. Fiona Polack, University of Hull * GÃ¶rel Hedin, Lund University * Guido Salvaneschi, University of St. Gallen * JoÃ£o Saraiva, HASLab/INESC TEC, University of Minho * Johannes HÃ¤rtel, Software Languages Lab, Vrije Universiteit Brussel * Judith Michael, RWTH Aachen University * Manuel Wimmer, JKU Linz * Marc Feeley, UniversitÃ© de MontrÃ©al * Michel Steuwer, Technische UniversitÃ¤t Berlin * Paddy Krishnan, Oracle Labs * Ragnar Mogk, Technische UniversitÃ¤t Darmstadt * Riemer van Rozen, CWI * Roberto Ierusalimschy, PUC-Rio * Sergio Queiroz de Medeiros, Universidade Federal do Rio Grande do Norte * Shigeru Chiba, The University of Tokyo * Stefan Marr, University of Kent * Stephen Chong, Harvard University * TamÃ¡s SzabÃ³, GitHub Next * Thomas Degueule, CNRS * Thomas KÃ¼hn, Martin-Luther-University Halle-Wittenberg * L. Thomas van Binsbergen, University of Amsterdam * Tijs van der Storm, CWI & University of Groningen * Walter Cazzola, UniversitÃ degli Studi di Milano --------------------------- Contact --------------------------- For additional information, clarification, or answers to questions, please get in touch with the program co-chairs (P.D.Mosses at tudelft.nl and Juliana at inf.puc-rio.br).

May 31, 2024

This week (22/2024) on the Pharo Issue Tracker

by Marcus Denker

# Pharo 12 - Backport use of icon #smallPharo in #pharoItemsOn: for WorldState and #menuCommandOn: for ProfStef #16695 https://github.com/pharo-project/pharo/pull/16695 # Fixes - fix Reflectivity API #link:toAST: for metaclasses to fix debug points on class-side methods #16701 https://github.com/pharo-project/pharo/pull/16701 - Pharo13 fficalls athens cairo surface #16679 https://github.com/pharo-project/pharo/pull/16679 - Fix a small bug with FFI calls when passing 'NULL' as argument to the C function #16562 https://github.com/pharo-project/pharo/pull/16562 - eflectivity fixing bytecode to ast mapping #16489 https://github.com/pharo-project/pharo/pull/16489 # Improvements - Add libgit 1.8 support for Pharo 13 #86 https://github.com/pharo-vcs/libgit2-pharo-bindings/pull/86 - It should be possible to reset a ZnCharacterReadStream #16707 https://github.com/pharo-project/pharo/pull/16707 - Make #withCloseBox and #withPinBox on MenuTitleMorph use a FormSet for the button label #16696 https://github.com/pharo-project/pharo/pull/16696 - fix #needRequestorScope of StDebuggerContextInteractionModel so that its bindings can be used when evaluating code in the debugger #762 https://github.com/pharo-spec/NewTools/pull/762 - Adopt to new spec #761 https://github.com/pharo-spec/NewTools/pull/761 - Adding entry completion setter to SpRequestDialog #1540 https://github.com/pharo-spec/Spec/pull/1540 # Cleanups - Cleanup TraitTest>>#testRemovingTraitsRemoveTraitedClassMethodsWithSubclasses #16717 https://github.com/pharo-project/pharo/pull/16717 - Cleanup ReOverridingExtentsionMethod>>#basicCheck: #16715 https://github.com/pharo-project/pharo/pull/16715 - Fix lint issue on ZnEncodedStream #16713 https://github.com/pharo-project/pharo/pull/16713 - Fix lint issues on ZnEncodedReadStream #16711 https://github.com/pharo-project/pharo/pull/16711 - Cleanup: ZnCharacterEncoder, ZnEncodedStream, ZnEncodedReadStream and ZnEncodedWriteStream should be abstract classes #16709 https://github.com/pharo-project/pharo/pull/16709

May 31, 2024

Re: Recent Pharo's seem to lose first keystroke when you swap to them to paste?

by Tim Mackinnon

It's very stange - and it seems many people experience it from comments on the submitted but - although it seems an OSX problem (so far) and one that has happened possibly in P9 or P10. Perhaps we can narrow it down enough to figure out the cause (and it occurs to me to see if GT has the same issue). Tim On Wed, 29 May 2024, at 12:29 PM, stephane ducasse wrote: > Tx > I did not know that pasting twice was workingâ¦ > How a strange bug. > > S > >> On 27 May 2024, at 22:32, Tim Mackinnon <tim(a)testit.works> wrote: >> >> I've submitted the issue https://github.com/pharo-project/pharo/issues/16700 and noted other comments >> >> On Mon, 27 May 2024, at 5:02 PM, Tim Mackinnon wrote: >>> >>> It would be handy to know if itâs just macOS - but Iâll write up an issue this evening. >>> >>> Thanks for confirming. >>> >>> Tim >>> >>> >>>> On 27 May 2024, at 16:01, Koen De Hondt <koen(a)all-objects-all-the-time.st> wrote: >>>> ï»¿I have suffered from copy & paste issues like this for a long time, in P11 and P12. >>>> I always have trouble with copying text from an image. I am already used to pressing Command-C twice ð >>>> >>>> I use a M2 Mac with MacOS 14.5, but it happened on earlier versions of MacOS as well. >>>> >>>> Koen >>>> >>>>> On 27 May 2024, at 15:48, Noury Bouraqadi <bouraqadi(a)gmail.com> wrote: >>>>> >>>>> Same bug on P11 with MacOS. >>>>> >>>>> On May 27 2024, at 3:44 pm, Tim Mackinnon <tim(a)testit.works> wrote: >>>>>> For a while I've noticed that every time I try and copy some text from a web browser or email and then paste it into pharo the first time it fails - and then thinking I didn't copy, I try it again and then realise that I have to paste twice - as the first one doesn't work. >>>>>> >>>>>> This didn't seem to do this in Pharo 9 (maybe 10) but its definitely the case in Pharo 11 and Pharo 12. This is on OSX (14.x) so I'm wondering if the same occurs in Windows or Linux or if its just my laptop? Its quite annoying and I'm wondering if it might be a side effect from the gradual UI changes in Pharo? >>>>>> >>>>>> I've looked in the issues tracker - but its a tricky thing to search for - and so I wanted to canvas experience and then will report it. >>>>>> >>>>>> Tim > > StÃ©phane Ducasse > http://stephane.ducasse.free.fr > 06 30 93 66 73 > > "If you knew today was your last day on earth, what would you do differently? ....ESPECIALLY if, by doing something different, today might not be your last day on earth.â Calvin & Hobbes > >

May 29, 2024

Re: Recent Pharo's seem to lose first keystroke when you swap to them to paste?

by stephane ducasse

Tx I did not know that pasting twice was workingâ¦ How a strange bug. S > On 27 May 2024, at 22:32, Tim Mackinnon <tim(a)testit.works> wrote: > > I've submitted the issue https://github.com/pharo-project/pharo/issues/16700 and noted other comments > > On Mon, 27 May 2024, at 5:02 PM, Tim Mackinnon wrote: >> >> It would be handy to know if itâs just macOS - but Iâll write up an issue this evening. >> >> Thanks for confirming. >> >> Tim >> >> >>> On 27 May 2024, at 16:01, Koen De Hondt <koen(a)all-objects-all-the-time.st> wrote: >>> ï»¿I have suffered from copy & paste issues like this for a long time, in P11 and P12. >>> I always have trouble with copying text from an image. I am already used to pressing Command-C twice ð >>> >>> I use a M2 Mac with MacOS 14.5, but it happened on earlier versions of MacOS as well. >>> >>> Koen >>> >>>> On 27 May 2024, at 15:48, Noury Bouraqadi <bouraqadi(a)gmail.com> wrote: >>>> >>>> Same bug on P11 with MacOS. >>>> >>>> On May 27 2024, at 3:44 pm, Tim Mackinnon <tim(a)testit.works> wrote: >>>> For a while I've noticed that every time I try and copy some text from a web browser or email and then paste it into pharo the first time it fails - and then thinking I didn't copy, I try it again and then realise that I have to paste twice - as the first one doesn't work. >>>> >>>> This didn't seem to do this in Pharo 9 (maybe 10) but its definitely the case in Pharo 11 and Pharo 12. This is on OSX (14.x) so I'm wondering if the same occurs in Windows or Linux or if its just my laptop? Its quite annoying and I'm wondering if it might be a side effect from the gradual UI changes in Pharo? >>>> >>>> I've looked in the issues tracker - but its a tricky thing to search for - and so I wanted to canvas experience and then will report it. >>>> >>>> Tim StÃ©phane Ducasse http://stephane.ducasse.free.fr 06 30 93 66 73 "If you knew today was your last day on earth, what would you do differently? ....ESPECIALLY if, by doing something different, today might not be your last day on earth.â Calvin & Hobbes

May 29, 2024

Re: Recent Pharo's seem to lose first keystroke when you swap to them to paste?

by Tim Mackinnon

I've submitted the issue https://github.com/pharo-project/pharo/issues/16700 and noted other comments On Mon, 27 May 2024, at 5:02 PM, Tim Mackinnon wrote: > > It would be handy to know if itâs just macOS - but Iâll write up an issue this evening. > > Thanks for confirming. > > Tim > > >> On 27 May 2024, at 16:01, Koen De Hondt <koen(a)all-objects-all-the-time.st> wrote: >> ï»¿I have suffered from copy & paste issues like this for a long time, in P11 and P12. >> I always have trouble with copying text from an image. I am already used to pressing Command-C twice ð >> >> I use a M2 Mac with MacOS 14.5, but it happened on earlier versions of MacOS as well. >> >> Koen >> >>> On 27 May 2024, at 15:48, Noury Bouraqadi <bouraqadi(a)gmail.com> wrote: >>> >>> Same bug on P11 with MacOS. >>> >>> On May 27 2024, at 3:44 pm, Tim Mackinnon <tim(a)testit.works> wrote: >>>> For a while I've noticed that every time I try and copy some text from a web browser or email and then paste it into pharo the first time it fails - and then thinking I didn't copy, I try it again and then realise that I have to paste twice - as the first one doesn't work. >>>> >>>> This didn't seem to do this in Pharo 9 (maybe 10) but its definitely the case in Pharo 11 and Pharo 12. This is on OSX (14.x) so I'm wondering if the same occurs in Windows or Linux or if its just my laptop? Its quite annoying and I'm wondering if it might be a side effect from the gradual UI changes in Pharo? >>>> >>>> I've looked in the issues tracker - but its a tricky thing to search for - and so I wanted to canvas experience and then will report it. >>>> >>>> Tim

May 27, 2024

Re: Recent Pharo's seem to lose first keystroke when you swap to them to paste?

by Davide Varvello

Tim, Also Pharo10 has this bug (mac m2, sonoma). Thanks for your report! Cheers DavideÂ On Monday, May 27, 2024 at 03:45:46 PM GMT+2, Tim Mackinnon <tim(a)testit.works> wrote: For a while I've noticed that every time I try and copy some text from a web browser or email and then paste it into pharo the first time it fails - and then thinking I didn't copy, I try it again and then realise that I have to paste twice - as the first one doesn't work. This didn't seem to do this in Pharo 9 (maybe 10) but its definitely the case in Pharo 11 and Pharo 12. This is on OSX (14.x) so I'm wondering if the same occurs in Windows or Linux or if its just my laptop? Its quite annoying and I'm wondering if it might be a side effect from the gradual UI changes in Pharo? I've looked in the issues tracker - but its a tricky thing to search for - and so I wanted to canvas experience and then will report it. Tim

May 27, 2024

Re: Recent Pharo's seem to lose first keystroke when you swap to them to paste?

by Yanni Chiu

Itâs been happening for at least four years across updates of Pharo and MacOS. At first it seemed random, but it is now so frequent as to require pressing cmd-c twice, out of habit. On Mon, May 27, 2024 at 10:01 AM Koen De Hondt < koen(a)all-objects-all-the-time.st> wrote: > I have suffered from copy & paste issues like this for a long time, in P11 > and P12. > I always have trouble with copying text from an image. I am already used > to pressing Command-C twice ð > > I use a M2 Mac with MacOS 14.5, but it happened on earlier versions of > MacOS as well. > > Koen > > On 27 May 2024, at 15:48, Noury Bouraqadi <bouraqadi(a)gmail.com> wrote: > > Same bug on P11 with MacOS. > > On May 27 2024, at 3:44 pm, Tim Mackinnon <tim(a)testit.works> wrote: > > For a while I've noticed that every time I try and copy some text from a > web browser or email and then paste it into pharo the first time it fails - > and then thinking I didn't copy, I try it again and then realise that I > have to paste twice - as the first one doesn't work. > > This didn't seem to do this in Pharo 9 (maybe 10) but its definitely the > case in Pharo 11 and Pharo 12. This is on OSX (14.x) so I'm wondering if > the same occurs in Windows or Linux or if its just my laptop? Its quite > annoying and I'm wondering if it might be a side effect from the gradual UI > changes in Pharo? > > I've looked in the issues tracker - but its a tricky thing to search for - > and so I wanted to canvas experience and then will report it. > > Tim > > >

May 27, 2024

Re: Recent Pharo's seem to lose first keystroke when you swap to them to paste?

by Tim Mackinnon

It would be handy to know if itâs just macOS - but Iâll write up an issue this evening. Thanks for confirming. Tim > On 27 May 2024, at 16:01, Koen De Hondt <koen(a)all-objects-all-the-time.st> wrote: > > ï»¿I have suffered from copy & paste issues like this for a long time, in P11 and P12. > I always have trouble with copying text from an image. I am already used to pressing Command-C twice ð > > I use a M2 Mac with MacOS 14.5, but it happened on earlier versions of MacOS as well. > > Koen > >> On 27 May 2024, at 15:48, Noury Bouraqadi <bouraqadi(a)gmail.com> wrote: >> >> Same bug on P11 with MacOS. >> >> On May 27 2024, at 3:44 pm, Tim Mackinnon <tim(a)testit.works> wrote: >> For a while I've noticed that every time I try and copy some text from a web browser or email and then paste it into pharo the first time it fails - and then thinking I didn't copy, I try it again and then realise that I have to paste twice - as the first one doesn't work. >> >> This didn't seem to do this in Pharo 9 (maybe 10) but its definitely the case in Pharo 11 and Pharo 12. This is on OSX (14.x) so I'm wondering if the same occurs in Windows or Linux or if its just my laptop? Its quite annoying and I'm wondering if it might be a side effect from the gradual UI changes in Pharo? >> >> I've looked in the issues tracker - but its a tricky thing to search for - and so I wanted to canvas experience and then will report it. >> >> Tim >

May 27, 2024

Re: Recent Pharo's seem to lose first keystroke when you swap to them to paste?

by Koen De Hondt

I have suffered from copy & paste issues like this for a long time, in P11 and P12. I always have trouble with copying text from an image. I am already used to pressing Command-C twice ð I use a M2 Mac with MacOS 14.5, but it happened on earlier versions of MacOS as well. Koen > On 27 May 2024, at 15:48, Noury Bouraqadi <bouraqadi(a)gmail.com> wrote: > > Same bug on P11 with MacOS. > > On May 27 2024, at 3:44 pm, Tim Mackinnon <tim(a)testit.works> wrote: > For a while I've noticed that every time I try and copy some text from a web browser or email and then paste it into pharo the first time it fails - and then thinking I didn't copy, I try it again and then realise that I have to paste twice - as the first one doesn't work. > > This didn't seem to do this in Pharo 9 (maybe 10) but its definitely the case in Pharo 11 and Pharo 12. This is on OSX (14.x) so I'm wondering if the same occurs in Windows or Linux or if its just my laptop? Its quite annoying and I'm wondering if it might be a side effect from the gradual UI changes in Pharo? > > I've looked in the issues tracker - but its a tricky thing to search for - and so I wanted to canvas experience and then will report it. > > Tim

May 27, 2024

Re: Recent Pharo's seem to lose first keystroke when you swap to them to paste?

by Noury Bouraqadi

Same bug on P11 with MacOS. On May 27 2024, at 3:44 pm, Tim Mackinnon <tim(a)testit.works> wrote: > For a while I've noticed that every time I try and copy some text from a web browser or email and then paste it into pharo the first time it fails - and then thinking I didn't copy, I try it again and then realise that I have to paste twice - as the first one doesn't work. > > > This didn't seem to do this in Pharo 9 (maybe 10) but its definitely the case in Pharo 11 and Pharo 12. This is on OSX (14.x) so I'm wondering if the same occurs in Windows or Linux or if its just my laptop? Its quite annoying and I'm wondering if it might be a side effect from the gradual UI changes in Pharo? > > I've looked in the issues tracker - but its a tricky thing to search for - and so I wanted to canvas experience and then will report it. > > Tim

May 27, 2024

Recent Pharo's seem to lose first keystroke when you swap to them to paste?

by Tim Mackinnon

For a while I've noticed that every time I try and copy some text from a web browser or email and then paste it into pharo the first time it fails - and then thinking I didn't copy, I try it again and then realise that I have to paste twice - as the first one doesn't work. This didn't seem to do this in Pharo 9 (maybe 10) but its definitely the case in Pharo 11 and Pharo 12. This is on OSX (14.x) so I'm wondering if the same occurs in Windows or Linux or if its just my laptop? Its quite annoying and I'm wondering if it might be a side effect from the gradual UI changes in Pharo? I've looked in the issues tracker - but its a tricky thing to search for - and so I wanted to canvas experience and then will report it. Tim

May 27, 2024

Re: [SOLVED] Shortcut CMD-v for version history

by Davide Varvello

ð On Saturday, May 25, 2024 at 07:07:24 PM GMT+2, stephane ducasse <stephane.ducasse(a)inria.fr> wrote: Since this mailing-list is not a bug tracker I created an issue with the feature. https://github.com/pharo-project/pharo/issues/16694 I will not comment this but smart people will easily guess. Now Pharo is more important than that. S > On 25 May 2024, at 06:42, Davide Varvello via Pharo-users <pharo-users(a)lists.pharo.org> wrote: > > Hi, > If you too miss some shortcuts like... cmd-v to show the versions of a method, here is the solution, you have to add methodShortcutActivation to SycShowMethodVersionCommand class: > > SycShowMethodVersionCommand class >> methodShortcutActivation > <classAnnotation> > ^ CmdShortcutActivation by: $v meta for: ClyMethod asCalypsoItemContext > > HTH > Cheers > Davide StÃ©phane Ducasse http://stephane.ducasse.free.fr 06 30 93 66 73 "If you knew today was your lastÂ day on earth, what wouldÂ youÂ do differently? ....ESPECIALLYÂ if, by doing somethingÂ different,Â today mightÂ notÂ be your last dayÂ on earth.â CalvinÂ & Hobbes

May 26, 2024

Re: [SOLVED] Shortcut CMD-v for version history

by stephane ducasse

Since this mailing-list is not a bug tracker I created an issue with the feature. https://github.com/pharo-project/pharo/issues/16694 I will not comment this but smart people will easily guess. Now Pharo is more important than that. S > On 25 May 2024, at 06:42, Davide Varvello via Pharo-users <pharo-users(a)lists.pharo.org> wrote: > > Hi, > If you too miss some shortcuts like... cmd-v to show the versions of a method, here is the solution, you have to add methodShortcutActivation to SycShowMethodVersionCommand class: > > SycShowMethodVersionCommand class >> methodShortcutActivation > <classAnnotation> > ^ CmdShortcutActivation by: $v meta for: ClyMethod asCalypsoItemContext > > HTH > Cheers > Davide StÃ©phane Ducasse http://stephane.ducasse.free.fr 06 30 93 66 73 "If you knew today was your last day on earth, what would you do differently? ....ESPECIALLY if, by doing something different, today might not be your last day on earth.â Calvin & Hobbes

May 25, 2024

[SOLVED] Shortcut CMD-v for version history

by Davide Varvello

Hi, If you too miss some shortcuts like... cmd-v to show the versions of a method, here is the solution, you have to add methodShortcutActivation to SycShowMethodVersionCommand class: SycShowMethodVersionCommand class >> methodShortcutActivation <classAnnotation> ^ CmdShortcutActivation by: $v meta for: ClyMethod asCalypsoItemContext HTH Cheers Davide

May 25, 2024

Re: 3D graphics?

by Noury Bouraqadi

Hi Kasper, I never did investigate using Pharo to building STL files. But, I did used PharoJS to build a 3D scene using the three.js Javascript library. The code is part of PharoJS examples Here is a live demo https://pharojs.org/Demos/PjThreeJsDemo/index.html More about ThreeJS: https://threejs.org/ I'll be happy to help with it and discuss anything 3D printing. I am fond of 3D printing since I bought my first printer in 2017. You can find some of my prints https://nootrix.com/tag/3d-printing/ Noury On May 24 2024, at 2:28 pm, Kasper Osterbye <kasper.osterbye(a)gmail.com> wrote: > Cheers all > > I am looking for classes which can be used to build 3D pictures. Spheres, Boxes, etc. > It is a fun thing for me to build, but on the other hand, if it is already done, I will use them. > > Also, I am interested in 3D figures being outputtet in STL files. Is that done? It is an easier thing for me to build (have done some work already). > I want the stl format as I can pass that on to 3D printers. Are there anyone else who have worked from Pharo to 3D printing (prusa for example). > Best, Kasper

May 24, 2024

3D graphics?

by Kasper Osterbye

Cheers all I am looking for classes which can be used to build 3D pictures. Spheres, Boxes, etc. It is a fun thing for me to build, but on the other hand, if it is already done, I will use them. Also, I am interested in 3D figures being outputtet in STL files. Is that done? It is an easier thing for me to build (have done some work already). I want the stl format as I can pass that on to 3D printers. Are there anyone else who have worked from Pharo to 3D printing (prusa for example). Best, Kasper

May 24, 2024

This week (21/2024) on the Pharo Issue Tracker

by Marcus Denker

# Pharo 11 backports - P11 - During compilation there are redundant allocation of collections #16485 https://github.com/pharo-project/pharo/pull/16485 # Pharo 12 - Fix for pharo/pharo-project#16677: libgit2 library not listed in LGitLibrary>>#unix64LibraryName #85 https://github.com/pharo-vcs/libgit2-pharo-bindings/pull/85 # Fixes - 15652-Check-and-add-test-for--CompiledCodenewFrom #16663 https://github.com/pharo-project/pharo/pull/16663 - Debug points cleaning fixing #16670 https://github.com/pharo-project/pharo/pull/16670 - Change #pharoItemsOn: for WorldState and #menuCommandOn: for ProfStef to use the icon #smallPharo #16496 https://github.com/pharo-project/pharo/pull/16496 # Scriptable Debugger - Migrate to Tonel V3 #97 https://github.com/pharo-spec/ScriptableDebugger/pull/97 - Cleanup: do not use #notNil, use #isNotNil instead #96 https://github.com/pharo-spec/ScriptableDebugger/pull/96 # Rules / Refactoring Engine - Make class abstract driver #16347 https://github.com/pharo-project/pharo/pull/16347 - proposition for a potential new rule: use deny: instead of assert:equals:false #16668 https://github.com/pharo-project/pharo/pull/16668 # Cleanup - Debug point refactoring #757 https://github.com/pharo-spec/NewTools/pull/757 - Remove empty Manifests from baseline packages, synchronize on the tagâ¦ #16537 https://github.com/pharo-project/pharo/pull/16537 - Remove VariableLayout from tests #16686 https://github.com/pharo-project/pharo/pull/16686 - 16680-Zinc-uses-old-Announcers-API #16681 https://github.com/pharo-project/pharo/pull/16681 - 16608 cleanup crown initialize should call super initialize #16676 https://github.com/pharo-project/pharo/pull/16676 - Deprecate RPackageSet #16675 https://github.com/pharo-project/pharo/pull/16675 - Update call to a deprecated class #16671 https://github.com/pharo-project/pharo/pull/16671 - fixes #16610: Cleanup: simple typo in Crown class comment #16666 https://github.com/pharo-project/pharo/pull/16666

May 24, 2024

DATE CORRECTION - UKSTUG Meeting - Javier Pimas -- Live Metacircular Runtimes: The case of Egg Smalltalk - 29 May 2024

by UK Smalltalk

Egg is a new Smalltalk dialect that was designed from scratch to incorporate some interesting features: A module system with namespaces that replaces the old-good Smalltalk global. Dynamic identifiers, which are bound lazily similarly to how methods are lazily bound. A multi-VM architecture, with different VM implementations written in C++, Pharo, JavaScript and Egg. The Egg-in-Egg VM is special in that the VM component is just another module of the system, creating what we have named Live Metacircular Runtimes (LMRs) [1]. The most interesting characteristic of LMRs in Smalltalk is that they can be developed using standard Smalltalk tools, which shorten feedback loops when doing VM development. During the talk I'll show a little bit about Egg and its LMR, and how not only VM developers get more productive when writing VMs, but also application developers can better understand what the VM does behind the scenes. [1] https://arxiv.org/abs/2312.16973 - Live Objects All The Way Down: Removing the Barriers between Applications and Virtual Machines Javier Pimas is a fan of high-level low-level programming. He has been successfully mixing Smalltalk and assembly code for more than a decade. Within Bee Smalltalk, SqueakNOS and now Egg Smalltalk projects he has been trying to make live-programming of system-level concerns more practical to application programmers. Javier works for Labware and Quorum Software, where he applies his expertise to real-world challenges while pursuing a PhD in Computer Science at Buenos Aires University. This will be an online meeting from home. If you'd like to join us, please sign up in advance on the meeting's Meetup page ( https://www.meetup.com/ukstug/events/300511322/ ) to receive the meeting details. Donât forget to bring your laptop and drinks!

May 22, 2024

UKSTUG Meeting - Javier Pimas -- Live Metacircular Runtimes: The case of Egg Smalltalk - 29 June 2024

by UK Smalltalk

Egg is a new Smalltalk dialect that was designed from scratch to incorporate some interesting features: A module system with namespaces that replaces the old-good Smalltalk global. Dynamic identifiers, which are bound lazily similarly to how methods are lazily bound. A multi-VM architecture, with different VM implementations written in C++, Pharo, JavaScript and Egg. The Egg-in-Egg VM is special in that the VM component is just another module of the system, creating what we have named Live Metacircular Runtimes (LMRs) [1]. The most interesting characteristic of LMRs in Smalltalk is that they can be developed using standard Smalltalk tools, which shorten feedback loops when doing VM development. During the talk I'll show a little bit about Egg and its LMR, and how not only VM developers get more productive when writing VMs, but also application developers can better understand what the VM does behind the scenes. [1] https://arxiv.org/abs/2312.16973 - Live Objects All The Way Down: Removing the Barriers between Applications and Virtual Machines Javier Pimas is a fan of high-level low-level programming. He has been successfully mixing Smalltalk and assembly code for more than a decade. Within Bee Smalltalk, SqueakNOS and now Egg Smalltalk projects he has been trying to make live-programming of system-level concerns more practical to application programmers. Javier works for Labware and Quorum Software, where he applies his expertise to real-world challenges while pursuing a PhD in Computer Science at Buenos Aires University. This will be an online meeting from home. If you'd like to join us, please sign up in advance on the meeting's Meetup page ( https://www.meetup.com/ukstug/events/300511322/ ) to receive the meeting details. Donât forget to bring your laptop and drinks!

May 22, 2024

[ANN] Package Formulas v1

by HernÃ¡n Morales Durand

Hi everyone. I've updated package formulas to work with Pharo 12 and Pharo 13. You can find the project here: https://github.com/hernanmd/package-formulas Let me know if there's any features you would like to see implemented. Cheers, HernÃ¡n

May 17, 2024

This week (20/2024) on the Pharo Issue Tracker

by Marcus Denker

# Pharo 12 - Backport use of FormSet for ToggleMenuItemMorph submenu markers #16631 https://github.com/pharo-project/pharo/pull/16631 # Ehancements - [Enhancement] Add "copy class name" to extras menu in Calypse #16635 https://github.com/pharo-project/pharo/pull/16635 - Add missing RGGlobalVariable>>isInstanceVariable #16644 https://github.com/pharo-project/pharo/pull/16644 - Introduce CompiledMethod>>#isInstanceSide #16626 https://github.com/pharo-project/pharo/pull/16626 # Fixes - Issue 16430 - String>> asSymbol no protected against concurrent access (alternative solution) #16565 https://github.com/pharo-project/pharo/pull/16565 - [Bug]: Date>>#addMonths: should Respect Offset #16603 https://github.com/pharo-project/pharo/pull/16603 - sort subdirectories in the same order as the file tree table #748 https://github.com/pharo-spec/NewTools/pull/748 # VM - Fixed VirtualMachine 76 and 78 parameters #16641 https://github.com/pharo-project/pharo/pull/16641 - Do not retain any selectors in CogAbstractInstruction #798 https://github.com/pharo-project/pharo-vm/pull/798 - add tests for type harmonization #807 https://github.com/pharo-project/pharo-vm/pull/807 - remove warning because of type and unsigned shift issues #800 https://github.com/pharo-project/pharo-vm/pull/800 - Fixed ntb page selection change announcement if built without pages #1542 https://github.com/pharo-spec/Spec/pull/1542 # Package Structure - Sindarin/ScriptableDebugger should be listed as external project #16653 https://github.com/pharo-project/pharo/pull/16653 - Sindarin in Pharo13 need to be loaded from Pharo13 branch of ScriptableDebugger (and not Pharo12 branch) #751 https://github.com/pharo-spec/NewTools/pull/751 - Simplify Calypso packaging #16602 https://github.com/pharo-project/pharo/pull/16602 - Cleanup: CoverageCollectorTest should be in an own test package #16613 https://github.com/pharo-project/pharo/pull/16613 # Rules - proposition rule for nil branch #16547 https://github.com/pharo-project/pharo/pull/16547 - [Enhancement] Add a rule ReBaselineProperlyPackagedRule #16630 https://github.com/pharo-project/pharo/pull/16630 - [Enhancement] Add a rule ReBaselineWithProperSuperclassRule #16633 https://github.com/pharo-project/pharo/pull/16633 - proposition for a potential new rule: useless ifTrue:ifFalse: #16638 https://github.com/pharo-project/pharo/pull/16638 - add ReStatementsAfterReturnConditionalRule #16640 https://github.com/pharo-project/pharo/pull/16640 - Review ReClassNotCategorizedRuleTest>>#testRule #16649 https://github.com/pharo-project/pharo/pull/16649 - Improve ReBaselineProperlyPackagedRule and ReBaselineWithProperSuperclassRule and cover with tests #16648 https://github.com/pharo-project/pharo/pull/16648 - Enhancement: Provide a lint rule to check for a "super initialize" call in instance side #initialize methods #16615 https://github.com/pharo-project/pharo/pull/16615 - tests for rules from the General-Rules package #16474 https://github.com/pharo-project/pharo/pull/16474 # Cleanups - Reduce references to Undeclared global variable #16642 https://github.com/pharo-project/pharo/pull/16642 - Remove deprecated way to access the global package organizer #754 https://github.com/pharo-spec/NewTools/pull/754 - Remove the package Deprecated12, introduce package Deprecated13 #16538 https://github.com/pharo-project/pharo/pull/16538 - proposition refactoring -> Cleanup: 2 duplicated methods in FreeType #16583 https://github.com/pharo-project/pharo/pull/16583 - Clean up in SDL_Texture and SDL_Renderer #16601 https://github.com/pharo-project/pharo/pull/16601 - Simplify script pragma for FinderUI #16623 https://github.com/pharo-project/pharo/pull/16623 - CommentTestCase should be moved to PharoDocComment-Tests #16619 https://github.com/pharo-project/pharo/pull/16619 - Package "System-DependenciesTests" should be "System-Dependencies-Tests" #16621 https://github.com/pharo-project/pharo/pull/16621 - Cleanup: AthensTransformTest>>transformClass should be in accessing #16628 https://github.com/pharo-project/pharo/pull/16628 - Fix lint in ReShouldSendSuperSetUpAsFirstMessage class>>#checksMethod (second PR) #16643 https://github.com/pharo-project/pharo/pull/16643 - Remove part of ReAsClassRule about #asClass #16658 https://github.com/pharo-project/pharo/pull/16658 - Cleanup: Remove deprecated announcement #SnapshotDone in SnapshotOperation>>#performSnapshot for Pharo 13 #16657 https://github.com/pharo-project/pharo/pull/16657 - Cleanup: unnecessary class BlLoadProjectWorldMenu #16655 https://github.com/pharo-project/pharo/pull/16655 - SourceFile>>#isOpen should use isNotNil #16651 https://github.com/pharo-project/pharo/pull/16651 - Remove Gofer #16606 https://github.com/pharo-project/pharo/pull/16606 - Remove reference to a deprecated class #1822 https://github.com/pharo-vcs/iceberg/pull/1822 - Fixing call to deprecated code #749 https://github.com/pharo-spec/NewTools/pull/749 - Use isNotNil instead notNil in initializePresenters #753 https://github.com/pharo-spec/NewTools/pull/753 # Website - Update community.md: Social Media Section #74 https://github.com/pharo-project/pharo-website/pull/74 - Update community.md: update tweet suggestion form #73 https://github.com/pharo-project/pharo-website/pull/73 - Update Companies.md #72 https://github.com/pharo-project/pharo-website/pull/72 - Update 2024-04-26-pharo12-released.md: fix typy #69 https://github.com/pharo-project/pharo-website/pull/69

May 17, 2024

Re: Getting started with the easy projects

by Richard O'Keefe

Life has been getting in the way. Thanks for the "Managing your code" chapter. I've got that now. On Fri, 17 May 2024 at 00:00, stephane ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi richard > > I wanted to tell you that there is also a chapter about how to contribute > in the Managing your code > [image: preview.png] > > 2020-05-12-ManageCode > <https://books.pharo.org/booklet-ManageCode/pdf/2020-05-12-ManageCode.pdf> > PDF Document Â· 2,1 MB > <https://books.pharo.org/booklet-ManageCode/pdf/2020-05-12-ManageCode.pdf> > <https://books.pharo.org/booklet-ManageCode/pdf/2020-05-12-ManageCode.pdf> > > > S > > > On 4 May 2024, at 09:10, stephane ducasse <stephane.ducasse(a)inria.fr> > wrote: > > Hi richard > > I can write something once you have a look at the video and let me know > what you would like to know. > > S > > On 3 May 2024, at 14:27, Sebastian Jordan Montano < > sebastian.jordan(a)inria.fr> wrote: > > You have the guide how to contribute to a fix in Pharo: > https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo > > Sebastian > > ----- Mail original ----- > > De: "Richard O'Keefe" <raoknz(a)gmail.com> > Ã: "Any question about pharo is welcome" <pharo-users(a)lists.pharo.org> > EnvoyÃ©: Vendredi 3 Mai 2024 12:28:16 > Objet: [Pharo-users] Re: Getting started with the easy projects > > > What I was really asking was about the very basic mechanics of it. > "Where are the instructions about how to sign up" > meant "do I have to register somewhere and if so where and how?" > "Where are the instructions about what to do" > meant "suppose I have registered and have the latest Pharo open > on my laptop; how do I connect to the repository, how do I submit > a change for review?" I have been playing with Pharo since version 1 > but I've never actually connected to a repository. > > I think a "Complete Idiot's Guide to Getting Started with Distributed > Development in Phraro" probably already exists somewhere, I just > don't know where to look for it. > > On Sat, 27 Apr 2024 at 21:05, stephane ducasse > <stephane.ducasse(a)inria.fr> wrote: > > > Hi richard > > https://github.com/orgs/pharo-project/projects/8 > lists some easy projects. I'd like to make a contribution. > > > Cool. > The first thing I suggest is to take the stupidiest issue like adding a > comment > in a method > or fixing a badly written comment and make a PR. > I like to do this trivial things because there are easy to give a positive > slant > on my energy. > > Where are the instructions on how to sign up and what > to do? Fair warning, I'll probably need a bit of hand-holdingâ¦ > > > For the contributions feel free to pick what you like > > - Some easy things are: better comments, improving test coverage > - Now Iâm pretty sure that we can get collection improvements > - This one could interest you: underscores in numeric literals > https://github.com/pharo-project/pheps/pull/18/files > We had long design discussions and I think that the result is good but we > never > got the time to implement it. > > S > > > > > StÃ©phane Ducasse > http://stephane.ducasse.free.fr > 06 30 93 66 73 > > "If you knew today was your last day on earth, what would you do > differently? > ....ESPECIALLY if, by doing something different, today might not be your > last > day on earth.â Calvin & Hobbes > > > > > > StÃ©phane Ducasse > http://stephane.ducasse.free.fr > 06 30 93 66 73 > > "If you knew today was your last day on earth, what would you do > differently? ....ESPECIALLY if, by doing something different, today > might not be your last day on earth.â Calvin & Hobbes > > > > > > > StÃ©phane Ducasse > http://stephane.ducasse.free.fr > 06 30 93 66 73 > > "If you knew today was your last day on earth, what would you do > differently? ....ESPECIALLY if, by doing something different, today > might not be your last day on earth.â Calvin & Hobbes > > > > > >

May 17, 2024

Re: Getting started with the easy projects

by stephane ducasse

Hi richard I wanted to tell you that there is also a chapter about how to contribute in the Managing your code https://books.pharo.org/booklet-ManageCode/pdf/2020-05-12-ManageCode.pdfï¿¼ 2020-05-12-ManageCode PDF Document Â· 2,1 MB S > On 4 May 2024, at 09:10, stephane ducasse <stephane.ducasse(a)inria.fr> wrote: > > Hi richard > > I can write something once you have a look at the video and let me know what you would like to know. > > S > >> On 3 May 2024, at 14:27, Sebastian Jordan Montano <sebastian.jordan(a)inria.fr> wrote: >> >> You have the guide how to contribute to a fix in Pharo: https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo >> >> Sebastian >> >> ----- Mail original ----- >>> De: "Richard O'Keefe" <raoknz(a)gmail.com> >>> Ã: "Any question about pharo is welcome" <pharo-users(a)lists.pharo.org> >>> EnvoyÃ©: Vendredi 3 Mai 2024 12:28:16 >>> Objet: [Pharo-users] Re: Getting started with the easy projects >> >>> What I was really asking was about the very basic mechanics of it. >>> "Where are the instructions about how to sign up" >>> meant "do I have to register somewhere and if so where and how?" >>> "Where are the instructions about what to do" >>> meant "suppose I have registered and have the latest Pharo open >>> on my laptop; how do I connect to the repository, how do I submit >>> a change for review?" I have been playing with Pharo since version 1 >>> but I've never actually connected to a repository. >>> >>> I think a "Complete Idiot's Guide to Getting Started with Distributed >>> Development in Phraro" probably already exists somewhere, I just >>> don't know where to look for it. >>> >>> On Sat, 27 Apr 2024 at 21:05, stephane ducasse >>> <stephane.ducasse(a)inria.fr> wrote: >>>> >>>> Hi richard >>>> >>>> https://github.com/orgs/pharo-project/projects/8 >>>> lists some easy projects. I'd like to make a contribution. >>>> >>>> >>>> Cool. >>>> The first thing I suggest is to take the stupidiest issue like adding a comment >>>> in a method >>>> or fixing a badly written comment and make a PR. >>>> I like to do this trivial things because there are easy to give a positive slant >>>> on my energy. >>>> >>>> Where are the instructions on how to sign up and what >>>> to do? Fair warning, I'll probably need a bit of hand-holdingâ¦ >>>> >>>> >>>> For the contributions feel free to pick what you like >>>> >>>> - Some easy things are: better comments, improving test coverage >>>> - Now Iâm pretty sure that we can get collection improvements >>>> - This one could interest you: underscores in numeric literals >>>> https://github.com/pharo-project/pheps/pull/18/files >>>> We had long design discussions and I think that the result is good but we never >>>> got the time to implement it. >>>> >>>> S >>>> >>>> >>>> >>>> >>>> StÃ©phane Ducasse >>>> http://stephane.ducasse.free.fr >>>> 06 30 93 66 73 >>>> >>>> "If you knew today was your last day on earth, what would you do differently? >>>> ....ESPECIALLY if, by doing something different, today might not be your last >>>> day on earth.â Calvin & Hobbes >>>> >>>> >>>> >>>> > > StÃ©phane Ducasse > http://stephane.ducasse.free.fr > 06 30 93 66 73 > > "If you knew today was your last day on earth, what would you do differently? ....ESPECIALLY if, by doing something different, today might not be your last day on earth.â Calvin & Hobbes > > > > > StÃ©phane Ducasse http://stephane.ducasse.free.fr 06 30 93 66 73 "If you knew today was your last day on earth, what would you do differently? ....ESPECIALLY if, by doing something different, today might not be your last day on earth.â Calvin & Hobbes

May 16, 2024

Re: P12 new Tonel formatting and PR implications

by Tim Mackinnon

Answering my own question - it writes out file to the disk outside of Iceberg's knowledge - so you have to open a terminal and: git commit -a -m "Update tonel formal to V3" git push I 've submitted a PR to improve the instructions in the open docs repo. On Thu, 16 May 2024, at 12:09 AM, Tim Mackinnon wrote: > Hey Cyril - before I raise a bug, I've tried running that script on > CodeParadise and first off, its missing a declaration for respository > (although I think you can execute and get away with it). > > I also hit an error that it assume that every package of your project > is loaded - so it probably needs a comment caveat to explain that you > shoujld have loaded every project before running it (or we correct the > internal code that makes that assumption). > > But having run it - I'm a bit confused what should happen? I was > expecting dirty projects that I would then commit (having made a branch > to submit a PR on) - however no packages appear dirty and so there is > nothing to commit? I guess I'm a bit confused what > #forInternalStoreFileOut: on: does ? Is it writing something out to > disk - and if so, what do we do with that in pharo - or are we expected > to do something on the terminal? If so - the instructions don't make > that very clear? > > To be honest I was expecting something that caused something that cause > a comment change that would cause every package to force a commit in > the iceberg browser? > > Can you clarify a bit more please? > > Tim > > On Mon, 13 May 2024, at 10:45 AM, Cyril FERLICOT-DELBECQUE via > Pharo-users wrote: >> Hi, >> >> Here are some additional notes to what was already answered. >> >> If you want to convert all the files of a repository at once to avoid >> to have multiple PR with format changes you can use this script and >> commit the resulting files: >> >> | projectName | >> projectName := 'Spec2'. >> repository := IceRepository repositories detect: [ :repo | repo name = >> projectName ]. >> repository workingCopy packages do: [ :pkg | >> IceLibgitTonelWriter forInternalStoreFileOut: pkg latestVersion >> mcVersion on: repository ] >> >> Also, if you work on a project both in p12 and p11, you can avoid the >> ping pong by fixing a version of tonel in the properties file. The file >> to update is the .properties that is in the source folder and it should >> look like this: >> >> { >> #format : #tonel, >> #version: #'1.0' >> } >> >> P12 will take into account the tonel version asked and use it. In >> previous version of Pharo, this additional line will be ignored and >> Tonel v1 will be used. >> >> With both of those options it should be possible to reduce the pain of >> the format update. >> >> Have a nice day >> >> -- >> Cyril Ferlicot-Delbecque >> https://ferlicot.fr >> >> >> On Sunday, May 12th, 2024 at 12:21 PM, Tim Mackinnon <tim(a)testit.works> wrote: >> >>> Asking this here as it didnât get much traction on Discord - but with the move to P12, the category format in Tonel has changed from a symbol to a string e.g. { #category : #examples } vs { #category : 'examples' } - this causes mega noise when submitting tiny PR's - how is everyone else handling this? Should projects resave every project module to get the new format while people are out of the pool? Or is there a way to force the old format on specific projects until they can be upgraded ? >>> >>> It seems like a change whose consequences need some attention ? >>> >>> What are others doing? >>> >>> Tim

May 15, 2024

Re: P12 new Tonel formatting and PR implications

by Tim Mackinnon

Hey Cyril - before I raise a bug, I've tried running that script on CodeParadise and first off, its missing a declaration for respository (although I think you can execute and get away with it). I also hit an error that it assume that every package of your project is loaded - so it probably needs a comment caveat to explain that you shoujld have loaded every project before running it (or we correct the internal code that makes that assumption). But having run it - I'm a bit confused what should happen? I was expecting dirty projects that I would then commit (having made a branch to submit a PR on) - however no packages appear dirty and so there is nothing to commit? I guess I'm a bit confused what #forInternalStoreFileOut: on: does ? Is it writing something out to disk - and if so, what do we do with that in pharo - or are we expected to do something on the terminal? If so - the instructions don't make that very clear? To be honest I was expecting something that caused something that cause a comment change that would cause every package to force a commit in the iceberg browser? Can you clarify a bit more please? Tim On Mon, 13 May 2024, at 10:45 AM, Cyril FERLICOT-DELBECQUE via Pharo-users wrote: > Hi, > > Here are some additional notes to what was already answered. > > If you want to convert all the files of a repository at once to avoid > to have multiple PR with format changes you can use this script and > commit the resulting files: > > | projectName | > projectName := 'Spec2'. > repository := IceRepository repositories detect: [ :repo | repo name = > projectName ]. > repository workingCopy packages do: [ :pkg | > IceLibgitTonelWriter forInternalStoreFileOut: pkg latestVersion > mcVersion on: repository ] > > Also, if you work on a project both in p12 and p11, you can avoid the > ping pong by fixing a version of tonel in the properties file. The file > to update is the .properties that is in the source folder and it should > look like this: > > { > #format : #tonel, > #version: #'1.0' > } > > P12 will take into account the tonel version asked and use it. In > previous version of Pharo, this additional line will be ignored and > Tonel v1 will be used. > > With both of those options it should be possible to reduce the pain of > the format update. > > Have a nice day > > -- > Cyril Ferlicot-Delbecque > https://ferlicot.fr > > > On Sunday, May 12th, 2024 at 12:21 PM, Tim Mackinnon <tim(a)testit.works> wrote: > >> Asking this here as it didnât get much traction on Discord - but with the move to P12, the category format in Tonel has changed from a symbol to a string e.g. { #category : #examples } vs { #category : 'examples' } - this causes mega noise when submitting tiny PR's - how is everyone else handling this? Should projects resave every project module to get the new format while people are out of the pool? Or is there a way to force the old format on specific projects until they can be upgraded ? >> >> It seems like a change whose consequences need some attention ? >> >> What are others doing? >> >> Tim

May 15, 2024

Re: Window size: look at ClyBrowserMorph>>initialExtent

by Tim Mackinnon

Davide - I encourage you to consider whether you can do that tiny bit more from "posting a working on this list". You can of course choose what you want, and Pharo is free for everyone, but as is often mentioned - its a project that belongs to everyone and the more we can each do, the better (and quicker) it gets. I too started out thinking I was too busy, and that posting a solution that "others" could run with was enough - but then I noticed how busy some of the key people are, fixing things that are beyond my perceived capability. And it dawned on my that I could at least create an issue on Github with my poposed fix and some more details around the problem (and maybe post that here to widen conversation) - this at least made things more efficient to get fixed. And then I noticed sometimes those fixes never got applied, and I realised that those key people really are super busy and I want them to fix/improve the harder stuff - and honestly - it wasn't that much harder to launch a fresh image - create branch, apply my fix and submit a PR - in fact I learned a lot more doing it AND I helped those busy people too. win/win. So why not consider giving it a go next time? In fact your settings idea would be a great one to flex your passion on? Of course - posting a fix is helpful - but at least create the issue. Tim On Tue, 14 May 2024, at 6:17 AM, Davide Varvello wrote: > Hi Tim, > > I get it and appreciate your suggestion. My approach to contribute to > the Pharo community is when I can solve an issue to post my solution or > a workaround on this list, I know pushing code to github would be > better but I canât do more than this actually, sorry. > > Cheers > Davide > > > > > > > > On Friday, May 10, 2024 at 07:03:55 PM GMT+2, Tim Mackinnon > <tim(a)testit.works> wrote: > > > > > > > Davide - why don't you submit a PR? I'm sure you can figure out how to > add a settings to the system (can't offhand remember, but there are > examples - and you can ask on the discord) and it would be a nice > contribution to make . > > Its all the little contributions that make the system better - I know > I've been there, and saw how the others do it and so had a go. > > Tim > > On Fri, 10 May 2024, at 5:25 PM, Davide Varvello via Pharo-users wrote: >> Hi Guys, >> It seems to me the default size of a lot of windows is too small, so after some search and thanks to thisÂ https://stackoverflow.com/questions/55102480/how-do-i-change-the-default-he… by Marko GrdiniÄ >> >> I discovered I can change the default size of many type of windows simply changing ClyBrowserMorph>>initialExtent. >> HTH >> >> It would be good to be able to manage the size of windows in Settings >> >> Cheers >> Davide >>

May 15, 2024

Fwd: Submission is open for the ESUG 2024 Innovation Technology Awards

by Noury Bouraqadi

---------- Forwarded Message --------- From: Noury Bouraqadi <bouraqadi(a)gmail.com> Subject: Submission is open for the ESUG 2024 Innovation Technology Awards Date: May 14 2024, at 5:39 pm To: Members ESUG <esug-list(a)lists.esug.org> Dear fellow Smalltalkers, Please find below the call of the call for submissions to the ESUG 2024 Innovation Technology Awards. Best, Noury ---- Innovation Technology Awards 19th Edition Have you developed a cool Smalltalk project you want to share? Developers of any Smalltalk-based software can participate (https://forms.gle/8k8DwauZj8VJb6cu9) During the conference, participants demonstrate their systems in a session Monday July 8th, during which the conference attendees vote. The top 3 teams will receive, respectively, 500 Euros, 300 Euros and 200 Euros. The results will be announced in the Awards ceremony that is held during the social event. Submit now (https://forms.gle/8k8DwauZj8VJb6cu9) Submission Deadline: Sunday June 30th

May 14, 2024

Re: [Pharo-dev] Open Call: Object-Centric Breakpoints experiment

by Steven Costiou

Dear community, we are still looking for participants for our experiment in the EVREF team! Please help us! We need 15 more participants, if you are interested and if you believe you can work your way around a debugger, the experiment is fully available online here (using Pharo 9): https://github.com/Pharo-XP-Tools/XPImageGeneration/tree/exp-ocd We would like to show our results at ESUG, but for that we really need these 15 additional participations so that we can trust the results better. Thanks in advance, and many thanks to the people who already participated! Steven. Le 2024-02-02 14:14, Steven Costiou a Ã©crit : > Dear Community, > > as part of a research project in the EVREF team, we are looking for people to participate to an empirical experiment on object-centric breakpoints - a debugging tool present in Pharo 9. > > Many people from the community already participated, and we thank them very much ð > > We are still looking for participants, we need 40 people to do the experiment! > > Please help us, in return it helps us understand better our tools and their impact and therefore build better tools for the Pharo community! > > For those who want to know a bit more, see my original email below. > For those who just want to jump at the experiment, you can go there https://github.com/Pharo-XP-Tools/XPImageGeneration/tree/exp-ocd > > Thanks in advance ð > Steven. > > --- > > We would like to invite you to participate to our experimental study on Object-Centric Breakpoints. > This study aims to evaluate and to understand how Object-Centric Breakpoints impacts the debugging activity. > > This experiment takes place in **Pharo 9**. > In this experiment, we ask you to solve 2 debugging tasks, one with standard Pharo tools and one other with Object-Centric Breakpoints. > Between the two tasks, you will have to follow a tutorialand warmup tasks to learn how to use the tool. > > **How to Participate:** > All instructions are here, please read them carefully: https://github.com/Pharo-XP-Tools/XPImageGeneration/tree/exp-ocd > > **About the Experiment:** > > The experiment last between 40 minutes and 2 hours. > Participants should have experience with Pharo development and debugging. > We recommend having more than 6 months experience in Pharo and debugging in general. > You will gain insights into the Object-Centric Breakpoints approach and contribute to advancements in debugging research. > > Help us to build better debugging tools that help you debug! > > **Some constraints:** > > - You are not allowed to load external tools and baselines, but you can use anything that is in the base image > - Please do the experiment in one shot if possible without interruptions > - The experiment sends anonymous data to our inria server, please make sure that you have a valid internet connection > - Please try to use the object-centric breakpoints when the experimental framework asks you to > > **Notes:** > Participation is voluntary, and everything is anonymous. > You can abandon the experiment at any point (and your data will be discarded). > For any question, you can contact us: steven.costiou(a)inria.fr and valentin.bourcier(a)inria.fr > > Thank you for considering participating in our study. > Your contribution will be valuable in advancing the field of debugging and helping us understand what tools we need to build for Pharo. > > Sincerely, > Steven and Valentin, > EVREF team, Inria

May 14, 2024

Re: Window size: look at ClyBrowserMorph>>initialExtent

by Davide Varvello

Hi Tim, I get it and appreciate your suggestion. My approach to contribute to the Pharo community is when I can solve an issue to post my solution or a workaround on this list, I know pushing code to github would be better but I canât do more than this actually, sorry. Cheers Davide On Friday, May 10, 2024 at 07:03:55 PM GMT+2, Tim Mackinnon <tim(a)testit.works> wrote: Davide - why don't you submit a PR? I'm sure you can figure out how to add a settings to the system (can't offhand remember, but there are examples - and you can ask on the discord) and it would be a nice contribution to make . Its all the little contributions that make the system better - I know I've been there, and saw how the others do it and so had a go. Tim On Fri, 10 May 2024, at 5:25 PM, Davide Varvello via Pharo-users wrote: > Hi Guys, > It seems to me the default size of a lot of windows is too small, so after some search and thanks to thisÂ https://stackoverflow.com/questions/55102480/how-do-i-change-the-default-he… by Marko GrdiniÄ > > I discovered I can change the default size of many type of windows simply changing ClyBrowserMorph>>initialExtent. > HTH > > It would be good to be able to manage the size of windows in Settings > > Cheers > Davide >

May 14, 2024

Re: [Pharo-dev] This week (19/2024) on the Pharo Issue Tracker

by stephane ducasse

Yes I understood that after sending my mail > On 13 May 2024, at 11:56, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Only the first issue is for Pharo 12, all the other for Pharo 13. > (the idea is to have just one headline Pharo 12 for all the issues backported) > > Marcus > >> On 13 May 2024, at 15:31, stephane ducasse <stephane.ducasse(a)inria.fr> wrote: >> >> Hi >> >> I imagine that this is for Pharo 13 >> >> S >> >>> On 13 May 2024, at 03:11, Marcus Denker <marcus.denker(a)inria.fr> wrote: >>> >>> # Pharo 12 >>> >>> - 16576-Problem-with-completion-in-the-tutorial #16582 >>> https://github.com/pharo-project/pharo/pull/16582 >>> >>> >>> # Virtual Machine >>> >>> - Bump to MacOS 11 and above #792 >>> https://github.com/pharo-project/pharo-vm/pull/792 >>> >>> - Do not use asserta: in a statement #788 >>> https://github.com/pharo-project/pharo-vm/pull/788 >>> >>> - Moving pharo.signatures files for OSX Bundle to Resources folder #770 >>> https://github.com/pharo-project/pharo-vm/pull/770 >>> >>> >>> # Features >>> >>> - New debugger extension model to display dynamic extensions #739 >>> https://github.com/pharo-spec/NewTools/pull/739 >>> >>> - add asAccessor #16579 >>> https://github.com/pharo-project/pharo/pull/16579 >>> >>> - Make it easier to diagnose mock failures by printing message sends properly and storing the send history in the mock #16555 >>> https://github.com/pharo-project/pharo/pull/16555 >>> >>> - add two's complement display for negative integers #746 >>> https://github.com/pharo-spec/NewTools/pull/746 >>> >>> # Fixes >>> >>> - Make ToggleMenuItemMorph use a FormSet for the submenu marker #16510 >>> https://github.com/pharo-project/pharo/pull/16510 >>> >>> - Taskbar option to close windows hidden behind other windows #16552 >>> https://github.com/pharo-project/pharo/pull/16552 >>> >>> - prof stef lesson view did not understand has binding of #16578 >>> https://github.com/pharo-project/pharo/pull/16578 >>> >>> - fix precedence computation #16581 >>> https://github.com/pharo-project/pharo/pull/16581 >>> >>> # Refactoring Engine >>> >>> - Fix RBCompositeRefactoryChange>>#defineClass: argument name #16600 >>> https://github.com/pharo-project/pharo/pull/16600 >>> >>> - Refactor: preconditions return array of preconditions by default #16527 >>> https://github.com/pharo-project/pharo/pull/16527 >>> >>> >>> # Rules >>> >>> - add ReOverridingExtentsionMethod rule #16550 >>> https://github.com/pharo-project/pharo/pull/16550 >>> >>> - add rule to avoid that TestCase rely on Initialize #16513 >>> https://github.com/pharo-project/pharo/pull/16513 >>> >>> # Tests (Green tests on CI) >>> >>> - Fix testCodeCruftLeftInMethods #16598 >>> https://github.com/pharo-project/pharo/pull/16598 >>> >>> - Update roassal to v1.06d #16595 >>> https://github.com/pharo-project/pharo/pull/16595 >>> >>> - Fixing reflectivity tests that can randomly fail because of unstable and unpredictable tests generating methods #16584 >>> https://github.com/pharo-project/pharo/pull/16584 >>> >>> - 16569-CI-Pharo13-code-with-halt-was-merged #16570 >>> https://github.com/pharo-project/pharo/pull/16570 >>> >>> - clearing debugger subscriptions and subcomponents in StDebuggerExtensionMechanismTest>>#tearDown #712 >>> https://github.com/pharo-spec/NewTools/pull/712 >>> >>> >>> # Cleanups >>> >>> - Renaming DebugPointSideEffect into DebugPointMetaBehavior #16563 >>> https://github.com/pharo-project/pharo/pull/16563 >>> >>> - Cleanup: TestCase class>>#lastRunMethodNamed: #16588 >>> https://github.com/pharo-project/pharo/pull/16588 >>> >>> - Cleanup: TestCase class>>#hasErrorTest, TestCase class>>#hasPassedTest and TestCase class>>#hasFailedTest #16586 >>> https://github.com/pharo-project/pharo/pull/16586 >>> >>> - Changed 'Transcript show:' construct to 'self trace' #16385 >>> https://github.com/pharo-project/pharo/pull/16385 >>> >>> - removing dependency to UIManager in StFuelStackCommand #745 >>> https://github.com/pharo-spec/NewTools/pull/745 >>> >>> # Documentation >>> >>> - Update CONTRIBUTING.md #16575 >>> https://github.com/pharo-project/pharo/pull/16575 >> >> StÃ©phane Ducasse >> http://stephane.ducasse.free.fr >> 06 30 93 66 73 >> >> "If you knew today was your last day on earth, what would you do differently? ....ESPECIALLY if, by doing something different, today might not be your last day on earth.â Calvin & Hobbes >> >> >> >> >> > StÃ©phane Ducasse http://stephane.ducasse.free.fr 06 30 93 66 73 "If you knew today was your last day on earth, what would you do differently? ....ESPECIALLY if, by doing something different, today might not be your last day on earth.â Calvin & Hobbes

May 14, 2024

Re: P12 new Tonel formatting and PR implications

by Tim Mackinnon

Hey Cyril - as mentioned on Discord, thanks for advising and sorting this out (for the bigger changes in P13 - it will be useful to get something in the release notes - but definitely don't want to stand in the way of progress)!. Tim On Mon, 13 May 2024, at 1:55 PM, Cyril FERLICOT-DELBECQUE via Pharo-users wrote: > I added some documentation here:â¯ > > https://github.com/pharo-open-documentation/pharo-wiki/blob/master/General/… > > I hope this helps :) > > -- > Cyril Ferlicot-Delbecque > https://ferlicot.fr > > > On Monday, May 13th, 2024 at 12:55 PM, stephane ducasse <stephane.ducasse(a)inria.fr> wrote: >> Cyril >> >> could you add that in the wiki somewhere. I will publish something on pharo weekly. >> >> S >> >>> On 13 May 2024, at 05:45, Cyril FERLICOT-DELBECQUE via Pharo-users <pharo-users(a)lists.pharo.org> wrote: >>> >>> Hi, >>> >>> Here are some additional notes to what was already answered. >>> >>> If you want to convert all the files of a repository at once to avoid to have multiple PR with format changes you can use this script and commit the resulting files: >>> >>> | projectName | >>> projectName := 'Spec2'. >>> repository := IceRepository repositories detect: [ :repo | repo name = projectName ]. >>> repository workingCopy packages do: [ :pkg | >>> IceLibgitTonelWriter forInternalStoreFileOut: pkg latestVersion mcVersion on: repository ] >>> >>> Also, if you work on a project both in p12 and p11, you can avoid the ping pong by fixing a version of tonel in the properties file. The file to update is the .properties that is in the source folder and it should look like this: >>> >>> { >>> #format : #tonel, >>> #version: #'1.0' >>> } >>> >>> P12 will take into account the tonel version asked and use it. In previous version of Pharo, this additional line will be ignored and Tonel v1 will be used. >>> >>> With both of those options it should be possible to reduce the pain of the format update. >>> >>> Have a nice day >>> >>> -- >>> Cyril Ferlicot-Delbecque >>> https://ferlicot.fr >>> >>> >>> On Sunday, May 12th, 2024 at 12:21 PM, Tim Mackinnon <tim(a)testit.works> wrote: >>> >>>> Asking this here as it didnât get much traction on Discord - but with the move to P12, the category format in Tonel has changed from a symbol to a string e.g. { #category : #examples } vs { #category : 'examples' } - this causes mega noise when submitting tiny PR's - how is everyone else handling this? Should projects resave every project module to get the new format while people are out of the pool? Or is there a way to force the old format on specific projects until they can be upgraded ? >>>> >>>> It seems like a change whose consequences need some attention ? >>>> >>>> What are others doing? >>>> >>>> Tim >> >> StÃ©phane Ducasse >> http://stephane.ducasse.free.fr >> 06 30 93 66 73 >> >> "If you knew today was your last day on earth, what would you do differently? ....ESPECIALLY if, by doing something different, today might not be your last day on earth.â Calvin & Hobbes >> >>

May 13, 2024

Re: [Pharo-dev] This week (19/2024) on the Pharo Issue Tracker

by Marcus Denker

Only the first issue is for Pharo 12, all the other for Pharo 13. (the idea is to have just one headline Pharo 12 for all the issues backported) Marcus > On 13 May 2024, at 15:31, stephane ducasse <stephane.ducasse(a)inria.fr> wrote: > > Hi > > I imagine that this is for Pharo 13 > > S > >> On 13 May 2024, at 03:11, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> # Pharo 12 >> >> - 16576-Problem-with-completion-in-the-tutorial #16582 >> https://github.com/pharo-project/pharo/pull/16582 >> >> >> # Virtual Machine >> >> - Bump to MacOS 11 and above #792 >> https://github.com/pharo-project/pharo-vm/pull/792 >> >> - Do not use asserta: in a statement #788 >> https://github.com/pharo-project/pharo-vm/pull/788 >> >> - Moving pharo.signatures files for OSX Bundle to Resources folder #770 >> https://github.com/pharo-project/pharo-vm/pull/770 >> >> >> # Features >> >> - New debugger extension model to display dynamic extensions #739 >> https://github.com/pharo-spec/NewTools/pull/739 >> >> - add asAccessor #16579 >> https://github.com/pharo-project/pharo/pull/16579 >> >> - Make it easier to diagnose mock failures by printing message sends properly and storing the send history in the mock #16555 >> https://github.com/pharo-project/pharo/pull/16555 >> >> - add two's complement display for negative integers #746 >> https://github.com/pharo-spec/NewTools/pull/746 >> >> # Fixes >> >> - Make ToggleMenuItemMorph use a FormSet for the submenu marker #16510 >> https://github.com/pharo-project/pharo/pull/16510 >> >> - Taskbar option to close windows hidden behind other windows #16552 >> https://github.com/pharo-project/pharo/pull/16552 >> >> - prof stef lesson view did not understand has binding of #16578 >> https://github.com/pharo-project/pharo/pull/16578 >> >> - fix precedence computation #16581 >> https://github.com/pharo-project/pharo/pull/16581 >> >> # Refactoring Engine >> >> - Fix RBCompositeRefactoryChange>>#defineClass: argument name #16600 >> https://github.com/pharo-project/pharo/pull/16600 >> >> - Refactor: preconditions return array of preconditions by default #16527 >> https://github.com/pharo-project/pharo/pull/16527 >> >> >> # Rules >> >> - add ReOverridingExtentsionMethod rule #16550 >> https://github.com/pharo-project/pharo/pull/16550 >> >> - add rule to avoid that TestCase rely on Initialize #16513 >> https://github.com/pharo-project/pharo/pull/16513 >> >> # Tests (Green tests on CI) >> >> - Fix testCodeCruftLeftInMethods #16598 >> https://github.com/pharo-project/pharo/pull/16598 >> >> - Update roassal to v1.06d #16595 >> https://github.com/pharo-project/pharo/pull/16595 >> >> - Fixing reflectivity tests that can randomly fail because of unstable and unpredictable tests generating methods #16584 >> https://github.com/pharo-project/pharo/pull/16584 >> >> - 16569-CI-Pharo13-code-with-halt-was-merged #16570 >> https://github.com/pharo-project/pharo/pull/16570 >> >> - clearing debugger subscriptions and subcomponents in StDebuggerExtensionMechanismTest>>#tearDown #712 >> https://github.com/pharo-spec/NewTools/pull/712 >> >> >> # Cleanups >> >> - Renaming DebugPointSideEffect into DebugPointMetaBehavior #16563 >> https://github.com/pharo-project/pharo/pull/16563 >> >> - Cleanup: TestCase class>>#lastRunMethodNamed: #16588 >> https://github.com/pharo-project/pharo/pull/16588 >> >> - Cleanup: TestCase class>>#hasErrorTest, TestCase class>>#hasPassedTest and TestCase class>>#hasFailedTest #16586 >> https://github.com/pharo-project/pharo/pull/16586 >> >> - Changed 'Transcript show:' construct to 'self trace' #16385 >> https://github.com/pharo-project/pharo/pull/16385 >> >> - removing dependency to UIManager in StFuelStackCommand #745 >> https://github.com/pharo-spec/NewTools/pull/745 >> >> # Documentation >> >> - Update CONTRIBUTING.md #16575 >> https://github.com/pharo-project/pharo/pull/16575 > > StÃ©phane Ducasse > http://stephane.ducasse.free.fr > 06 30 93 66 73 > > "If you knew today was your last day on earth, what would you do differently? ....ESPECIALLY if, by doing something different, today might not be your last day on earth.â Calvin & Hobbes > > > > >

May 13, 2024

[ANN] docker-pharo-vm v10.2.0-2024-05-13 [v10.2.0 [2024-05-13]] released!

by Buenos Aires Smalltalk

May 13, 2024

Re: P12 new Tonel formatting and PR implications

by stephane ducasse

Tx! > On 13 May 2024, at 08:55, Cyril FERLICOT-DELBECQUE via Pharo-users <pharo-users(a)lists.pharo.org> wrote: > > I added some documentation here:â¯ > > https://github.com/pharo-open-documentation/pharo-wiki/blob/master/General/… > > I hope this helps :) > > -- > Cyril Ferlicot-Delbecque > https://ferlicot.fr <https://ferlicot.fr/> > > On Monday, May 13th, 2024 at 12:55 PM, stephane ducasse <stephane.ducasse(a)inria.fr> wrote: >> Cyril >> >> could you add that in the wiki somewhere. I will publish something on pharo weekly. >> >> S >> >>> On 13 May 2024, at 05:45, Cyril FERLICOT-DELBECQUE via Pharo-users <pharo-users(a)lists.pharo.org> wrote: >>> >>> Hi, >>> >>> Here are some additional notes to what was already answered. >>> >>> If you want to convert all the files of a repository at once to avoid to have multiple PR with format changes you can use this script and commit the resulting files: >>> >>> | projectName | >>> projectName := 'Spec2'. >>> repository := IceRepository repositories detect: [ :repo | repo name = projectName ]. >>> repository workingCopy packages do: [ :pkg | >>> IceLibgitTonelWriter forInternalStoreFileOut: pkg latestVersion mcVersion on: repository ] >>> >>> Also, if you work on a project both in p12 and p11, you can avoid the ping pong by fixing a version of tonel in the properties file. The file to update is the .properties that is in the source folder and it should look like this: >>> >>> { >>> #format : #tonel, >>> #version: #'1.0' >>> } >>> >>> P12 will take into account the tonel version asked and use it. In previous version of Pharo, this additional line will be ignored and Tonel v1 will be used. >>> >>> With both of those options it should be possible to reduce the pain of the format update. >>> >>> Have a nice day >>> >>> -- >>> Cyril Ferlicot-Delbecque >>> https://ferlicot.fr >>> >>> >>> On Sunday, May 12th, 2024 at 12:21 PM, Tim Mackinnon <tim(a)testit.works> wrote: >>> >>>> Asking this here as it didnât get much traction on Discord - but with the move to P12, the category format in Tonel has changed from a symbol to a string e.g. { #category : #examples } vs { #category : 'examples' } - this causes mega noise when submitting tiny PR's - how is everyone else handling this? Should projects resave every project module to get the new format while people are out of the pool? Or is there a way to force the old format on specific projects until they can be upgraded ? >>>> >>>> It seems like a change whose consequences need some attention ? >>>> >>>> What are others doing? >>>> >>>> Tim >> >> StÃ©phane Ducasse >> http://stephane.ducasse.free.fr >> 06 30 93 66 73 >> >> "If you knew today was your last day on earth, what would you do differently? ....ESPECIALLY if, by doing something different, today might not be your last day on earth.â Calvin & Hobbes >> >> >> >> >> > StÃ©phane Ducasse http://stephane.ducasse.free.fr 06 30 93 66 73 "If you knew today was your last day on earth, what would you do differently? ....ESPECIALLY if, by doing something different, today might not be your last day on earth.â Calvin & Hobbes

May 13, 2024

Re: [Pharo-dev] This week (19/2024) on the Pharo Issue Tracker

by stephane ducasse

Hi I imagine that this is for Pharo 13 S > On 13 May 2024, at 03:11, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > # Pharo 12 > > - 16576-Problem-with-completion-in-the-tutorial #16582 > https://github.com/pharo-project/pharo/pull/16582 > > > # Virtual Machine > > - Bump to MacOS 11 and above #792 > https://github.com/pharo-project/pharo-vm/pull/792 > > - Do not use asserta: in a statement #788 > https://github.com/pharo-project/pharo-vm/pull/788 > > - Moving pharo.signatures files for OSX Bundle to Resources folder #770 > https://github.com/pharo-project/pharo-vm/pull/770 > > > # Features > > - New debugger extension model to display dynamic extensions #739 > https://github.com/pharo-spec/NewTools/pull/739 > > - add asAccessor #16579 > https://github.com/pharo-project/pharo/pull/16579 > > - Make it easier to diagnose mock failures by printing message sends properly and storing the send history in the mock #16555 > https://github.com/pharo-project/pharo/pull/16555 > > - add two's complement display for negative integers #746 > https://github.com/pharo-spec/NewTools/pull/746 > > # Fixes > > - Make ToggleMenuItemMorph use a FormSet for the submenu marker #16510 > https://github.com/pharo-project/pharo/pull/16510 > > - Taskbar option to close windows hidden behind other windows #16552 > https://github.com/pharo-project/pharo/pull/16552 > > - prof stef lesson view did not understand has binding of #16578 > https://github.com/pharo-project/pharo/pull/16578 > > - fix precedence computation #16581 > https://github.com/pharo-project/pharo/pull/16581 > > # Refactoring Engine > > - Fix RBCompositeRefactoryChange>>#defineClass: argument name #16600 > https://github.com/pharo-project/pharo/pull/16600 > > - Refactor: preconditions return array of preconditions by default #16527 > https://github.com/pharo-project/pharo/pull/16527 > > > # Rules > > - add ReOverridingExtentsionMethod rule #16550 > https://github.com/pharo-project/pharo/pull/16550 > > - add rule to avoid that TestCase rely on Initialize #16513 > https://github.com/pharo-project/pharo/pull/16513 > > # Tests (Green tests on CI) > > - Fix testCodeCruftLeftInMethods #16598 > https://github.com/pharo-project/pharo/pull/16598 > > - Update roassal to v1.06d #16595 > https://github.com/pharo-project/pharo/pull/16595 > > - Fixing reflectivity tests that can randomly fail because of unstable and unpredictable tests generating methods #16584 > https://github.com/pharo-project/pharo/pull/16584 > > - 16569-CI-Pharo13-code-with-halt-was-merged #16570 > https://github.com/pharo-project/pharo/pull/16570 > > - clearing debugger subscriptions and subcomponents in StDebuggerExtensionMechanismTest>>#tearDown #712 > https://github.com/pharo-spec/NewTools/pull/712 > > > # Cleanups > > - Renaming DebugPointSideEffect into DebugPointMetaBehavior #16563 > https://github.com/pharo-project/pharo/pull/16563 > > - Cleanup: TestCase class>>#lastRunMethodNamed: #16588 > https://github.com/pharo-project/pharo/pull/16588 > > - Cleanup: TestCase class>>#hasErrorTest, TestCase class>>#hasPassedTest and TestCase class>>#hasFailedTest #16586 > https://github.com/pharo-project/pharo/pull/16586 > > - Changed 'Transcript show:' construct to 'self trace' #16385 > https://github.com/pharo-project/pharo/pull/16385 > > - removing dependency to UIManager in StFuelStackCommand #745 > https://github.com/pharo-spec/NewTools/pull/745 > > # Documentation > > - Update CONTRIBUTING.md #16575 > https://github.com/pharo-project/pharo/pull/16575 StÃ©phane Ducasse http://stephane.ducasse.free.fr 06 30 93 66 73 "If you knew today was your last day on earth, what would you do differently? ....ESPECIALLY if, by doing something different, today might not be your last day on earth.â Calvin & Hobbes

May 13, 2024

Re: P12 new Tonel formatting and PR implications

by Cyril FERLICOT-DELBECQUE

I added some documentation here:â¯ https://github.com/pharo-open-documentation/pharo-wiki/blob/master/General/… I hope this helps :) -- Cyril Ferlicot-Delbecquehttps://ferlicot.fr On Monday, May 13th, 2024 at 12:55 PM, stephane ducasse <stephane.ducasse(a)inria.fr> wrote: > Cyril > > could you add that in the wiki somewhere. I will publish something on pharo weekly. > > S > >> On 13 May 2024, at 05:45, Cyril FERLICOT-DELBECQUE via Pharo-users <pharo-users(a)lists.pharo.org> wrote: >> >> Hi, >> >> Here are some additional notes to what was already answered. >> >> If you want to convert all the files of a repository at once to avoid to have multiple PR with format changes you can use this script and commit the resulting files: >> >> | projectName | >> projectName := 'Spec2'. >> repository := IceRepository repositories detect: [ :repo | repo name = projectName ]. >> repository workingCopy packages do: [ :pkg | >> IceLibgitTonelWriter forInternalStoreFileOut: pkg latestVersion mcVersion on: repository ] >> >> Also, if you work on a project both in p12 and p11, you can avoid the ping pong by fixing a version of tonel in the properties file. The file to update is the .properties that is in the source folder and it should look like this: >> >> { >> #format : #tonel, >> #version: #'1.0' >> } >> >> P12 will take into account the tonel version asked and use it. In previous version of Pharo, this additional line will be ignored and Tonel v1 will be used. >> >> With both of those options it should be possible to reduce the pain of the format update. >> >> Have a nice day >> >> -- >> Cyril Ferlicot-Delbecque >> https://ferlicot.fr >> >> On Sunday, May 12th, 2024 at 12:21 PM, Tim Mackinnon <tim(a)testit.works> wrote: >> >>> Asking this here as it didnât get much traction on Discord - but with the move to P12, the category format in Tonel has changed from a symbol to a string e.g. { #category : #examples } vs { #category : 'examples' } - this causes mega noise when submitting tiny PR's - how is everyone else handling this? Should projects resave every project module to get the new format while people are out of the pool? Or is there a way to force the old format on specific projects until they can be upgraded ? >>> >>> It seems like a change whose consequences need some attention ? >>> >>> What are others doing? >>> >>> Tim > > StÃ©phane Ducasse > http://stephane.ducasse.free.fr > 06 30 93 66 73 > > "If you knew today was your last day on earth, what would you do differently? ....ESPECIALLY if, by doing something different, today might not be your last day on earth.â Calvin & Hobbes

May 13, 2024

Re: P12 new Tonel formatting and PR implications

by stephane ducasse

https://pharoweekly.wordpress.com/2024/05/13/about-controling-change-format… > On 13 May 2024, at 05:45, Cyril FERLICOT-DELBECQUE via Pharo-users <pharo-users(a)lists.pharo.org> wrote: > > Hi, > > Here are some additional notes to what was already answered. > > If you want to convert all the files of a repository at once to avoid to have multiple PR with format changes you can use this script and commit the resulting files: > > | projectName | > projectName := 'Spec2'. > repository := IceRepository repositories detect: [ :repo | repo name = projectName ]. > repository workingCopy packages do: [ :pkg | > IceLibgitTonelWriter forInternalStoreFileOut: pkg latestVersion mcVersion on: repository ] > > Also, if you work on a project both in p12 and p11, you can avoid the ping pong by fixing a version of tonel in the properties file. The file to update is the .properties that is in the source folder and it should look like this: > > { > #format : #tonel, > #version: #'1.0' > } > > P12 will take into account the tonel version asked and use it. In previous version of Pharo, this additional line will be ignored and Tonel v1 will be used. > > With both of those options it should be possible to reduce the pain of the format update. > > Have a nice day > > -- > Cyril Ferlicot-Delbecque > https://ferlicot.fr > > > On Sunday, May 12th, 2024 at 12:21 PM, Tim Mackinnon <tim(a)testit.works> wrote: > >> Asking this here as it didnât get much traction on Discord - but with the move to P12, the category format in Tonel has changed from a symbol to a string e.g. { #category : #examples } vs { #category : 'examples' } - this causes mega noise when submitting tiny PR's - how is everyone else handling this? Should projects resave every project module to get the new format while people are out of the pool? Or is there a way to force the old format on specific projects until they can be upgraded ? >> >> It seems like a change whose consequences need some attention ? >> >> What are others doing? >> >> Tim StÃ©phane Ducasse http://stephane.ducasse.free.fr 06 30 93 66 73 "If you knew today was your last day on earth, what would you do differently? ....ESPECIALLY if, by doing something different, today might not be your last day on earth.â Calvin & Hobbes

May 13, 2024

Re: P12 new Tonel formatting and PR implications

by stephane ducasse

Cyril could you add that in the wiki somewhere. I will publish something on pharo weekly. S > On 13 May 2024, at 05:45, Cyril FERLICOT-DELBECQUE via Pharo-users <pharo-users(a)lists.pharo.org> wrote: > > Hi, > > Here are some additional notes to what was already answered. > > If you want to convert all the files of a repository at once to avoid to have multiple PR with format changes you can use this script and commit the resulting files: > > | projectName | > projectName := 'Spec2'. > repository := IceRepository repositories detect: [ :repo | repo name = projectName ]. > repository workingCopy packages do: [ :pkg | > IceLibgitTonelWriter forInternalStoreFileOut: pkg latestVersion mcVersion on: repository ] > > Also, if you work on a project both in p12 and p11, you can avoid the ping pong by fixing a version of tonel in the properties file. The file to update is the .properties that is in the source folder and it should look like this: > > { > #format : #tonel, > #version: #'1.0' > } > > P12 will take into account the tonel version asked and use it. In previous version of Pharo, this additional line will be ignored and Tonel v1 will be used. > > With both of those options it should be possible to reduce the pain of the format update. > > Have a nice day > > -- > Cyril Ferlicot-Delbecque > https://ferlicot.fr > > > On Sunday, May 12th, 2024 at 12:21 PM, Tim Mackinnon <tim(a)testit.works> wrote: > >> Asking this here as it didnât get much traction on Discord - but with the move to P12, the category format in Tonel has changed from a symbol to a string e.g. { #category : #examples } vs { #category : 'examples' } - this causes mega noise when submitting tiny PR's - how is everyone else handling this? Should projects resave every project module to get the new format while people are out of the pool? Or is there a way to force the old format on specific projects until they can be upgraded ? >> >> It seems like a change whose consequences need some attention ? >> >> What are others doing? >> >> Tim StÃ©phane Ducasse http://stephane.ducasse.free.fr 06 30 93 66 73 "If you knew today was your last day on earth, what would you do differently? ....ESPECIALLY if, by doing something different, today might not be your last day on earth.â Calvin & Hobbes

May 13, 2024

Re: P12 new Tonel formatting and PR implications

by Cyril FERLICOT-DELBECQUE

Hi, Here are some additional notes to what was already answered. If you want to convert all the files of a repository at once to avoid to have multiple PR with format changes you can use this script and commit the resulting files: | projectName | projectName := 'Spec2'. repository := IceRepository repositories detect: [ :repo | repo name = projectName ]. repository workingCopy packages do: [ :pkg | IceLibgitTonelWriter forInternalStoreFileOut: pkg latestVersion mcVersion on: repository ] Also, if you work on a project both in p12 and p11, you can avoid the ping pong by fixing a version of tonel in the properties file. The file to update is the .properties that is in the source folder and it should look like this: { #format : #tonel, #version: #'1.0' } P12 will take into account the tonel version asked and use it. In previous version of Pharo, this additional line will be ignored and Tonel v1 will be used. With both of those options it should be possible to reduce the pain of the format update. Have a nice day -- Cyril Ferlicot-Delbecque https://ferlicot.fr On Sunday, May 12th, 2024 at 12:21 PM, Tim Mackinnon <tim(a)testit.works> wrote: > Asking this here as it didnât get much traction on Discord - but with the move to P12, the category format in Tonel has changed from a symbol to a string e.g. { #category : #examples } vs { #category : 'examples' } - this causes mega noise when submitting tiny PR's - how is everyone else handling this? Should projects resave every project module to get the new format while people are out of the pool? Or is there a way to force the old format on specific projects until they can be upgraded ? > > It seems like a change whose consequences need some attention ? > > What are others doing? > > Tim

May 13, 2024

Re: The System Browser has recently started showing 2 comments tabs - one is text and one is formatted pretty. That seems odd and is not wanted...

by stephane ducasse

we have the unique feature or rewriting deprecation now this is true is this is why tests help a lot. I migrate regularly all our software: microdown, pillar, moose and more. And this is life. Now do not expect that all the suddent Pharo 10 will improve and see bug fixed. Even apple or microsoft or oracle do not support for free old versions. And the fixed versions of P10 is called P11 and P12. S > On 13 May 2024, at 05:15, Davide Varvello via Pharo-users <pharo-users(a)lists.pharo.org> wrote: > > Switch version is never pain free. > Davide > > > > > > > > On Monday, May 13, 2024 at 11:05:39 AM GMT+2, stephane ducasse <stephane.ducasse(a)inria.fr> wrote: > > > > > > I understand. > Can you tell us what is blocking you to switch versions? > > > You should know that we did an amazing amount of job fixing a lot of glitches and improving > Pharo over the last two years. > > Would you be interested in a special support for Pharo10 and at which price? Because we were thinking > about a LTS for Pharo but this is not free :). > > Have fun. > > > >>> On Sunday, May 12, 2024 at 11:26:02 AM GMT+2, stephane ducasse <stephane.ducasse(a)inria.fr> wrote: >> >> >>> Not really. Did you check in Pharo 12? >> >> No, I can't switch Pharo version and I don't think is so uncommon to stay on a stable version for a while. >> Davide >> >> >> >>> We got too busy on more important issues. >> >>> S >> >> >> >> >> >>> On 9 May 2024, at 11:43, Davide Varvello via Pharo-users <pharo-users(a)lists.pharo.org> wrote: >>> >>> >>> >>> Hi Guys, >>> >>> Any news about this issue? It's happening also to me. >>> >>> Cheers >>> Davide >>> >>> >>> >>> >>> >>> >>> On Monday, January 9, 2023 at 07:03:43 AM GMT+1, Mark O'Donoghue <mark.odonoghue.2010(a)gmail.com> wrote: >>> >>> >>> >>> >>> >>> Hi Stephane >>> >>> Many thanks for following up on the issue with the extra comment tab in the System Browser. >>> >>> As requested, I have included more information below: >>> >>> Versions >>> Over the last few days, I have seen the issue in >>> Build information: Pharo-10.0.0+build.536.sha.2314c3f457171dcde477ff6575b578835f1fd519 (64 Bit) >>> I believe this is the latest stable P10 release for Windows 64. >>> It was created as a new image via Pharo Launcher version: 3.0.1 >>> >>> Previously I was using >>> Build information: Pharo-10.0.0+build.515.sha.b18847fed2389428342d35b0056824644a1ce5fe (64 Bit) >>> And I was getting the normal comment tab behaviour. >>> I still can see that when I fire up that old image. >>> >>> Background >>> I had not used Pharo since July 2022, and before resuming work I decided to create a fresh new P10 image to work with. >>> Using the launcher, I created a new image based on the Pharo 10 (stable) image. And of course it updated the Windows 64 VM as well for me. >>> I then reloaded my code base and started work. Pretty soon I noticed the odd behaviour with the System Browser. >>> I then posed the question on discord for guidance. >>> >>> Since then, I tried to simplify the issue by creating another new image based on Pharo 10 (stable). >>> This time I didnât make any changes, alter settings, or loading any code or libraries. >>> I checked the simple image and verified that the System Browser issue was happening. >>> Because this is just the âvanillaâ image, unchanged by me, I a hoping it will be easy to verify this behaviour at your endâ¦ >>> >>> >>> Cheers and regards >>> Mark >>> Perth, Western Australia >>> >>> From: stephane ducasse <stephane.ducasse(a)inria.fr> Sent: Sunday, 8 January 2023 10:43 PMTo: Any question about pharo is welcome <pharo-users(a)lists.pharo.org>Subject: [Pharo-users] Re: The System Browser has recently started showing 2 comments tabs - one is text and one is formatted pretty. That seems odd and is not wanted - has anyone else seen this? Pharo 10 stable image - windows 64 - all reloaded recently... >>> >>> Hi mark >>> >>> Which version of Pharo are you using? >>> In P11 I saw some regressions. >>> S >>> >>> >>>> On 8 Jan 2023, at 14:30, mark.odonoghue.2010(a)gmail.com wrote: >>>> >>>> >>> >>> >>> >> >> >> StÃ©phane Ducasse >> http://stephane.ducasse.free.fr >> 06 30 93 66 73 >> >> "If you knew today was your last day on earth, what would you do differently? ....ESPECIALLY if, by doing something different, today might not be your last day on earth.â Calvin & Hobbes >> >> >> >> >> >> > > > StÃ©phane Ducasse > http://stephane.ducasse.free.fr > 06 30 93 66 73 > > "If you knew today was your last day on earth, what would you do differently? ....ESPECIALLY if, by doing something different, today might not be your last day on earth.â Calvin & Hobbes > > > > StÃ©phane Ducasse http://stephane.ducasse.free.fr 06 30 93 66 73 "If you knew today was your last day on earth, what would you do differently? ....ESPECIALLY if, by doing something different, today might not be your last day on earth.â Calvin & Hobbes

May 13, 2024

Re: The System Browser has recently started showing 2 comments tabs - one is text and one is formatted pretty. That seems odd and is not wanted...

by Davide Varvello

Switch version is never pain free. Davide On Monday, May 13, 2024 at 11:05:39 AM GMT+2, stephane ducasse <stephane.ducasse(a)inria.fr> wrote: I understand. Can you tell us what is blocking you to switch versions? You should know that we did an amazing amount of job fixing a lot of glitches and improving Â Pharo over the last two years.Â Would you be interested in a special support for Pharo10 and at which price? Because we were thinking about a LTS for Pharo but this is not free :). Have fun.Â >> On Sunday, May 12, 2024 at 11:26:02 AM GMT+2, stephane ducasse <stephane.ducasse(a)inria.fr> wrote:Â > > >> Not really. Did you check in Pharo 12?Â > > No, I can't switch Pharo version and I don't think is so uncommon to stay on a stable version for a while. > DavideÂ > > > >> We got too busy on more important issues. > >> S > > > > > >> On 9 May 2024, at 11:43, Davide Varvello via Pharo-users <pharo-users(a)lists.pharo.org> wrote: >> >> >> >> Hi Guys, >> >> Any news about this issue? It's happening also to me. >> >> Cheers >> Davide >> >> >> >> >> Â Â >> Â Â >> Â Â On Monday, January 9, 2023 at 07:03:43 AM GMT+1, Mark O'Donoghue <mark.odonoghue.2010(a)gmail.com> wrote: >> >> >> >> >> >> Hi Stephane >> Â Â Â >> Many thanks for following up on the issue with the extra comment tab in the System Browser. >> Â Â Â >> As requested, I have included more information below: >> Â Â Â >> Versions >> Over the last few days, I have seen the issue in >> Build information: Pharo-10.0.0+build.536.sha.2314c3f457171dcde477ff6575b578835f1fd519 (64 Bit) >> I believe this is the latest stable P10 release for Windows 64. >> It was created as a new image via Pharo Launcher version: 3.0.1 >> Â Â Â >> Previously I was using >> Build information: Pharo-10.0.0+build.515.sha.b18847fed2389428342d35b0056824644a1ce5fe (64 Bit) >> And I was getting the normal comment tab behaviour. >> I still can see that when I fire up that old image. >> Â Â Â >> Background >> I had not used Pharo since July 2022, and before resuming work I decided to create a fresh new P10 image to work with. >> Using the launcher, I created a new image based on the Pharo 10 (stable) image. And of course it updated the Windows 64 VM as well for me. >> I then reloaded my code base and started work. Pretty soon I noticed the odd behaviour with the System Browser. >> I then posed the question on discord for guidance. >> Â Â Â >> Since then, I tried to simplify the issue by creating another new image based on Pharo 10 (stable). >> This time I didnât make any changes, alter settings, or loading any code or libraries. >> I checked the simple image and verified that the System Browser issue was happening. >> Because this is just the âvanillaâ image, unchanged by me, I a hoping it will be easy to verify this behaviour at your endâ¦ >> Â Â Â >> Â Â Â >> Cheers and regards >> Mark >> Perth, Western Australia >> Â Â Â >> From: stephane ducasse <stephane.ducasse(a)inria.fr> Sent: Sunday, 8 January 2023 10:43 PMTo: Any question about pharo is welcome <pharo-users(a)lists.pharo.org>Subject: [Pharo-users] Re: The System Browser has recently started showing 2 comments tabs - one is text and one is formatted pretty. That seems odd and is not wanted - has anyone else seen this? Pharo 10 stable image - windows 64 - all reloaded recently... >> Â Â Â >> Hi markÂ >> Â Â Â >> Which version of Pharo are you using? >> In P11 I saw some regressions. >> S >> >> >>> On 8 Jan 2023, at 14:30, mark.odonoghue.2010(a)gmail.com wrote: >>> Â Â Â >>> >> Â Â Â >> >> > > > StÃ©phane Ducasse > http://stephane.ducasse.free.fr > 06 30 93 66 73 > > "If you knew today was your lastÂ day on earth, what wouldÂ youÂ do differently? ....ESPECIALLYÂ if, by doing somethingÂ different,Â today mightÂ notÂ be your last dayÂ on earth.â CalvinÂ & Hobbes > > > > > > StÃ©phane Ducasse http://stephane.ducasse.free.fr 06 30 93 66 73 "If you knew today was your lastÂ day on earth, what wouldÂ youÂ do differently? ....ESPECIALLYÂ if, by doing somethingÂ different,Â today mightÂ notÂ be your last dayÂ on earth.â CalvinÂ & Hobbes

May 13, 2024

The System Browser has recently started showing 2 comments tabs - one is text and one is formatted pretty. That seems odd and is not wanted...

by Davide Varvello

From: Davide Varvello <varvello(a)yahoo.com> To: stephane ducasse <stephane.ducasse(a)inria.fr> Sent: Monday, May 13, 2024 at 10:43:37 AM GMT+2 Subject: Re: [Pharo-users] The System Browser has recently started showing 2 comments tabs - one is text and one is formatted pretty. That seems odd and is not wanted... > On Sunday, May 12, 2024 at 11:26:02 AM GMT+2, stephane ducasse <stephane.ducasse(a)inria.fr> wrote:Â > Not really. Did you check in Pharo 12?Â No, I can't switch Pharo version and I don't think is so uncommon to stay on a stable version for a while. DavideÂ > We got too busy on more important issues. >S > On 9 May 2024, at 11:43, Davide Varvello via Pharo-users <pharo-users(a)lists.pharo.org> wrote: > > > > Hi Guys, > > Any news about this issue? It's happening also to me. > > Cheers > Davide > > > > >Â Â >Â Â >Â Â On Monday, January 9, 2023 at 07:03:43 AM GMT+1, Mark O'Donoghue <mark.odonoghue.2010(a)gmail.com> wrote: > > > > > > Hi Stephane >Â Â Â > Many thanks for following up on the issue with the extra comment tab in the System Browser. >Â Â Â > As requested, I have included more information below: >Â Â Â > Versions > Over the last few days, I have seen the issue in > Build information: Pharo-10.0.0+build.536.sha.2314c3f457171dcde477ff6575b578835f1fd519 (64 Bit) > I believe this is the latest stable P10 release for Windows 64. > It was created as a new image via Pharo Launcher version: 3.0.1 >Â Â Â > Previously I was using > Build information: Pharo-10.0.0+build.515.sha.b18847fed2389428342d35b0056824644a1ce5fe (64 Bit) > And I was getting the normal comment tab behaviour. > I still can see that when I fire up that old image. >Â Â Â > Background > I had not used Pharo since July 2022, and before resuming work I decided to create a fresh new P10 image to work with. > Using the launcher, I created a new image based on the Pharo 10 (stable) image. And of course it updated the Windows 64 VM as well for me. > I then reloaded my code base and started work. Pretty soon I noticed the odd behaviour with the System Browser. > I then posed the question on discord for guidance. >Â Â Â > Since then, I tried to simplify the issue by creating another new image based on Pharo 10 (stable). > This time I didnât make any changes, alter settings, or loading any code or libraries. > I checked the simple image and verified that the System Browser issue was happening. > Because this is just the âvanillaâ image, unchanged by me, I a hoping it will be easy to verify this behaviour at your endâ¦ >Â Â Â >Â Â Â > Cheers and regards > Mark > Perth, Western Australia >Â Â Â > From: stephane ducasse <stephane.ducasse(a)inria.fr> Sent: Sunday, 8 January 2023 10:43 PMTo: Any question about pharo is welcome <pharo-users(a)lists.pharo.org>Subject: [Pharo-users] Re: The System Browser has recently started showing 2 comments tabs - one is text and one is formatted pretty. That seems odd and is not wanted - has anyone else seen this? Pharo 10 stable image - windows 64 - all reloaded recently... >Â Â Â > Hi markÂ >Â Â Â > Which version of Pharo are you using? > In P11 I saw some regressions. > S > > >> On 8 Jan 2023, at 14:30, mark.odonoghue.2010(a)gmail.com wrote: >>Â Â Â >> >Â Â Â > > StÃ©phane Ducasse http://stephane.ducasse.free.fr 06 30 93 66 73 "If you knew today was your lastÂ day on earth, what wouldÂ youÂ do differently? ....ESPECIALLYÂ if, by doing somethingÂ different,Â today mightÂ notÂ be your last dayÂ on earth.â CalvinÂ & Hobbes

May 13, 2024

Re: P12 new Tonel formatting and PR implications

by Tim Mackinnon

Hey Esteban - understood. So it sounds like - quickly walk through all your project packages - add a little comment "upgrade to new tonel formt" and then commit (with everyone checked in before) sounds like the way to go. I'll get on that with projects that I work with. It does of course imply everyone move up to P12 (from P11) to avoid flip flopping between formats - and I don't think there is any reason to stick to P11 as P12 seems solid and without anything controversial to hold back on. Thanks for pushing things forward. Tim On Mon, 13 May 2024, at 6:31 AM, Esteban Lorenzano via Pharo-users wrote: > Hi, > > This is indeed a noisy change. That's the reason it was a change we were holding back during years, but at a point we needed to do it (there is a spec for tonel format we made together with Gemstone people and at a point, we needed to go to the agreed definition. > > So, yes... this will cause annoying moments until all projects are migrated. My recommendation is to make a PR with the new format and work from there. > > Esteban > > ps: there will be still some noise, next year, since we need to clean up a bit around... I am sorry in advance. > > On 12/05/2024 23:55, stephane ducasse wrote: >> The team will be back from vacationâ¦. last week was a three free days week :). >> >> S >> >>> On 12 May 2024, at 06:21, Tim Mackinnon <tim(a)testit.works> wrote: >>> >>> Asking this here as it didnât get much traction on Discord - but with the move to P12, the category format in Tonel has changed from a symbol to a string e.g. { #category : #examples } vs { #category : 'examples' } - this causes mega noise when submitting tiny PR's - how is everyone else handling this? Should projects resave every project module to get the new format while people are out of the pool? Or is there a way to force the old format on specific projects until they can be upgraded ? >>> >>> It seems like a change whose consequences need some attention ? >>> >>> What are others doing? >>> >>> Tim >> >> StÃ©phane Ducasse >> http://stephane.ducasse.free.fr >> 06 30 93 66 73 >> >> "If you knew today was your last day on earth, what would you do differently? ....ESPECIALLY if, by doing something different, today might not be your last day on earth.â Calvin & Hobbes >> >>

May 13, 2024

This week (19/2024) on the Pharo Issue Tracker

by Marcus Denker

# Pharo 12 - 16576-Problem-with-completion-in-the-tutorial #16582 https://github.com/pharo-project/pharo/pull/16582 # Virtual Machine - Bump to MacOS 11 and above #792 https://github.com/pharo-project/pharo-vm/pull/792 - Do not use asserta: in a statement #788 https://github.com/pharo-project/pharo-vm/pull/788 - Moving pharo.signatures files for OSX Bundle to Resources folder #770 https://github.com/pharo-project/pharo-vm/pull/770 # Features - New debugger extension model to display dynamic extensions #739 https://github.com/pharo-spec/NewTools/pull/739 - add asAccessor #16579 https://github.com/pharo-project/pharo/pull/16579 - Make it easier to diagnose mock failures by printing message sends properly and storing the send history in the mock #16555 https://github.com/pharo-project/pharo/pull/16555 - add two's complement display for negative integers #746 https://github.com/pharo-spec/NewTools/pull/746 # Fixes - Make ToggleMenuItemMorph use a FormSet for the submenu marker #16510 https://github.com/pharo-project/pharo/pull/16510 - Taskbar option to close windows hidden behind other windows #16552 https://github.com/pharo-project/pharo/pull/16552 - prof stef lesson view did not understand has binding of #16578 https://github.com/pharo-project/pharo/pull/16578 - fix precedence computation #16581 https://github.com/pharo-project/pharo/pull/16581 # Refactoring Engine - Fix RBCompositeRefactoryChange>>#defineClass: argument name #16600 https://github.com/pharo-project/pharo/pull/16600 - Refactor: preconditions return array of preconditions by default #16527 https://github.com/pharo-project/pharo/pull/16527 # Rules - add ReOverridingExtentsionMethod rule #16550 https://github.com/pharo-project/pharo/pull/16550 - add rule to avoid that TestCase rely on Initialize #16513 https://github.com/pharo-project/pharo/pull/16513 # Tests (Green tests on CI) - Fix testCodeCruftLeftInMethods #16598 https://github.com/pharo-project/pharo/pull/16598 - Update roassal to v1.06d #16595 https://github.com/pharo-project/pharo/pull/16595 - Fixing reflectivity tests that can randomly fail because of unstable and unpredictable tests generating methods #16584 https://github.com/pharo-project/pharo/pull/16584 - 16569-CI-Pharo13-code-with-halt-was-merged #16570 https://github.com/pharo-project/pharo/pull/16570 - clearing debugger subscriptions and subcomponents in StDebuggerExtensionMechanismTest>>#tearDown #712 https://github.com/pharo-spec/NewTools/pull/712 # Cleanups - Renaming DebugPointSideEffect into DebugPointMetaBehavior #16563 https://github.com/pharo-project/pharo/pull/16563 - Cleanup: TestCase class>>#lastRunMethodNamed: #16588 https://github.com/pharo-project/pharo/pull/16588 - Cleanup: TestCase class>>#hasErrorTest, TestCase class>>#hasPassedTest and TestCase class>>#hasFailedTest #16586 https://github.com/pharo-project/pharo/pull/16586 - Changed 'Transcript show:' construct to 'self trace' #16385 https://github.com/pharo-project/pharo/pull/16385 - removing dependency to UIManager in StFuelStackCommand #745 https://github.com/pharo-spec/NewTools/pull/745 # Documentation - Update CONTRIBUTING.md #16575 https://github.com/pharo-project/pharo/pull/16575

May 13, 2024

Re: P12 new Tonel formatting and PR implications

by Esteban Lorenzano

Hi, This is indeed a noisy change. That's the reason it was a change we were holding back during years, but at a point we needed to do it (there is a spec for tonel format we made together with Gemstone people and at a point, we needed to go to the agreed definition. So, yes... this will cause annoying moments until all projects are migrated. My recommendation is to make a PR with the new format and work from there. Esteban ps: there will be still some noise, next year, since we need to clean up a bit around... I am sorry in advance. On 12/05/2024 23:55, stephane ducasse wrote: > The team will be back from vacationâ¦. last week was a three free days > week :). > > S > >> On 12 May 2024, at 06:21, Tim Mackinnon <tim(a)testit.works> wrote: >> >> Asking this here as it didnât get much traction on Discord - but with >> the move to P12, the category format in Tonel has changed from a >> symbol to a string e.g. Â { #category : #examples } vs { #category : >> 'examples' } - this causes mega noise when submitting tiny PR's - how >> is everyone else handling this? Should projects resave every project >> module to get the new format while people are out of the pool? Or is >> there a way to force the old format on specific projects until they >> can be upgraded ? >> >> It seems like a change whose consequences need some attention ? >> >> What are others doing? >> >> Tim > > StÃ©phane Ducasse > http://stephane.ducasse.free.fr > 06 30 93 66 73 > > "If you knew today was your lastÂ day on earth, what wouldÂ youÂ do > differently? ....ESPECIALLYÂ if, by doing somethingÂ different,Â today > mightÂ notÂ be your last dayÂ on earth.â CalvinÂ & Hobbes > > > > >

May 13, 2024

Re: P12 new Tonel formatting and PR implications

by stephane ducasse

The team will be back from vacationâ¦. last week was a three free days week :). S > On 12 May 2024, at 06:21, Tim Mackinnon <tim(a)testit.works> wrote: > > Asking this here as it didnât get much traction on Discord - but with the move to P12, the category format in Tonel has changed from a symbol to a string e.g. { #category : #examples } vs { #category : 'examples' } - this causes mega noise when submitting tiny PR's - how is everyone else handling this? Should projects resave every project module to get the new format while people are out of the pool? Or is there a way to force the old format on specific projects until they can be upgraded ? > > It seems like a change whose consequences need some attention ? > > What are others doing? > > Tim StÃ©phane Ducasse http://stephane.ducasse.free.fr 06 30 93 66 73 "If you knew today was your last day on earth, what would you do differently? ....ESPECIALLY if, by doing something different, today might not be your last day on earth.â Calvin & Hobbes

May 12, 2024

P12 new Tonel formatting and PR implications

by Tim Mackinnon

Asking this here as it didnât get much traction on Discord - but with the move to P12, the category format in Tonel has changed from a symbol to a string e.g. { #category : #examples } vs { #category : 'examples' } - this causes mega noise when submitting tiny PR's - how is everyone else handling this? Should projects resave every project module to get the new format while people are out of the pool? Or is there a way to force the old format on specific projects until they can be upgraded ? It seems like a change whose consequences need some attention ? What are others doing? Tim

May 12, 2024

Re: Window size: look at ClyBrowserMorph>>initialExtent

by stephane ducasse

+ 1000 S > On 10 May 2024, at 13:03, Tim Mackinnon <tim(a)testit.works> wrote: > > Davide - why don't you submit a PR? I'm sure you can figure out how to add a settings to the system (can't offhand remember, but there are examples - and you can ask on the discord) and it would be a nice contribution to make . > > Its all the little contributions that make the system better - I know I've been there, and saw how the others do it and so had a go. > > Tim > > On Fri, 10 May 2024, at 5:25 PM, Davide Varvello via Pharo-users wrote: >> Hi Guys, >> It seems to me the default size of a lot of windows is too small, so after some search and thanks to this https://stackoverflow.com/questions/55102480/how-do-i-change-the-default-he… by Marko GrdiniÄ >> >> I discovered I can change the default size of many type of windows simply changing ClyBrowserMorph>>initialExtent. >> HTH >> >> It would be good to be able to manage the size of windows in Settings >> >> Cheers >> Davide StÃ©phane Ducasse http://stephane.ducasse.free.fr 06 30 93 66 73 "If you knew today was your last day on earth, what would you do differently? ....ESPECIALLY if, by doing something different, today might not be your last day on earth.â Calvin & Hobbes

May 12, 2024

Re: The System Browser has recently started showing 2 comments tabs - one is text and one is formatted pretty. That seems odd and is not wanted...

by stephane ducasse

Not really. Did you check in Pharo 12? We got too busy on more important issues. S > On 9 May 2024, at 11:43, Davide Varvello via Pharo-users <pharo-users(a)lists.pharo.org> wrote: > > Hi Guys, > > Any news about this issue? It's happening also to me. > > Cheers > Davide > > > > On Monday, January 9, 2023 at 07:03:43 AM GMT+1, Mark O'Donoghue <mark.odonoghue.2010(a)gmail.com> wrote: > > > Hi Stephane > > > Many thanks for following up on the issue with the extra comment tab in the System Browser. > > > As requested, I have included more information below: > > > Versions > > Over the last few days, I have seen the issue in > > Build information: Pharo-10.0.0+build.536.sha.2314c3f457171dcde477ff6575b578835f1fd519 (64 Bit) > > I believe this is the latest stable P10 release for Windows 64. > > It was created as a new image via Pharo Launcher version: 3.0.1 > > > Previously I was using > > Build information: Pharo-10.0.0+build.515.sha.b18847fed2389428342d35b0056824644a1ce5fe (64 Bit) > > And I was getting the normal comment tab behaviour. > > I still can see that when I fire up that old image. > > > Background > > I had not used Pharo since July 2022, and before resuming work I decided to create a fresh new P10 image to work with. > > Using the launcher, I created a new image based on the Pharo 10 (stable) image. And of course it updated the Windows 64 VM as well for me. > > I then reloaded my code base and started work. Pretty soon I noticed the odd behaviour with the System Browser. > > I then posed the question on discord for guidance. > > > Since then, I tried to simplify the issue by creating another new image based on Pharo 10 (stable). > > This time I didnât make any changes, alter settings, or loading any code or libraries. > > I checked the simple image and verified that the System Browser issue was happening. > > Because this is just the âvanillaâ image, unchanged by me, I a hoping it will be easy to verify this behaviour at your endâ¦ > > > > Cheers and regards > > Mark > > Perth, Western Australia > > > From: stephane ducasse <stephane.ducasse(a)inria.fr> > Sent: Sunday, 8 January 2023 10:43 PM > To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > Subject: [Pharo-users] Re: The System Browser has recently started showing 2 comments tabs - one is text and one is formatted pretty. That seems odd and is not wanted - has anyone else seen this? Pharo 10 stable image - windows 64 - all reloaded recently... > > > Hi mark > > > Which version of Pharo are you using? > > In P11 I saw some regressions. > > S > > > > > On 8 Jan 2023, at 14:30, mark.odonoghue.2010(a)gmail.com <mailto:mark.odonoghue.2010@gmail.com> wrote: > > > > StÃ©phane Ducasse http://stephane.ducasse.free.fr 06 30 93 66 73 "If you knew today was your last day on earth, what would you do differently? ....ESPECIALLY if, by doing something different, today might not be your last day on earth.â Calvin & Hobbes

May 12, 2024

Re: Window size: look at ClyBrowserMorph>>initialExtent

by Tim Mackinnon

Davide - why don't you submit a PR? I'm sure you can figure out how to add a settings to the system (can't offhand remember, but there are examples - and you can ask on the discord) and it would be a nice contribution to make . Its all the little contributions that make the system better - I know I've been there, and saw how the others do it and so had a go. Tim On Fri, 10 May 2024, at 5:25 PM, Davide Varvello via Pharo-users wrote: > Hi Guys, > It seems to me the default size of a lot of windows is too small, so after some search and thanks to this https://stackoverflow.com/questions/55102480/how-do-i-change-the-default-he… by Marko GrdiniÄ > > I discovered I can change the default size of many type of windows simply changing *ClyBrowserMorph>>initialExtent.* > HTH > > It would be good to be able to manage the size of windows in Settings > > Cheers > Davide >

May 10, 2024