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

Re: [Pharo-dev] MQTT Data Broker & Client in Smalltalk

by Sven Van Caekenberghe

> On 16 Apr 2019, at 08:10, ducasse <stepharo(a)netcourrier.com> wrote: > > Thanks John > > Great news. > Do you know how different it is from https://github.com/svenvc/mqtt. > I saw that Sven have some tests. I did not see if he has the server part. Yes, that is correct: what I once did was a new MQTT client, an MQTT broker is a server that manages the distribution of messages. > Stef > > > >> On 16 Apr 2019, at 04:00, John M McIntosh <johnmci(a)smalltalkconsulting.com> wrote: >> >> Today we are pushing out a MQTT V311 client and data broker we've written in pure smalltalk. It is based on Tim Rowledge's earlier work, but as far as I know the only data broker in smalltalk. >> >> https://github.com/LabWare/MQTT-broker >> >> .... >> John M. McIntosh. Corporate Smalltalk Consulting Ltd https://www.linkedin.com/in/smalltalk >> >> >

April 16, 2019

Re: [Pharo-dev] MQTT Data Broker & Client in Smalltalk

by ducasse

Thanks John Great news. Do you know how different it is from https://github.com/svenvc/mqtt <https://github.com/svenvc/mqtt>. I saw that Sven have some tests. I did not see if he has the server part. Stef > On 16 Apr 2019, at 04:00, John M McIntosh <johnmci(a)smalltalkconsulting.com> wrote: > > Today we are pushing out a MQTT V311 client and data broker we've written in pure smalltalk. It is based on Tim Rowledge's earlier work, but as far as I know the only data broker in smalltalk. > > https://github.com/LabWare/MQTT-broker <https://github.com/LabWare/MQTT-broker> > > .... > John M. McIntosh. Corporate Smalltalk Consulting Ltd https://www.linkedin.com/in/smalltalk <https://www.linkedin.com/in/smalltalk> > >

April 16, 2019

MQTT Data Broker & Client in Smalltalk

by John M McIntosh

Today we are pushing out a MQTT V311 client and data broker we've written in pure smalltalk. It is based on Tim Rowledge's earlier work, but as far as I know the only data broker in smalltalk. https://github.com/LabWare/MQTT-broker .... John M. McIntosh. Corporate Smalltalk Consulting Ltd https://www.linkedin.com/in/smalltalk

April 16, 2019

Re: [Pharo-dev] ZnMimePart

by Sven Van Caekenberghe

Hi Alistair, Sorry that it took a while to answer, but I did not forget. > On 17 Mar 2019, at 07:55, Alistair Grant <akgrant0710(a)gmail.com> wrote: > > Hi Sven, > > I'm trying to parse maildir emails using ZnMimePart Cool. > and have a few questions: > > 1. The standard indicates that text lines should be terminated with > CRLF, however in practice many maildir format emails (as saved by > offlineimap and successfully handled by mutt) use LF. > > Are you open to modifying the parser to be a bit more forgiving, and > allow CRLF, LF or CR? > > I could then completely deprecate MIMEDocument from the image and make > MailMessage a bit more useful. Yes, being more forgiving about line end conventions would not hurt, it is more or less standard practice in Pharo. Just make sure you don't break anything else. > 2. ZnStringEntity and ZnByteArrayEntity both appear to answer their > contents without decoding the data based on the > Content-Transfer-Encoding, e.g. if I have: > > Date: Sat, 16 Mar 2019 12:00:21 +0100 > MIME-Version: 1.0 > Content-Type: image/jpeg; name="00585-capture.jpg" > Content-Transfer-Encoding: base64 > Content-Disposition: inline; filename="00585-capture.jpg" > > base64dataincludedhere... > > and send: > > aZmMimePart contents > > I'll get back the the result of evaluating: > > 'base64dataincludedhere...' asByteArray > > instead of the decoded data. > > Is this intended? I'd expect the decoded data (with charset decoding as > well, in the case of text). I am not sure I fully understand: both ZnStringEntity>>#contents and ZnByteArrayEntity>>#contents clearly return the internal string or bytes, so the fully decoded data. A ZnMimePart considers its entity to be its contents. The handling of transfer headers is currently located outside these objects, ZnEntityReader and ZnEntityWriter, as far as I remember. This feels correct. > 3. What do you think of adding a few convenience test methods, e.g. > isImage, isApplication, isText, etc.? That would be OK I guess. An alternative would be to add them to ZnMimeType, then more clients could use them (as far as they are universal enough). > Thanks, > Alistair Sven

April 15, 2019

[Pharo 8.0] Build #225: useCalypso0162

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

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

April 15, 2019

[Pharo 8.0] Build #224: 3112-openInEnvironment-does-not-seem-to-exist-anymore-but-it-is-sent

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

There is a new Pharo build available! The status of the build #224 was: FAILURE. The Pull Request #3137 was integrated: "3112-openInEnvironment-does-not-seem-to-exist-anymore-but-it-is-sent" Pull request url: https://github.com/pharo-project/pharo/pull/3137 Issue Url: https://github.com/pharo-project/pharo/issues/3112 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

