September 2019 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] About tweets

by Norbert Hartl

Ok, there seems to be some agreeable sense. Dealing with accounts of people tends to collect opinions and things not related to pharo. We are not interested in these. There are hashtags and mentions for things related to a topic. But a few (!) want to have more control. So using the @pharoproject account should be ok because we can like things to be includef from that account. Well at least the ones that have access to. Is this a proper summary? Norbert > Am 05.09.2019 um 08:48 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: > > Yes, I closed that issue. > > This is not going to happen, sorry :) > > Esteban > >> On 5 Sep 2019, at 08:03, ducasse <stepharo(a)netcourrier.com> wrote: >> >> 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 > >

Sept. 5, 2019

Re: [Pharo-dev] About tweets

by Esteban Lorenzano

Yes, I closed that issue. This is not going to happen, sorry :) Esteban > On 5 Sep 2019, at 08:03, ducasse <stepharo(a)netcourrier.com> wrote: > > 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

Sept. 5, 2019

About tweets

by ducasse

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

Sept. 5, 2019

Re: [Pharo-dev] Floating-point numbers with radix (non-decimal)?

by ducasse

Hi nicolas let us fix this :) why 15r1.2e1 is not working? why 15r1.2e1 is not equals to 15r1.2E1? why would we need a new syntax? Stef > On 5 Sep 2019, at 00:19, Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> wrote: > > Once upon a time, only uppercase letters were accpeted as extra digits (in base > 10) for both int and float > > Then 15r1.2E1 was not 15r1.2e1, the later being = 15r12.E > > Then it was considered better to understand hexadecimal numbers with lowercase too... > and alternate-base Float became ambiguous and were never fixed :( > > This would deserve a new syntax, I don't know what makes sense, 15r1.2_e1 15r1.2#e1 ... > Changing Smalltalk syntax is among the most difficult decisions, expect outcry ;) > Maybe because it's too easy :) > > > Le jeu. 5 sept. 2019 Ã 00:04, James Foster <Smalltalk(a)jgfoster.net <mailto:Smalltalk@jgfoster.net>> a Ã©crit : > 14r1.2e1 "16.0" > 15r1.2e1 â1.195851851851852" > > Does it make sense to have exponents for numbers that are not base 10? There are tests that have large exponents for binary numbers and we are not sure how to handle this in GemStone. > > James >

Sept. 5, 2019

Re: [Pharo-dev] [Pharo-users] [ANN] Pharo Headless - Beta (Actually what is between Alpha and Beta)

by Ben Coman

On Mon, 12 Aug 2019 at 17:59, tesonep(a)gmail.com <tesonep(a)gmail.com> wrote: > Hi, > the repos is https://github.com/pharo-project/opensmalltalk-vm in > the headless branch > btw, to go directly to that branch... https://github.com/pharo-project/opensmalltalk-vm/tree/headless I'm really glad to see smalltalksrc on github for its accessibility. The concern then is synchronization with the original Monticello repo. Could a branch "headless-tracking-vmmaker" be created as a pure-mirror updated by a daily CI job so Github Compare View can be used to easily see differences ( https://github.blog/2010-03-01-introducing-github-compare-view/) This would make it easier for anyone to experiment locally merging in vmmaker updates without needing access to the particular conversion-tool being used. That is, it would fan out better to potential contributors. It might be useful to similarly have an independent "headless-tracking-extracted". How is the extraction currently being done? Is it a script being run adhoc by particular people or is it run by a CI job? Again it would fan out better to potential contributors to not need access to the extraction script. cheers -ben

Sept. 5, 2019

Re: [Pharo-dev] Floating-point numbers with radix (non-decimal)?

by Nicolas Cellier

Once upon a time, only uppercase letters were accpeted as extra digits (in base > 10) for both int and float Then 15r1.2E1 was not 15r1.2e1, the later being = 15r12.E Then it was considered better to understand hexadecimal numbers with lowercase too... and alternate-base Float became ambiguous and were never fixed :( This would deserve a new syntax, I don't know what makes sense, 15r1.2_e1 15r1.2#e1 ... Changing Smalltalk syntax is among the most difficult decisions, expect outcry ;) Maybe because it's too easy :) Le jeu. 5 sept. 2019 Ã 00:04, James Foster <Smalltalk(a)jgfoster.net> a Ã©crit : > 14r1.2e1 "16.0" > 15r1.2e1 â1.195851851851852" > > Does it make sense to have exponents for numbers that are not base 10? > There are tests that have large exponents for binary numbers and we are not > sure how to handle this in GemStone. > > James > >

Sept. 4, 2019

Floating-point numbers with radix (non-decimal)?

by James Foster

14r1.2e1 "16.0" 15r1.2e1 â1.195851851851852" Does it make sense to have exponents for numbers that are not base 10? There are tests that have large exponents for binary numbers and we are not sure how to handle this in GemStone. James

Sept. 4, 2019

Re: [Pharo-dev] [Pharo-users] Pharo Branding Organization on GitHub

by ducasse

thanks for the initiative. I think that we have more material around, like alternate logo. It would be nice to collect also the svg versions? I know that lusy did also design for mugs. > On 4 Sep 2019, at 17:25, Torsten Bergmann <astares(a)gmx.de> wrote: > > 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

Re: [Pharo-dev] humanReadablePrintString

by Hilaire

https://github.com/pharo-project/pharo/issues/4497 Le 04/09/2019 Ã 15:57, Sven Van Caekenberghe a Ã©critÂ : > Yes, probably. -- Dr. Geo http://drgeo.eu

Sept. 4, 2019

[Pharo 8.0] Build #698: Improving performance of athens

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

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…

Sept. 4, 2019