- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Launcher: Missing version file for older Pharo

by ducasse

Yes > On 4 Sep 2019, at 19:10, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > ducasse wrote >> Can you open a bug entry > > Sure. For Launcher? > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html >

Sept. 4, 2019

Re: [Pharo-dev] Fund rising for the new Spec20 book.

by ducasse

Hi sean Thanks and sorry for the burden. I got some japanese supporters. So it should work internationally. Could you tell me your bank and I can ask the platform? > On 4 Sep 2019, at 19:04, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > The site said that my bank refused the transaction. I tried on two cards. > Does it work internationally? Is there another way to send the money? > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html >

Sept. 4, 2019

Re: [Pharo-dev] Launcher: Missing version file for older Pharo

by Sean P. DeNigris

ducasse wrote > Can you open a bug entry Sure. For Launcher? ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Sept. 4, 2019

Re: [Pharo-dev] Fund rising for the new Spec20 book.

by Sean P. DeNigris

The site said that my bank refused the transaction. I tried on two cards. Does it work internationally? Is there another way to send the money? ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Sept. 4, 2019

Re: [Pharo-dev] Launcher: Missing version file for older Pharo

by ducasse

yes now we should add in the todo and check Can you open a bug entry > On 4 Sep 2019, at 17:10, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > 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 >

Sept. 4, 2019

Re: [Pharo-dev] Epicea Feedback

by Sean P. DeNigris

Done: https://github.com/pharo-project/pharo/issues/4496 https://github.com/pharo-project/pharo/issues/4495 ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

Sept. 4, 2019

Pharo Branding Organization on GitHub

by Torsten Bergmann

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.

Sept. 4, 2019

Launcher: Missing version file for older Pharo

by Sean P. DeNigris

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

Sept. 4, 2019

[Pharo 8.0] Build #696: fix/blockprinting

by ci-pharo-ci-jenkins2＠inria.fr

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

Sept. 4, 2019

Re: [Pharo-dev] humanReadablePrintString

by Sven Van Caekenberghe

Yes, probably. > On 4 Sep 2019, at 15:32, Hilaire <hilaire(a)drgeo.eu> wrote: > > 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 > > >

Sept. 4, 2019