April 15, 2019

Re: [Pharo-dev] [ANN] Pharo 7.0.3

by Tim Mackinnon

No problem - itâs a bit early to tell if itâs the same as before - my sense is that itâs slightly improved. I had that 7.0.3 image in light use for 3-4 hours before I noticed it. In 7.0.2 it would happen within 5-20 mins. I deliberately loaded Mirage as I recalled it was the catalyst before, and I think this might still be the case - but Iâll continue to use this setup to give more details. Do we re-open the previous issue and our feedback there? Tim Sent from my iPhone > On 15 Apr 2019, at 08:14, "tesonep(a)gmail.com" <tesonep(a)gmail.com> wrote: > > I am afraid we will need to give more love to it. > We need a proper solution, hacking it is not working. We will have to refactor implementation and modify the users. > It is not that we are lazy (that we are) but also it is ugly and full of magic numbers. > > But we will win, we must win! > > Thanks again for the report! > >> On Mon, Apr 15, 2019 at 9:10 AM tesonep(a)gmail.com <tesonep(a)gmail.com> wrote: >> Thanks a lot, founding the issue is important. >> For sure I missed some other users of freetype doing the same!! >> >>> On Mon, Apr 15, 2019 at 1:14 AM Tim Mackinnon <tim(a)testit.works> wrote: >>> I hate to be the bearer of bad news - but 7.0.3 on OSX still has the font glyph issue (see how my menus have started to go) - saving my image has fixed it (for now). I do have Mirage loaded in my image ( the latest version, and I was showing you guys how that seems to stress it a bit more). >>> >>> Tim >>> >>> <PastedGraphic-8.png> >>> >>> >>> >>> >>>> On 14 Apr 2019, at 15:16, tesonep(a)gmail.com wrote: >>>> >>>> Like in the Oscars, I was thanking everybody. ;) >>>> >>>> On Fri, 12 Apr 2019, 21:40 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr wrote: >>>>> what is the academy? >>>>> :) >>>>> >>>>> stef >>>>> >>>>> >>>>> >>>>>> On 12 Apr 2019, at 17:26, tesonep(a)gmail.com wrote: >>>>>> >>>>>> Pharo 7.0.3 contains several bugfixes, notably a fix for the annoying font corruption font. >>>>>> >>>>>> <image.png> >>>>>> >>>>>> Changes Log >>>>>> >>>>>> #2781 Fix comment on OSWindow >> startTextInput >>>>>> #3160 2975-Problem-when-you-read-an-mcz-pharo7 >>>>>> #3130 Improving the performance of SourceFileArray >>>>>> #3164 MailMessage can not send mails with attachment in Pharo7 >>>>>> #3149 3148-backport-2395-to-Pharo-70--Non-ASCII-class-and-author-names-break-SourceFileArraygetPreambleFromat >>>>>> #3178 Fix for corrupted fonts in Pharo7 >>>>>> Detailed Diff: v7.0.2...pharo-project:v7.0.3 >>>>>> https://github.com/pharo-project/pharo/releases/tag/v7.0.3 >>>>>> >>>>>> All the images are available in ZeroConf and in the Pharo Launcher. >>>>>> >>>>>> Thanks to all the collaborators especially: >>>>>> >>>>>> - David >>>>>> - Guille >>>>>> - Pavel >>>>>> - Christophe >>>>>> - Theo >>>>>> - Sabine >>>>>> - Sven >>>>>> >>>>>> And to all the people that helped to make this release in a couple of minutes. >>>>>> And thanks to the academy! >>>>>> >>>>>> Pablo >>>>> >>>>> -------------------------------------------- >>>>> 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 >>>>> >>> >> >> >> -- >> Pablo Tesone. >> tesonep(a)gmail.com > > > -- > Pablo Tesone. > tesonep(a)gmail.com

April 15, 2019

Re: [Pharo-dev] [ANN] Pharo 7.0.3

by tesonep＠gmail.com

