- Pharo-dev - lists.pharo.org

[Pharo 9.0] Build #31: 5601-Enhance-support-of-pipewildcard-notation-for-searching-in-DrTests-lists
by ci-pharo-ci-jenkins2＠inria.fr Jan. 31, 2020

Jan. 31, 2020

There is a new Pharo build available! The status of the build #31 was: SUCCESS. The Pull Request #5602 was integrated: "5601-Enhance-support-of-pipewildcard-notation-for-searching-in-DrTests-lists" Pull request url: https://github.com/pharo-project/pharo/pull/5602 Issue Url: https://github.com/pharo-project/pharo/issues/5601 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 9.0] Build #30: [improvement] now returns a selfNode directly rather than wait for thâ¦
by ci-pharo-ci-jenkins2＠inria.fr Jan. 31, 2020

Jan. 31, 2020

There is a new Pharo build available! The status of the build #30 was: SUCCESS. The Pull Request #5460 was integrated: "[improvement] now returns a selfNode directly rather than wait for thâ¦" Pull request url: https://github.com/pharo-project/pharo/pull/5460 Issue Url: https://github.com/pharo-project/pharo/issues/fixMethodAST Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Re: [Pharo-dev] Pharo4pharo mailing-list announce
by ducasse Jan. 30, 2020

Jan. 30, 2020

