- Pharo-dev - lists.pharo.org

[Pharo 8.0] Build #699: 4401-bis-ZipArchive-should-not-convert-FileReference-to-paths
by ci-pharo-ci-jenkins2＠inria.fr Sept. 5, 2019

Sept. 5, 2019

There is a new Pharo build available! The status of the build #699 was: FAILURE. The Pull Request #4473 was integrated: "4401-bis-ZipArchive-should-not-convert-FileReference-to-paths" Pull request url: https://github.com/pharo-project/pharo/pull/4473 Issue Url: https://github.com/pharo-project/pharo/issues/4401 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Pharo Branding Organization on GitHub
by Torsten Bergmann Sept. 5, 2019

Sept. 5, 2019

Hi, the Pharo community is growing and our lovely Pharo system is an innovation driver with cool tools and projects but it is also used in real projects in research and business setups. There are still many entries left on all our TODO lists - not only in shaping the next stable Pharo release(s) but also in bringing more attention to people about what Pharo is all about. A few of us already follow a well know marketing phrase: âDo good and talk about it!â as some report about Pharo news in BLOGS, on TWITTER or by writing articles on MEDIUM.com or even books. I also like that we have a growing number of YOUTUBE videos about Pharo. We also have a regular Newsletter - even a Facebook page, ... This gives visibility to Pharo activities and is already a good step in doing some advertising. An additional important lesson in successful marketing is that one has to give a homogenous "Brand Identity" to a project or product to be easily recognizable and rememberable over time. We already have the nice lighthouse and use it all over - but often it is hard to find the logo or other marketing material in correct size or correct graphics format. We should improve on that side too. As we work mostly with git I therefore now have setup a new organization "pharo-brand": https://github.com/pharo-brand that should give easy access and group existing branding material in one place. The site now already includes the following three projects: 1. pharo-brand-material This should be the place for "logo" and "logo-flat". In the subdirectories you will find the logo in three different variations: - logo composed of text + icon + beacon - logo composed of icon + beacon - logo beacon only including subdirectories for "vector" (like SVG, PDF) and "screen" formats (like PNG, BMP, ...) 2. pharo-github-images These are the Icons i created for the various github organizations like - https://github.com/pharo-project - https://github.com/pharo-nosql - https://github.com/pharo-rdbms - https://github.com/pharo-contributions - https://github.com/pharo-brand and a template for additional ones 3. pharo-jingle A jingle is a short song or tune used in advertising. Jingles are a form of sound and or video branding - when you see it often as an intro or outro you will more easily remember the brand name (Pharo in this case). This repository includes a "Pharo jingle" that can be used as a start or end section within own custom videos about Pharo and related projects. The short video jingle was created using a free video software called OpenShot using a sound jingle from freesound.org - Pharo_HDV720_24p_1280x720.mp4 - Pharo_HDV1080_25p_1920x1080.mp4 - Pharo_HDV1440_25p_1440x1080.mp4 Note that the jingle is currently a proposal - if you have better ones we can discuss it within the community on the mailinglist. I hope the repos will improve a little bit the situation in finding and organizing the brand material. Feel free to comment and give feedback or even add marketing material (templates, icons or other) yourself to the repos. Thanks T.

3 3

[Pharo 8.0] Build #698: Improving performance of athens
by ci-pharo-ci-jenkins2＠inria.fr Sept. 5, 2019

Sept. 5, 2019

There is a new Pharo build available! The status of the build #698 was: SUCCESS. The Pull Request #4464 was integrated: "Improving performance of athens" Pull request url: https://github.com/pharo-project/pharo/pull/4464 Issue Url: https://github.com/pharo-project/pharo/issues/improving Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

2 1

About tweets
by ducasse Sept. 5, 2019

Sept. 5, 2019

Hi guys I encourage everybody to read this issue until the last conversation. https://github.com/pharo-project/pharo/issues/4491 I have problem to promote an aggregator that can contain tweets containing #abortionismurder inside.!!!!!!!!! And I have even more problem that this is in a tweet on Amber Weekly!!!! I do not know who is behind AmberSmalltalk tweets but for me this is clearly impossible to read this on a tweet that Pharo supports. I also have a problem to promote an aggregator account We can provide a list and people what they want. I do not like the idea of aggregation. So I vote against and I will ask the board to decide. Stef

4 6

Fund rising for the new Spec20 book.
by StÃ©phane Ducasse Sept. 5, 2019