I am afraid we will need to give more love to it. We need a proper solution, hacking it is not working. We will have to refactor implementation and modify the users. It is not that we are lazy (that we are) but also it is ugly and full of magic numbers. But we will win, we must win! Thanks again for the report! On Mon, Apr 15, 2019 at 9:10 AM tesonep(a)gmail.com <tesonep(a)gmail.com> wrote: > Thanks a lot, founding the issue is important. > For sure I missed some other users of freetype doing the same!! > > On Mon, Apr 15, 2019 at 1:14 AM Tim Mackinnon <tim(a)testit.works> wrote: > >> I hate to be the bearer of bad news - but 7.0.3 on OSX still has the font >> glyph issue (see how my menus have started to go) - saving my image has >> fixed it (for now). I do have Mirage loaded in my image ( the latest >> version, and I was showing you guys how that seems to stress it a bit more). >> >> Tim >> >> >> >> >> >> On 14 Apr 2019, at 15:16, tesonep(a)gmail.com wrote: >> >> Like in the Oscars, I was thanking everybody. ;) >> >> On Fri, 12 Apr 2019, 21:40 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr >> wrote: >> >>> what is the academy? >>> :) >>> >>> stef >>> >>> >>> >>> On 12 Apr 2019, at 17:26, tesonep(a)gmail.com wrote: >>> >>> Pharo 7.0.3 contains several bugfixes, notably a fix for the annoying >>> font corruption font. >>> >>> <image.png> >>> >>> Changes Log >>> >>> >>> - #2781 <https://github.com/pharo-project/pharo/pull/2781> Fix >>> comment on OSWindow >> startTextInput >>> - #3160 <https://github.com/pharo-project/pharo/pull/3160> >>> 2975-Problem-when-you-read-an-mcz-pharo7 >>> - #3130 <https://github.com/pharo-project/pharo/pull/3130> Improving >>> the performance of SourceFileArray >>> - #3164 <https://github.com/pharo-project/pharo/pull/3164> MailMessage >>> can not send mails with attachment in Pharo7 >>> - #3149 <https://github.com/pharo-project/pharo/pull/3149> >>> 3148-backport-2395-to-Pharo-70--Non-ASCII-class-and-author-names-break-SourceFileArraygetPreambleFromat >>> - #3178 <https://github.com/pharo-project/pharo/pull/3178> Fix for >>> corrupted fonts in Pharo7 >>> >>> Detailed Diff: v7.0.2...pharo-project:v7.0.3 >>> <https://github.com/pharo-project/pharo/compare/v7.0.2...pharo-project:v7.0.3> >>> https://github.com/pharo-project/pharo/releases/tag/v7.0.3 >>> >>> All the images are available in ZeroConf and in the Pharo Launcher. >>> >>> Thanks to all the collaborators especially: >>> >>> - David >>> - Guille >>> - Pavel >>> - Christophe >>> - Theo >>> - Sabine >>> - Sven >>> >>> And to all the people that helped to make this release in a couple of >>> minutes. >>> And thanks to the academy! >>> >>> Pablo >>> >>> >>> -------------------------------------------- >>> 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 >>> >>> >> > > -- > Pablo Tesone. > tesonep(a)gmail.com > -- Pablo Tesone. tesonep(a)gmail.com

April 15, 2019

Re: [Pharo-dev] [ANN] Pharo 7.0.3

by tesonep＠gmail.com

Thanks a lot, founding the issue is important. For sure I missed some other users of freetype doing the same!! On Mon, Apr 15, 2019 at 1:14 AM Tim Mackinnon <tim(a)testit.works> wrote: > I hate to be the bearer of bad news - but 7.0.3 on OSX still has the font > glyph issue (see how my menus have started to go) - saving my image has > fixed it (for now). I do have Mirage loaded in my image ( the latest > version, and I was showing you guys how that seems to stress it a bit more). > > Tim > > > > > > On 14 Apr 2019, at 15:16, tesonep(a)gmail.com wrote: > > Like in the Oscars, I was thanking everybody. ;) > > On Fri, 12 Apr 2019, 21:40 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > >> what is the academy? >> :) >> >> stef >> >> >> >> On 12 Apr 2019, at 17:26, tesonep(a)gmail.com wrote: >> >> Pharo 7.0.3 contains several bugfixes, notably a fix for the annoying >> font corruption font. >> >> <image.png> >> >> Changes Log >> >> >> - #2781 <https://github.com/pharo-project/pharo/pull/2781> Fix >> comment on OSWindow >> startTextInput >> - #3160 <https://github.com/pharo-project/pharo/pull/3160> >> 2975-Problem-when-you-read-an-mcz-pharo7 >> - #3130 <https://github.com/pharo-project/pharo/pull/3130> Improving >> the performance of SourceFileArray >> - #3164 <https://github.com/pharo-project/pharo/pull/3164> MailMessage >> can not send mails with attachment in Pharo7 >> - #3149 <https://github.com/pharo-project/pharo/pull/3149> >> 3148-backport-2395-to-Pharo-70--Non-ASCII-class-and-author-names-break-SourceFileArraygetPreambleFromat >> - #3178 <https://github.com/pharo-project/pharo/pull/3178> Fix for >> corrupted fonts in Pharo7 >> >> Detailed Diff: v7.0.2...pharo-project:v7.0.3 >> <https://github.com/pharo-project/pharo/compare/v7.0.2...pharo-project:v7.0.3> >> https://github.com/pharo-project/pharo/releases/tag/v7.0.3 >> >> All the images are available in ZeroConf and in the Pharo Launcher. >> >> Thanks to all the collaborators especially: >> >> - David >> - Guille >> - Pavel >> - Christophe >> - Theo >> - Sabine >> - Sven >> >> And to all the people that helped to make this release in a couple of >> minutes. >> And thanks to the academy! >> >> Pablo >> >> >> -------------------------------------------- >> 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 >> >> > -- Pablo Tesone. tesonep(a)gmail.com

April 15, 2019

