December 2018 - Pharo-dev - lists.pharo.org

[Pharo 7.0] Build #38: 22767 Categorize uncategorized classes in Tool-Finder
by ci-pharo-ci-jenkins2＠inria.fr Dec. 14, 2018

Dec. 14, 2018

There is a new Pharo build available! The status of the build #38 was: SUCCESS. The Pull Request #2070 was integrated: "22767 Categorize uncategorized classes in Tool-Finder" Pull request url: https://github.com/pharo-project/pharo/pull/2070 Issue Url: https://pharo.fogbugz.com/f/cases/22767 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0] Build #37: 22766-Transcript-window-is-leaking
by ci-pharo-ci-jenkins2＠inria.fr Dec. 14, 2018

Dec. 14, 2018

There is a new Pharo build available! The status of the build #37 was: SUCCESS. The Pull Request #2071 was integrated: "22766-Transcript-window-is-leaking" Pull request url: https://github.com/pharo-project/pharo/pull/2071 Issue Url: https://pharo.fogbugz.com/f/cases/22766 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

glamorous toolkit: v0.4.0
by Tudor Girba Dec. 14, 2018

Dec. 14, 2018

Hi, Things are moving fast in the glamorous land. We now reached v0.4.0: https://gtoolkit.com There are several significant advances in this version. The first thing to note is that v0.4.0 is a reproducible version that can be loaded with: Metacello new baseline: 'GToolkit'; repository: 'github://feenkcom/gtoolkit:v0.4.0/src'; load. https://github.com/feenkcom/gtoolkit/releases/tag/v0.4.0 The version was created with Releaser the new member of GT that is able to release deeply nested projects: https://twitter.com/girba/status/1073407418460225536 The rest of the environment has seen a few key changes as well: - Documenter received support for dynamic markup edit. This is an almost magic ability that makes the markup appear when the cursor nears the markup. With this we have reached a seamless experience that supports both viewing without markup and editing on demand. https://twitter.com/feenkcom/status/1067879286143676419 - Playground uses Coder and snippets are now collapsable. https://twitter.com/feenkcom/status/1070806168459767809 - The Inspector updates when the code changes. https://twitter.com/feenkcom/status/1072581283925159936 https://twitter.com/feenkcom/status/1072107898900238337 - The Meta view from Inspector was enhanced to show the super classes and method categories, each of these act list filters. On top of that, we can also filter methods by name. https://twitter.com/feenkcom/status/1072223641583149057 A more complete list of issues we addressed is found here: https://github.com/feenkcom/gtoolkit/milestone/2?closed=1 Please do let us know what you think .. and, of course, what you feel. Have fun, The feenk team -- www.feenk.com âHow do you feenk today?"

1 0

LibC system pops up a CMD.exe window in Windows 10 (Pharo 6.1)
by Christopher Fuhrman Dec. 13, 2018

Dec. 13, 2018

Hello, My Git data mining API in Pharo 6.1 uses "LibC uniqueInstance system: 'some commands'" which has an annoying side effect of popping up a window (which steals the GUI focus in Windows 10). Maybe it's the same on MacOS and Linux? As such, I can't use my Windows PC to do anything else when the mining process is running (it can take several minutes). I'm not able to use Pharo's OSProcess or OSSubprocess because they don't support Windows (yet?). I tried creating a separate Windows Desktop (feature of Windows 10), but the CMD.EXE window manages to pop up there, too - almost seems like a windows bug. Does anyone know of a way to have the LibC window not pop up? Cheers, Christopher

5 9

Application entrypoints
by Ben Coman Dec. 13, 2018

Dec. 13, 2018