You see this is several times that I gently ask if we can move on. And regularly we get the same. So I can also live pharo-dev. At the end of the day we cannot have the cake and eat it too. So you can consider that Iâm an asshole. Iâm probably that. Now Iâm super super fedup to have to jump over some thread. I quit newsgroups in the past because of that. I quit Pharo-users because of that. When I want to read about X Z Y and this is not related to Pharo then I google the Web. S. > On 30 Jan 2020, at 12:05, Benoit St-Jean <bstjean(a)yahoo.com> wrote: > > > From: Benoit St-Jean <bstjean(a)yahoo.com> > Subject: Re: [Pharo-dev] Pharo4pharo mailing-list announce > Date: 30 January 2020 at 12:05:38 CET > To: pharo-dev(a)lists.pharo.org > > > Wow! > > That post on Pharo Weekly ( https://pharoweekly.wordpress.com/2020/01/30/ann-pharo-4-pharo-mailing-list/ <https://pharoweekly.wordpress.com/2020/01/30/ann-pharo-4-pharo-mailing-list/> ) really sets a great welcoming ambiance for any newcomer interested by Pharo who'll read that or who'll stumble on it by accident while googling "Pharo+mailing+list" ! > > #Not #Fail #WorstAdvertisingEver > > Please, take 30 seconds to remove that crap before too many people read it... > > P.S. it's one thing to express yourself like that on a mailing list, it's another one to put it upfront on a blog... > > On 2020-01-30 02:33, StÃ©phane Ducasse wrote: >> Hi >> >> Tired of boring and dull discussions about the past? >> Tired and bored about the fact that the discussions are not about Pharo but about X, Z, K? >> Want to get in touch with other real pharo users? >> Want to have positive and nice discussions about Pharo? >> >> This mailing-list is for you >> >> https://lists.gforge.inria.fr/mailman/listinfo/lse-pharo4pharo <https://lists.gforge.inria.fr/mailman/listinfo/lse-pharo4pharo> >> >> I created a new mailing-list for Pharo 4 Pharo. >> The idea of this new mailing-list is to exchange between Pharo users on Pharo. >> >> If you want to talk about the weather and other cool fishing practices or how other languages are super cool, >> then you should use another mailing-list. >> >> You can consider that Iâm >> [ ] an asshole >> [ ] an arrogant idiot >> [ ] other >> This is not my concern. >> >> My concern is: can we respect Pharo and users of Pharo that want to share what they are doing >> and ask questions about their language? >> >> If you join this mailing-list be warned that I (yes me the benevolent dictator of Pharo) will remove you from the mailing-list >> when you get on my nerves. >> >> If you do not like it, do not like me, do not appreciate it, do not join! >> >> S. >> >> BTW they are plenty of newsgroups about Smalltalk and you can join there. >> >> >> -------------------------------------------- >> StÃ©phane Ducasse >> http://stephane.ducasse.free.fr <http://stephane.ducasse.free.fr/> / http://www.pharo.org <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 >> > -- > ----------------- > BenoÃ®t St-Jean > Yahoo! Messenger: bstjean > Twitter: @BenLeChialeux > Pinterest: benoitstjean > Instagram: Chef_Benito > IRC: lamneth > GitHub: bstjean > Blogue: endormitoire.wordpress.com > "A standpoint is an intellectual horizon of radius zero". (A. Einstein) > >

2 2

Pharo4pharo mailing-list announce
by StÃ©phane Ducasse Jan. 30, 2020

Jan. 30, 2020

Hi Tired of boring and dull discussions about the past? Tired and bored about the fact that the discussions are not about Pharo but about X, Z, K? Want to get in touch with other real pharo users? Want to have positive and nice discussions about Pharo? This mailing-list is for you https://lists.gforge.inria.fr/mailman/listinfo/lse-pharo4pharo I created a new mailing-list for Pharo 4 Pharo. The idea of this new mailing-list is to exchange between Pharo users on Pharo. If you want to talk about the weather and other cool fishing practices or how other languages are super cool, then you should use another mailing-list. You can consider that Iâm [ ] an asshole [ ] an arrogant idiot [ ] other This is not my concern. My concern is: can we respect Pharo and users of Pharo that want to share what they are doing and ask questions about their language? If you join this mailing-list be warned that I (yes me the benevolent dictator of Pharo) will remove you from the mailing-list when you get on my nerves. If you do not like it, do not like me, do not appreciate it, do not join! S. BTW they are plenty of newsgroups about Smalltalk and you can join there. -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr / 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

4 3

Re: [Pharo-dev] Pharo4pharo mailing-list announce
by Paul DeBruicker Jan. 30, 2020

Jan. 30, 2020

+1 Pharo Smalltalk Developers mailing list wrote > Wow! > > That post on Pharo Weekly ( > https://pharoweekly.wordpress.com/2020/01/30/ann-pharo-4-pharo-mailing-list/ > ) really sets a great welcoming ambiance for any newcomer interested by > Pharo who'll read that or who'll stumble on it by accident while > googling "Pharo+mailing+list" ! > > #Not #Fail #WorstAdvertisingEver > > Please, take 30 seconds to remove that crap before too many people read > it... > > P.S. it's one thing to express yourself like that on a mailing list, > it's another one to put it upfront on a blog... > > On 2020-01-30 02:33, StÃ©phane Ducasse wrote: >> Hi >> >> Tired of boring and dull discussions about the past? >> Tired and bored about the fact that the discussions are not about >> Pharo but about X, Z, K? >> Want to get in touch with other real pharo users? >> Want to have positive and nice discussions about Pharo? >> >> This mailing-list is for you >> >> https://lists.gforge.inria.fr/mailman/listinfo/lse-pharo4pharo >> >> I created a new mailing-list for Pharo 4 Pharo. >> The idea of this new mailing-list is to exchange between Pharo users >> on Pharo. >> >> If you want to talk about the weather and other cool fishing practices >> or how other languages are super cool, >> then you should use another mailing-list. >> >> You can consider that Iâm >> [ ]Â Â an asshole >> [ ] Â an arrogant idiot >> [ ] Â other >> This is not my concern. >> >> My concern is: can we respect Pharo and users of Pharo that want to >> share what they are doing >> and ask questions about their language? >> >> If you join this mailing-list be warned that I (yes me the benevolent >> dictator of Pharo) will remove you from the mailing-list >> when you get on my nerves. >> >> If you do not like it, do not like me, do not appreciate it, do not join! >> >> S. >> >> BTW they are plenty of newsgroups about Smalltalk and you can join there. >> >> >> -------------------------------------------- >> StÃ©phane Ducasse >> http://stephane.ducasse.free.fr / 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 >> > -- > ----------------- > BenoÃ®t St-Jean > Yahoo! Messenger: bstjean > Twitter: @BenLeChialeux > Pinterest: benoitstjean > Instagram: Chef_Benito > IRC: lamneth > GitHub: bstjean > Blogue: endormitoire.wordpress.com > "A standpoint is an intellectual horizon of radius zero". (A. Einstein) -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html

1 0

[Experiment] playing with https://colony.io/
by Marcus Denker Jan. 29, 2020

Jan. 29, 2020

Hi, I was looking a bit at âThe Colonyâ, this is a project that wants to use Etherum âto Organize and Incentivize Collaborators, Contributors, and Communitiesâ, as they put it. They now have a first working version (which does not yet implement the whole model as described in the original white paperâ¦ but nevertheless it seems an interesting first step): There is some info here: https://colony.io/product/dapp/ If someone is interested to play with this, I added a #colony channel on Discord. The people behind colony are very interested to get people to try it, so this means that we will maybe organise to have them do a remote walk through or something like hat for everyone who is interested. Marcus

1 0

[Pharo 9.0] Build #29: 5387-RBSimpleFormatter-contains-deadcode
by ci-pharo-ci-jenkins2＠inria.fr Jan. 29, 2020

Jan. 29, 2020

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

1 0

[Pharo 9.0] Build #28: 5364-CompletionEngine-and-Monticello-saving
by ci-pharo-ci-jenkins2＠inria.fr Jan. 28, 2020

Jan. 28, 2020

There is a new Pharo build available! The status of the build #28 was: SUCCESS. The Pull Request #5583 was integrated: "5364-CompletionEngine-and-Monticello-saving" Pull request url: https://github.com/pharo-project/pharo/pull/5583 Issue Url: https://github.com/pharo-project/pharo/issues/5364 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Jan. 28, 2020

Hello we have a two years engineer position to work with us on the Moose Platform. S. -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr / 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

1 0

[Mm10s] 2020-01-27
by Esteban Lorenzano Jan. 27, 2020

Jan. 27, 2020

### Last week * Release Pharo 8.0 * [UFFI] See a problem in TFFI + Gtk3 backend caused by a change made to allow String econdings. * [objcbridge] I made the bridge compatible with the latest version of TFFI * [spec2] prepare a status document (I will attach it to this mail) * [spec2] table/list/trees: default sort in string columns work. * [Spec2-doc] add good comments to SpApplication * [big images] review usages of SystemNavigation (and similars) in the image, looking to centralise its behaviour (so we can plan strategies). * [big images] I got a functional calypso that uses notebook instead tabmanager. Still a lot of bugs to fix to make it functional (but it looks promising). * [Morphic] I fixed some errors on SpNotebookMorph: is was not informing correctly the last page when a page changed event happened. * Some branch clean up on pharo site ### This week * Work on speed up of big images (finish migration to notebook morph, start looking improvements on senders/implementors) * Work on idle vm

1 1