Re: [Pharo-dev] [ANN] Pharo 7.0.3

by Tim Mackinnon

I hate to be the bearer of bad news - but 7.0.3 on OSX still has the font glyph issue (see how my menus have started to go) - saving my image has fixed it (for now). I do have Mirage loaded in my image ( the latest version, and I was showing you guys how that seems to stress it a bit more). Tim > On 14 Apr 2019, at 15:16, tesonep(a)gmail.com wrote: > > Like in the Oscars, I was thanking everybody. ;) > > On Fri, 12 Apr 2019, 21:40 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr <mailto:stephane.ducasse@inria.fr> wrote: > what is the academy? > :) > > stef > > > >> On 12 Apr 2019, at 17:26, tesonep(a)gmail.com <mailto:tesonep@gmail.com> wrote: >> >> Pharo 7.0.3 contains several bugfixes, notably a fix for the annoying font corruption font. >> >> <image.png> >> >> Changes Log >> >> #2781 <https://github.com/pharo-project/pharo/pull/2781> Fix comment on OSWindow >> startTextInput >> #3160 <https://github.com/pharo-project/pharo/pull/3160> 2975-Problem-when-you-read-an-mcz-pharo7 >> #3130 <https://github.com/pharo-project/pharo/pull/3130> Improving the performance of SourceFileArray >> #3164 <https://github.com/pharo-project/pharo/pull/3164> MailMessage can not send mails with attachment in Pharo7 >> #3149 <https://github.com/pharo-project/pharo/pull/3149> 3148-backport-2395-to-Pharo-70--Non-ASCII-class-and-author-names-break-SourceFileArraygetPreambleFromat >> #3178 <https://github.com/pharo-project/pharo/pull/3178> Fix for corrupted fonts in Pharo7 >> Detailed Diff: v7.0.2...pharo-project:v7.0.3 <https://github.com/pharo-project/pharo/compare/v7.0.2...pharo-project:v7.0.3> >> https://github.com/pharo-project/pharo/releases/tag/v7.0.3 <https://github.com/pharo-project/pharo/releases/tag/v7.0.3> >> All the images are available in ZeroConf and in the Pharo Launcher. >> >> Thanks to all the collaborators especially: >> >> - David >> - Guille >> - Pavel >> - Christophe >> - Theo >> - Sabine >> - Sven >> >> And to all the people that helped to make this release in a couple of minutes. >> And thanks to the academy! >> >> Pablo > > -------------------------------------------- > StÃ©phane Ducasse > http://stephane.ducasse.free.fr <http://stephane.ducasse.free.fr/> > http://www.synectique.eu <http://www.synectique.eu/> / 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 >

April 14, 2019

Re: [Pharo-dev] [ANN] Pharo 7.0.3

by tesonep＠gmail.com

Like in the Oscars, I was thanking everybody. ;) On Fri, 12 Apr 2019, 21:40 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr wrote: > what is the academy? > :) > > stef > > > > On 12 Apr 2019, at 17:26, tesonep(a)gmail.com wrote: > > Pharo 7.0.3 contains several bugfixes, notably a fix for the annoying font > corruption font. > > <image.png> > > Changes Log > > > - #2781 <https://github.com/pharo-project/pharo/pull/2781> Fix comment > on OSWindow >> startTextInput > - #3160 <https://github.com/pharo-project/pharo/pull/3160> > 2975-Problem-when-you-read-an-mcz-pharo7 > - #3130 <https://github.com/pharo-project/pharo/pull/3130> Improving > the performance of SourceFileArray > - #3164 <https://github.com/pharo-project/pharo/pull/3164> MailMessage > can not send mails with attachment in Pharo7 > - #3149 <https://github.com/pharo-project/pharo/pull/3149> > 3148-backport-2395-to-Pharo-70--Non-ASCII-class-and-author-names-break-SourceFileArraygetPreambleFromat > - #3178 <https://github.com/pharo-project/pharo/pull/3178> Fix for > corrupted fonts in Pharo7 > > Detailed Diff: v7.0.2...pharo-project:v7.0.3 > <https://github.com/pharo-project/pharo/compare/v7.0.2...pharo-project:v7.0.3> > https://github.com/pharo-project/pharo/releases/tag/v7.0.3 > > All the images are available in ZeroConf and in the Pharo Launcher. > > Thanks to all the collaborators especially: > > - David > - Guille > - Pavel > - Christophe > - Theo > - Sabine > - Sven > > And to all the people that helped to make this release in a couple of > minutes. > And thanks to the academy! > > Pablo > > > -------------------------------------------- > 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 > >

April 14, 2019

Re: [Pharo-dev] [ANN] Pharo 7.0.3

by Norbert Hartl