A question was asked on discord... "I know how to start the lights out example, and feed my objects test data with the testing framework, but how does one start something like ChineseCheckers? How does one find the entry point? Is there a convention on naming a starting place?" I remember having similar thoughts when starting in Pharo. One convention I have seen is that amongst all the classes presumably prefixed "CC" one class would stand out being named for the application without the prefix. e.g. class "ChineseCheckers". That is only a narrow chance for a namespace conflict, the the risk still remains. I suggested another path would have a package tag "Application" (i.e. "ChineseCheckers-Application") that contains a single class which has an #open method on the class-side. The tag "Application" sorts high up on the package-tags and is self-descriptive. But I've not seen that used before, so while I think its a good idea, its not really a convention. Conventions are only useful if they are broadly understood. So I'm wondering what other things people do to draw attention to their application entry points. cheers -ben

4 3

Problem loading a branch of my pharo fork in an image
by Thomas Dupriez Dec. 13, 2018

Dec. 13, 2018

Hello, I loaded a branch of my pharo fork in an image using iceberg, but the method I was interested in did not change for some reason (my branch's latest commit changes this method, but these changes were not visible in the image I loaded my branch in). Does someone has an idea of what could have happened? Did I do something wrong? Here's what I did step-by-step if that helps: - fresh pharo 7 image - open iceberg - repair repository "pharo" - Clicked "Clone again this repository" - Chose "Clone remote repository", and put the url of my pharo fork: "https://github.com/dupriezt/pharo" - ok - wait for loading bar to complete - pharo repo is marked as "Fetch required. Unknown 67dc1e8" - repair repository "pharo" - chose "Discard local changes and checkout an existing branch" - chose the branch "BreakpointBrowser" from the "origin" remote - Clicked "checkout" on the checkout preview window - wait for loading bar to complete - browse the method WorldState class>>debugOn: - It is different from the last commit I made to this branch (https://github.com/dupriezt/pharo/commit/ead94e32f138eb435a95cd889f77ca39d4…) Thomas Dupriez

1 1

â¹Programmingâº 2019 Combined Call for Workshop Submissions
by Fabio Niephaus Dec. 13, 2018

Dec. 13, 2018

=========================================================================== â¹Programmingâº 2019 Combined Call for Workshop Submissions =========================================================================== To build a community and to foster an environment where participants can exchange ideas and experiences related to practical software development, â¹Programmingâº will host a number of workshops, during the days before the main conference. The workshops will provide a collaborative forum to exchange recent and/or preliminary results, to conduct intensive discussions on a particular topic, or to coordinate efforts between representatives of a technical community. They are intended as a forum for lively discussion of innovative ideas, recent progress, or practical experience on programming and applied software development in general for specific aspects, specific problems, or domain-specific needs. We also encourage practical, hands-on workshops in which participants actually experience one or several aspects of practical software development. The following workshops are co-located with â¹Programmingâº 2019. MoreVMsâ19: Workshop on Modern Language Runtimes, Ecosystems, and VMs --------------------------------------------------------------------------- MoreVMsâ19 aims to bring together industrial and academic programmers to discuss the design, implementation, and usage of modern languages and runtimes. Possible topics include reuse of language runtimes, modular implementation, language design, and compilation strategies. Call: https://2019.programming-conference.org/track/MoreVMs-2019 Extended Abstract Deadline: 11 Jan 2019 PX/19 5th Edition of the Programming Experience Workshop --------------------------------------------------------------------------- The Programming Experience (PX) Workshop is about what happens in that room when programmers sit down in front of computers and produce code, especially in an exploratory way. We are interested in this experience of programming and how to improve and evolve it. Call: https://2019.programming-conference.org/track/px-2019-papers Submission Deadline: 27 Jan 2019 VPT 2019: Seventh International Workshop on Program Transformation and Verification --------------------------------------------------------------------------- The aim of the workshop is to bring together researchers working in the fields of Program Verification and Program Transformation. There is a great potential for beneficial interactions between these two area. The workshop will provide a forum where researchers from these fields may interact and foster new developments. The workshop solicits research, position, application, and system description papers with a special emphasis on case studies, demonstrating viability of the interactions between the research fields of program transformation and program verification in a broad sense. Call: http://refal.botik.ru/vpt/vpt2019/ Submission Deadline: 8 Jan 2019 LANGETIâ19: Languages and Tools for Next Generation Testing --------------------------------------------------------------------------- The LANGETI workshop invites for submission of research papers and tool demonstrations developing new languages and tools that explore novel techniques to test next generation applications. We specially encourage new ideas on testing and its application domain that will spark discussion during the workshop. Call: https://2019.programming-conference.org/track/langeti-2019-papers Submission Deadline: 11 Jan 2019 PASSâ19: Workshop on Programming Across the System Stack (PASS) â19 --------------------------------------------------------------------------- PASSâ19 seeks contributions at the interaction of programming languages and computer systems, such as programming abstractions for emerging platforms, runtime performance and energy optimization, software tool support for systems, systems-level reasoning and verification, language-based security, and systems programming and debugging. Call: https://2019.programming-conference.org/home/PASS-2019 Submission Deadline: 15 Jan 2019 ICW 2019: Interconnecting Code Workshop --------------------------------------------------------------------------- Modern computer systems are often loosely coupled compositions of heterogeneous components. An important part of modern programming is the art, science, and engineering of interconnecting disparate code components to offer larger services in a reliable and scalable manner. The goal of this workshop is to facilitate an ongoing discussion, and advance the state of the art of interconnecting code. Call: https://2019.programming-conference.org/track/icw-2019-papers Initial Abstract Deadline: 11 Jan 2019 Salon des RefusÃ©s 2019 --------------------------------------------------------------------------- Salon des RefusÃ©s was an 1863 exhibition of artworks rejected from the official Paris Salon. We bring the same to programming research, creating a space for interesting ideas that are difficult to reduce to a proof or a naive measurement. Call: https://shift-society.org/salon/call-for-papers Submission Deadline: 7 Jan 2019 MiniPLoP 2019 --------------------------------------------------------------------------- Patterns are a systematic way to capture the experience of experts about good designs or best practices and document these nuggets of wisdom in an accessible way for peers. You can submit papers with 2-3 patterns for a discussion in a Writerâs Workshop session. Call: https://2019.programming-conference.org/track/PLOP-2019-papers Submission Deadline: 31 Jan 2019 ProWebâ19: 3rd International Workshop on Programming Technology for the Future Web --------------------------------------------------------------------------- ProWebâ19 is a forum for researchers and practitioners to share and discuss advances in programming technology (i.e., frameworks, libraries, programming languages, program analyses and development tools) for implementing web applications and for maintaining their quality over time, as well as experience reports about the use of state-of-the-art technology for the web. Call: https://2019.programming-conference.org/track/proweb-2019-papers Submission Deadline: 15 Jan 2019

1 0

[Pharo 7.0] Build #36: 22762 Cleanup TextEditorTest
by ci-pharo-ci-jenkins2＠inria.fr Dec. 13, 2018

Dec. 13, 2018

There is a new Pharo build available! The status of the build #36 was: FAILURE. The Pull Request #2066 was integrated: "22762 Cleanup TextEditorTest" Pull request url: https://github.com/pharo-project/pharo/pull/2066 Issue Url: https://pharo.fogbugz.com/f/cases/22762 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0] Build #35: 22763 Tag classes in Text-Diff package
by ci-pharo-ci-jenkins2＠inria.fr Dec. 13, 2018

Dec. 13, 2018

There is a new Pharo build available! The status of the build #35 was: SUCCESS. The Pull Request #2067 was integrated: "22763 Tag classes in Text-Diff package" Pull request url: https://github.com/pharo-project/pharo/pull/2067 Issue Url: https://pharo.fogbugz.com/f/cases/22763 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

periodic auto actions on bug tracker
by Ben Coman Dec. 13, 2018

Dec. 13, 2018

I support the auto-closing of old tickets to avoid bug bankruptcy. Sometimes things seem more important at the time and when my own tickets come back around I get to be more analytical about the effort/reward balance. It would be useful to expand this a bit to have a quarterly mail out saying something like "Is this issue still important to you? Try socializing it on the pharo-dev mail list. Issues going twelve months without interaction will be auto-closed". Then its not a bad surprise to new users when their ticket is auto-closed. cheers -ben

4 4