Sept. 5, 2019

Hello Pharoers and Smalltalk Friends Often you or other complain that there is not enough documentation, tutorialsâ¦. (even if we have a mooc worth 155 K euros http://mooc.pharo.org, several great books http://book.pharo.org) but yes we should update them. Now I started to work on a new book on Spec 20 with Cyril Ferlicot and I decided that I will not write it for free because it will take me at least 6 months. So I decided that if this community wants more books and documentation, it should prove its will :) I created a fundraising campaign to check if people can align their wishes and their means. So feel free to sponsor this great book. Building user interfaces with spec 20 â https://www.okpal.com/building-user-interfaces-with-spec/?utm_campaign=01DK… Organisations can also do it. BTW: the crowd funding system and other cost will cost us 10% and after we will pay taxes on this. So I prefer not to count our hour cost because else I would really not write a book at all. Stef -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr http://www.synectique.eu / http://www.pharo.org 03 59 35 87 52 Assistant: Julie Jonas FAX 03 59 57 78 50 TEL 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza Villeneuve d'Ascq 59650 France

3 3

[ANN] Pharo Headless - Beta (Actually what is between Alpha and Beta)
by tesonep＠gmail.com Sept. 5, 2019

Sept. 5, 2019

TL;DR; ====== For the anxious, you can get real headless vm and image from zero-conf. $ wget get.pharo.org/64/80+vmHeadlessLatest | bash Zero conf scripts remain unchanged for users. However, if you are launching the VM by hand from the executable instead of the launcher scripts (pharo and pharo-ui) as in $ ./pharoexecutable Pharo.image the image will launch in headless mode and will not open a window. To launch it in headfull, you can use the --interactive argument after the image, which will make the image open a window using SDL2. $ ./pharoexecutable Pharo.image --interactive Long version ============ Hi, this mail is the happy intermediate result of the work that us, the Pharo Consortium Team, has been doing in the last couple of months. Our main objective is to have a real headless implementation of Pharo where all the responsibility to open or not a World window (or other) is handled by the image. For doing so we have done a series of modifications in the image and the VM side. We consider this is the path that Pharo 8 and following versions should follow, as it will severely improve server-side and command line Pharo and in building custom desktop applications. These modifications are available only in 64-bits machines (Windows, OSX, and Linux). ARM32 and 64bits headless is in the roadmap, but it is delayed because we have prioritized our three major platforms for this first couple of months. All this work is based in Opensmalltalk-VM and Ronnie's initial work on headless. We are really grateful to all the contributors in the history of this nice product. To achieve a real headless VM we have brought modifications in the source tree because most of the platform code to open and manipulate windows is not required anymore. Instead, we use the SDL2 library that implements a nice layer on top of the OS and allows us to manage on the image side through FFI. So this mail is now an open call for (beta?)testing. The sources of the current VM we are building are in the headless branch in https://github.com/pharo-project/opensmalltalk-vm And we have set up a CI that is both building and testing the VM in https://ci.inria.fr/pharo-ci-jenkins2/job/pharo-vm/job/headless/ For the future we have a lot of ideas, that will wait for another long email or a beer-talk @ESUG. We want to hear your ideas!! Image-Side Improvements ======================= - The image handles the creation or not of the main world window. - We incorporated the idea of World renderer, where different backends are used to render the world. - We have 3 backends: VM support (compatibility with non-headless VMs), and OSWindow with two backends: SDL and GTK3+. - The modifications in the image are fully backward compatible with the non-headless VM and are pushed since weeks in the latest 8.0 image. - We move the handling of events to the image side when using SDL and GTK3+, opening the door to a richer set of events and finer-grained control over them. - SDL and GTK versions are implemented using FFI calls. VM-Side Improvements ==================== - VMMaker code migrated to Tonel thanks to Feenk and included in the repository of the VM. - Making VMMaker execute in Pharo 7 and 8. - Removing GPL code from the VM repository (GDB). - Slowly adding new tests for the JIT / Slang and VMGeneration. - Restructuring of the source code. - A new simpler CMake build. - Generate VM code from Slang on each build. - A CI process to validate (including the run of the tests in Pharo and the ones adding to the VM). - Simplification of the codebase. - Maximize the reuse of code between the platforms (preferring the standard versions over the platform-specific). - Cleaning up duplicated code. - All the plugins are now external plugins. - The VM is now a dynamic library. This is a first step towards embedding Pharo into other applications. - The main executable is a thin frontend (you can change it or implement your own). - Removing unused plugins. - Improved crash dump. Especially the crash dump works now in Windows 64bits. - Dummy implementation of Security plugin (it is going away.... eventually). - Cleanup of SSL, UUID, and Socket plugin. - Cleanup of conditional code (Still to improve). - Improving the types used in the functions (we have to be neat to be multiplatform/multi-arch). - Improving the lookup of modules - Improving the logging of the VM - Improving the handling of VM arguments Thanks a lot for reading so long!! We hope you enjoy the VM and please tell us all the problems you find!! Pablo, Guille, and Esteban

7 12

humanReadablePrintString
by Hilaire Sept. 4, 2019

Sept. 4, 2019

Hi, This code leads to an error: "On place 10'000 â¬ Ã un taux de 4 % par annÃ©e. Au bout de combien d'annÃ©es aura-t-on 20'000 â¬ ?" | annee | annee := [ :capital | Â Â Â ((capital / 10000) log / (1 + 0.04) log) years humanReadablePrintStringÂ ]. annee value: 20000 . #printWithCommasOn: is understood only by integer. In my opinion printHumanReadableOn: should be edited as: ../.. Â Â Â Â Â Â (wholeNanoseconds 'nanosecond')) do: [ :each | Â Â Â Â Â Â count := (self perform: each first) truncated. Â Â Â Â Â Â count > 0Â ../.. Opinion? Hilaire -- Dr. Geo http://drgeo.eu

2 2

[Pharo 8.0] Build #697: UFFI-introduce-FFIBit-type
by ci-pharo-ci-jenkins2＠inria.fr Sept. 4, 2019

Sept. 4, 2019

There is a new Pharo build available! The status of the build #697 was: FAILURE. The Pull Request #4471 was integrated: "UFFI-introduce-FFIBit-type" Pull request url: https://github.com/pharo-project/pharo/pull/4471 Issue Url: https://github.com/pharo-project/pharo/issues/UFFI Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Launcher: Missing version file for older Pharo
by Sean P. DeNigris Sept. 4, 2019

Sept. 4, 2019

Would it be possible to add a pharo.version file to the zip for older (<5.0) Pharos? Right now, Launcher can't determine the version and the file has to be created manually. Since those versions aren't getting updated, I would assume it's a one-time task. I didn't file a Launcher issue because I guess it's an issue with the file server, not with Launcher per se. ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

2 3

Epicea Feedback
by Sean P. DeNigris Sept. 4, 2019

Sept. 4, 2019

Not complaining at all and appreciate everyone's hard (mostly-unpaid) work, but providing raw feedback in case it's helpful... - Browser awkward: filters disappear whenever left selection changed; no multi-select of sessions, which led to a host of difficulties described below. - What is the heuristic to find API access points? Epicea package has no comment, 'Browser' tag doesn't seem to have an XyzBrowser class, no particular class in the 'Model' tag jumps out at me as an access point; as above Browser about text not set. I finally bring up Morphic halos on the browser and after flopping around, find subclasses of EpLogNode; I browse it and find EpLogNodeGraphModel, which sounds interesting and turns out to be a spec. I figure out how to list the log files, but not how to get the entries - I was expecting a term like that and the relevant method (#log it turns out) has no comment to indicate it's what I'm looking for. Now that I'm starting to understand the project organization, back to the browser to explore EpUnifiedBrowserModel. After a bit of poking around, I suspect (correctly) that #log is what I'm after. Based on code I extract from the browsers and a bit of experimenting in GT, I come up with the following seemingly very complex script: nodes := EpFileLogNode fromAllLogsIn: EpMonitor current sessionStore baseLocator. nodes do: [ :node | node populateReferencedNodesWith: nodes ]. nodes flatCollect: [ :n | n log events select: [ :e | e affectedPackageName beginsWith: 'Magritte' ] ] I now run into a series of problems because, although EpCodeChange declares #affectedPackageName as an abstract method, not all events are EpCodeChanges. I exclude EpUndos. Easy enough. Now I come to an EpGenericRefactoring. This one is harder because p.s. <rant>Code names for internal projects seem extremely counterproductive. Hiedra tells me absolutely nothing about functionality. It might as well be called XyzWidgetThing</rant> ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

2 4