> Am 14.04.2019 um 07:49 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: > > Hi Tim, > > Is not about subprojects, is about hot fixes :) > Pharo 7 will continue having some updates on critical bugs but it should not include regular changes (like an update on Calypso). > In that sense, fix #2781 sneaked in and it shouldnât, which means we still need to adjust the process :P > The last sentence made me very lucky.ð Norbert > Esteban > > >> On 13 Apr 2019, at 14:50, Tim Mackinnon <tim(a)testit.works> wrote: >> >> This is great - Iâm pleased we can get fixes like this (and keen to get passed that font issue which was driving me crazy). >> >> A small related question - how do ensure we get fixes from sub projects considered too? Iâd really like to see: https://github.com/pharo-ide/Calypso/pull/451 as itâs annoying not being able to move methods between classes. There are a few other Calypso gems in there too (and quite a few more to fix). >> >> I worry that having all these sub-projects makes it a bit complicated to get them included? >> >> Tim >> >> Sent from my iPhone >> >>> On 12 Apr 2019, at 16:26, "tesonep(a)gmail.com" <tesonep(a)gmail.com> wrote: >>> >>> Pharo 7.0.3 contains several bugfixes, notably a fix for the annoying font corruption font. >>> >>> <image.png> >>> >>> Changes Log >>> >>> #2781 Fix comment on OSWindow >> startTextInput >>> #3160 2975-Problem-when-you-read-an-mcz-pharo7 >>> #3130 Improving the performance of SourceFileArray >>> #3164 MailMessage can not send mails with attachment in Pharo7 >>> #3149 3148-backport-2395-to-Pharo-70--Non-ASCII-class-and-author-names-break-SourceFileArraygetPreambleFromat >>> #3178 Fix for corrupted fonts in Pharo7 >>> Detailed Diff: v7.0.2...pharo-project:v7.0.3 >>> https://github.com/pharo-project/pharo/releases/tag/v7.0.3 >>> >>> All the images are available in ZeroConf and in the Pharo Launcher. >>> >>> Thanks to all the collaborators especially: >>> >>> - David >>> - Guille >>> - Pavel >>> - Christophe >>> - Theo >>> - Sabine >>> - Sven >>> >>> And to all the people that helped to make this release in a couple of minutes. >>> And thanks to the academy! >>> >>> Pablo >

April 14, 2019

Re: [Pharo-dev] [ANN] Pharo 7.0.3

by Esteban Lorenzano

Hi Tim, Is not about subprojects, is about hot fixes :) Pharo 7 will continue having some updates on critical bugs but it should not include regular changes (like an update on Calypso). In that sense, fix #2781 sneaked in and it shouldnât, which means we still need to adjust the process :P Esteban > On 13 Apr 2019, at 14:50, Tim Mackinnon <tim(a)testit.works> wrote: > > This is great - Iâm pleased we can get fixes like this (and keen to get passed that font issue which was driving me crazy). > > A small related question - how do ensure we get fixes from sub projects considered too? Iâd really like to see: https://github.com/pharo-ide/Calypso/pull/451 <https://github.com/pharo-ide/Calypso/pull/451> as itâs annoying not being able to move methods between classes. There are a few other Calypso gems in there too (and quite a few more to fix). > > I worry that having all these sub-projects makes it a bit complicated to get them included? > > Tim > > Sent from my iPhone > > On 12 Apr 2019, at 16:26, "tesonep(a)gmail.com <mailto:tesonep@gmail.com>" <tesonep(a)gmail.com <mailto:tesonep@gmail.com>> wrote: > >> Pharo 7.0.3 contains several bugfixes, notably a fix for the annoying font corruption font. >> >> <image.png> >> >> Changes Log >> >> #2781 <https://github.com/pharo-project/pharo/pull/2781> Fix comment on OSWindow >> startTextInput >> #3160 <https://github.com/pharo-project/pharo/pull/3160> 2975-Problem-when-you-read-an-mcz-pharo7 >> #3130 <https://github.com/pharo-project/pharo/pull/3130> Improving the performance of SourceFileArray >> #3164 <https://github.com/pharo-project/pharo/pull/3164> MailMessage can not send mails with attachment in Pharo7 >> #3149 <https://github.com/pharo-project/pharo/pull/3149> 3148-backport-2395-to-Pharo-70--Non-ASCII-class-and-author-names-break-SourceFileArraygetPreambleFromat >> #3178 <https://github.com/pharo-project/pharo/pull/3178> Fix for corrupted fonts in Pharo7 >> Detailed Diff: v7.0.2...pharo-project:v7.0.3 <https://github.com/pharo-project/pharo/compare/v7.0.2...pharo-project:v7.0.3> >> https://github.com/pharo-project/pharo/releases/tag/v7.0.3 <https://github.com/pharo-project/pharo/releases/tag/v7.0.3> >> All the images are available in ZeroConf and in the Pharo Launcher. >> >> Thanks to all the collaborators especially: >> >> - David >> - Guille >> - Pavel >> - Christophe >> - Theo >> - Sabine >> - Sven >> >> And to all the people that helped to make this release in a couple of minutes. >> And thanks to the academy! >> >> Pablo

April 14, 2019

Re: [Pharo-dev] [ANN] Pharo 7.0.3

by Tim Mackinnon

This is great - Iâm pleased we can get fixes like this (and keen to get passed that font issue which was driving me crazy). A small related question - how do ensure we get fixes from sub projects considered too? Iâd really like to see: https://github.com/pharo-ide/Calypso/pull/451 as itâs annoying not being able to move methods between classes. There are a few other Calypso gems in there too (and quite a few more to fix). I worry that having all these sub-projects makes it a bit complicated to get them included? Tim Sent from my iPhone > On 12 Apr 2019, at 16:26, "tesonep(a)gmail.com" <tesonep(a)gmail.com> wrote: > > Pharo 7.0.3 contains several bugfixes, notably a fix for the annoying font corruption font. > > <image.png> > > Changes Log > > #2781 Fix comment on OSWindow >> startTextInput > #3160 2975-Problem-when-you-read-an-mcz-pharo7 > #3130 Improving the performance of SourceFileArray > #3164 MailMessage can not send mails with attachment in Pharo7 > #3149 3148-backport-2395-to-Pharo-70--Non-ASCII-class-and-author-names-break-SourceFileArraygetPreambleFromat > #3178 Fix for corrupted fonts in Pharo7 > Detailed Diff: v7.0.2...pharo-project:v7.0.3 > https://github.com/pharo-project/pharo/releases/tag/v7.0.3 > > All the images are available in ZeroConf and in the Pharo Launcher. > > Thanks to all the collaborators especially: > > - David > - Guille > - Pavel > - Christophe > - Theo > - Sabine > - Sven > > And to all the people that helped to make this release in a couple of minutes. > And thanks to the academy! > > Pablo

April 13, 2019

Re: [Pharo-dev] [ANN] Pharo 7.0.3

by StÃ©phane Ducasse

what is the academy? :) stef > On 12 Apr 2019, at 17:26, tesonep(a)gmail.com wrote: > > Pharo 7.0.3 contains several bugfixes, notably a fix for the annoying font corruption font. > > <image.png> > > Changes Log > > #2781 <https://github.com/pharo-project/pharo/pull/2781> Fix comment on OSWindow >> startTextInput > #3160 <https://github.com/pharo-project/pharo/pull/3160> 2975-Problem-when-you-read-an-mcz-pharo7 > #3130 <https://github.com/pharo-project/pharo/pull/3130> Improving the performance of SourceFileArray > #3164 <https://github.com/pharo-project/pharo/pull/3164> MailMessage can not send mails with attachment in Pharo7 > #3149 <https://github.com/pharo-project/pharo/pull/3149> 3148-backport-2395-to-Pharo-70--Non-ASCII-class-and-author-names-break-SourceFileArraygetPreambleFromat > #3178 <https://github.com/pharo-project/pharo/pull/3178> Fix for corrupted fonts in Pharo7 > Detailed Diff: v7.0.2...pharo-project:v7.0.3 <https://github.com/pharo-project/pharo/compare/v7.0.2...pharo-project:v7.0.3> > https://github.com/pharo-project/pharo/releases/tag/v7.0.3 <https://github.com/pharo-project/pharo/releases/tag/v7.0.3> > All the images are available in ZeroConf and in the Pharo Launcher. > > Thanks to all the collaborators especially: > > - David > - Guille > - Pavel > - Christophe > - Theo > - Sabine > - Sven > > And to all the people that helped to make this release in a couple of minutes. > And thanks to the academy! > > Pablo -------------------------------------------- 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

April 12, 2019

[Pharo 8.0] Build #223: 3153-Slots-Cleanups--some-first-ComposableSlot-

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

There is a new Pharo build available! The status of the build #223 was: SUCCESS. The Pull Request #3154 was integrated: "3153-Slots-Cleanups--some-first-ComposableSlot-" Pull request url: https://github.com/pharo-project/pharo/pull/3154 Issue Url: https://github.com/pharo-project/pharo/issues/3153 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

April 12, 2019

Re: [vwnc] most energy efficient AI system - challenge of the German Federal Ministry of Education and Research BMBF

by Alexandre Bergel

Hello, We conducted some experiment in characterizing virtual machine from an energetic point of view. Results are not public yet. This is just to say this is a topic that I am interested in. Cheers, Alexandre > On Apr 11, 2019, at 5:29 PM, Bernhard HÃ¶fner <bernhard.hoefner(a)web.de> wrote: > > Hello Group, > the German BMBF advertised a reward for the most energy efficient AI system, see: https://www.bmbf.de/de/mehr-ki-erfordert-weniger-energie-8156.html <https://www.bmbf.de/de/mehr-ki-erfordert-weniger-energie-8156.html> (in German), and I am wondering what is the position of Smalltalk in that field or what it could be. From the early 90th I know that much of the pretended slowness of Smalltalk was absorbed by the more efficient programs due to better analysis, concepts, design and development tools (and maybe developers ? ). > > Best Regards, Bernhard

April 12, 2019

[ANN] Pharo 7.0.3

by tesonep＠gmail.com

Pharo 7.0.3 contains several bugfixes, notably a fix for the annoying font corruption font. [image: image.png] Changes Log - #2781 <https://github.com/pharo-project/pharo/pull/2781> Fix comment on OSWindow >> startTextInput - #3160 <https://github.com/pharo-project/pharo/pull/3160> 2975-Problem-when-you-read-an-mcz-pharo7 - #3130 <https://github.com/pharo-project/pharo/pull/3130> Improving the performance of SourceFileArray - #3164 <https://github.com/pharo-project/pharo/pull/3164> MailMessage can not send mails with attachment in Pharo7 - #3149 <https://github.com/pharo-project/pharo/pull/3149> 3148-backport-2395-to-Pharo-70--Non-ASCII-class-and-author-names-break-SourceFileArraygetPreambleFromat - #3178 <https://github.com/pharo-project/pharo/pull/3178> Fix for corrupted fonts in Pharo7 Detailed Diff: v7.0.2...pharo-project:v7.0.3 <https://github.com/pharo-project/pharo/compare/v7.0.2...pharo-project:v7.0.3> https://github.com/pharo-project/pharo/releases/tag/v7.0.3 All the images are available in ZeroConf and in the Pharo Launcher. Thanks to all the collaborators especially: - David - Guille - Pavel - Christophe - Theo - Sabine - Sven And to all the people that helped to make this release in a couple of minutes. And thanks to the academy! Pablo

April 12, 2019

[Pharo 7.0] Build #158: Fix for corrupted fonts in Pharo7

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

There is a new Pharo build available! The status of the build #158 was: SUCCESS. The Pull Request #3178 was integrated: "Fix for corrupted fonts in Pharo7" Pull request url: https://github.com/pharo-project/pharo/pull/3178 Issue Url: https://pharo.fogbugz.com/f/cases/3157 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

April 12, 2019

[Pharo 7.0] Build #157: Fix for corrupted fonts in Pharo7

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

There is a new Pharo build available! The status of the build #157 was: FAILURE. The Pull Request #3178 was integrated: "Fix for corrupted fonts in Pharo7" Pull request url: https://github.com/pharo-project/pharo/pull/3178 Issue Url: https://pharo.fogbugz.com/f/cases/3157 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

April 12, 2019

[Pharo 8.0] Build #222: Adding flags for Smalltalk reference. Refactor some direct reference â¦

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

There is a new Pharo build available! The status of the build #222 was: FAILURE. The Pull Request #3155 was integrated: "Adding flags for Smalltalk reference. Refactor some direct reference â¦" Pull request url: https://github.com/pharo-project/pharo/pull/3155 Issue Url: https://github.com/pharo-project/pharo/issues/FewSmalltalkRemoval Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

April 12, 2019

[Pharo 8.0] Build #221: MailMessage can not send mails with attachment in Pharo8

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

There is a new Pharo build available! The status of the build #221 was: SUCCESS. The Pull Request #3167 was integrated: "MailMessage can not send mails with attachment in Pharo8" Pull request url: https://github.com/pharo-project/pharo/pull/3167 Issue Url: https://github.com/pharo-project/pharo/issues/3164 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

April 12, 2019

Re: [Pharo-dev] [Pharo-users] [OT] (slightly) What makes other dialects "enjoyable" for you? (WAS: difference between double dispatch...)

by Sven Van Caekenberghe

I agree with Norbert: the problem lies in the definition of LTS. Right now, Pharo 8 is the moving thing, Pharo 7 is stable and receives back ports of selected fixes. Each older Pharo version is also stable: what worked years ago, still works today. I have many Pharo 4 images running in production, they even get new application code that was developed in Pharo 7 images. LTS is also a bit of a trap: Ubuntu has it for Linux, but after 5 or 10 years you still have to move, and then it will be quite hard because you never did any small steps. We had similar problems in the Java and Javascript worlds (to name two much larger communities): one day some critical part that you depend on becomes obsolete, and then you have a problem. > On 11 Apr 2019, at 23:34, Norbert Hartl <norbert(a)hartl.name> wrote: > > > > Am 11.04.2019 um 21:35 schrieb Mariano Martinez Peck <marianopeck(a)gmail.com>: > >> >> >> On Thu, Apr 11, 2019 at 10:54 AM Norbert Hartl <norbert(a)hartl.name> wrote: >> >> >> Am 11.04.2019 um 15:29 schrieb Mariano Martinez Peck <marianopeck(a)gmail.com>: >> >>> Hi Esteban, >>> >>> We talk this privately a couple of weeks ago, but I thought it was worth writing again here. As for other IDE's being enjoyable, I can only talk about VASmalltalk. If there is ONE thing I enjoy from it, is the stability. May be ugly, may be too-windows, may be full of menus you don't understand what they do, but it's really rock solid. >>> Pharo has been doing a LOT of progress on so many areas and its expected to decrease a bit on stability. Unless you are Oracle and can hire 100 engineers. >>> So, my small recommendation to you back then was to make at least ONE release (called LTS or whatever) were you just focus on stability and bugs. No new features. No new framework. Just stability. Make it rock solid. Then after that release, you can keep moving forward, but that would give companies and really really stable Pharo to rely on. >>> >> For the provision of an LTS version we need more engineers. If there are enough companies that need a rock solid stable version then the consortium will have enough money to hire engineers for that. >> >> Well, either that or convince the community that that is a good thing. Obviously, when you don't pay for that and things come for free it's understandable you can't decide on what type of effort/results you get. And for almost all of us, is much way more cool to provide a new framework, a new tool, etc than bug fixing and testing. >> > Yes and it is ok it is that way. Peope spend their time and want to do something fun not the boring part. There might be projects which developed a culture of providing that as a value. But a general rule for open source work is âEither it is fun or it needs to be paidâ. I cannot see anything wrong with that. And I if try to think about an LTS version that is not backed up by a company I cannot come up with one quickly. > And when we discuss this topic I want to have a clearer definition of terms. To me there are âstabilityâ and âstand-stillâ mixed in the readings. Pharo provides quite a good stability while its moving. And that is IMHO the only way it can work. > And yet there is a place for an LTS. But who uses the new version then? How can you ever move because people just using the âstagnatedâ version? > > Norbert >> >> I would put a virtual machine that we can control much higher on the list of things we should have. >> >> Norbert >> >>> Best, >>> >>> -- >>> Mariano Martinez Peck >>> Email: marianopeck(a)gmail.com >>> Twitter: @MartinezPeck >>> LinkedIn: https://www.linkedin.com/in/mariano-mart%C3%ADnez-peck/ >> >> >> -- >> Mariano Martinez Peck >> Email: marianopeck(a)gmail.com >> Twitter: @MartinezPeck >> LinkedIn: https://www.linkedin.com/in/mariano-mart%C3%ADnez-peck/

April 12, 2019

Re: [Pharo-dev] [Pharo-users] [OT] (slightly) What makes other dialects "enjoyable" for you? (WAS: difference between double dispatch...)

by ducasse

I think that everybody should read the innovator dilemna because large industry got just destroyed because they followed what their customers wanted. They customers said we want A and never B and suddenly B was cool enough and they did not want A anymore. Stef

April 12, 2019

Re: [Pharo-dev] [Pharo-users] [OT] (slightly) What makes other dialects "enjoyable" for you? (WAS: difference between double dispatch...)

by Norbert Hartl

> Am 11.04.2019 um 21:35 schrieb Mariano Martinez Peck <marianopeck(a)gmail.com>: > > > >> On Thu, Apr 11, 2019 at 10:54 AM Norbert Hartl <norbert(a)hartl.name> wrote: >> >> >>> Am 11.04.2019 um 15:29 schrieb Mariano Martinez Peck <marianopeck(a)gmail.com>: >>> >>> Hi Esteban, >>> >>> We talk this privately a couple of weeks ago, but I thought it was worth writing again here. As for other IDE's being enjoyable, I can only talk about VASmalltalk. If there is ONE thing I enjoy from it, is the stability. May be ugly, may be too-windows, may be full of menus you don't understand what they do, but it's really rock solid. >>> Pharo has been doing a LOT of progress on so many areas and its expected to decrease a bit on stability. Unless you are Oracle and can hire 100 engineers. >>> So, my small recommendation to you back then was to make at least ONE release (called LTS or whatever) were you just focus on stability and bugs. No new features. No new framework. Just stability. Make it rock solid. Then after that release, you can keep moving forward, but that would give companies and really really stable Pharo to rely on. >>> >> For the provision of an LTS version we need more engineers. If there are enough companies that need a rock solid stable version then the consortium will have enough money to hire engineers for that. > > Well, either that or convince the community that that is a good thing. Obviously, when you don't pay for that and things come for free it's understandable you can't decide on what type of effort/results you get. And for almost all of us, is much way more cool to provide a new framework, a new tool, etc than bug fixing and testing. > Yes and it is ok it is that way. Peope spend their time and want to do something fun not the boring part. There might be projects which developed a culture of providing that as a value. But a general rule for open source work is âEither it is fun or it needs to be paidâ. I cannot see anything wrong with that. And I if try to think about an LTS version that is not backed up by a company I cannot come up with one quickly. And when we discuss this topic I want to have a clearer definition of terms. To me there are âstabilityâ and âstand-stillâ mixed in the readings. Pharo provides quite a good stability while its moving. And that is IMHO the only way it can work. And yet there is a place for an LTS. But who uses the new version then? How can you ever move because people just using the âstagnatedâ version? Norbert > >> I would put a virtual machine that we can control much higher on the list of things we should have. >> >> Norbert >> >>> Best, >>> >>> -- >>> Mariano Martinez Peck >>> Email: marianopeck(a)gmail.com >>> Twitter: @MartinezPeck >>> LinkedIn: https://www.linkedin.com/in/mariano-mart%C3%ADnez-peck/ > > > -- > Mariano Martinez Peck > Email: marianopeck(a)gmail.com > Twitter: @MartinezPeck > LinkedIn: https://www.linkedin.com/in/mariano-mart%C3%ADnez-peck/

April 11, 2019