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

Re: [Pharo-dev] Roassal Animations

by Alexandre Bergel

Hi! Just as a follow up, we have a UML diagram builder for Roassal3. You can load Roassal3 using: Metacello new baseline: 'Roassal3'; repository: 'github://ObjectProfile/Roassal3/src'; load. As indicated on https://github.com/ObjectProfile/Roassal3 An UML class diagram can be open using: -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= | builder pharoClassesToBeVisualized | "Zooming and position of the view can be controled using the keys: I O Space Arrows " pharoClassesToBeVisualized := TSAbstractLine withAllSubclasses. builder := RSUMLClassBuilder new. builder classes: pharoClassesToBeVisualized. builder classDescriptor methods: [ :cls | | methods | methods := cls methods sorted: [ :a :b | a selector < b selector ] ]. builder build. builder view when: TSExtentChangedEvent do: [ builder view zoomToFit ]. builder open -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= We now do have a support for UML class diagrams and we can easily add new features, if wanted. Cheers, Alexandre & Milton > On Mar 27, 2019, at 3:37 PM, ducasse <stepharo(a)netcourrier.com> wrote: > > > >> On 27 Mar 2019, at 18:27, Alexandre Bergel <alexandre.bergel(a)me.com <mailto:alexandre.bergel@me.com>> wrote: >> >> >> From: Alexandre Bergel <alexandre.bergel(a)me.com <mailto:alexandre.bergel@me.com>> >> Subject: Re: [Pharo-dev] Roassal Animations >> Date: 27 March 2019 at 18:27:28 CET >> To: Pharo Development List <pharo-dev(a)lists.pharo.org <mailto:pharo-dev@lists.pharo.org>> >> >> >> Thanks to all of you for your nice words. >> These posts are a teaser of what is coming. Code of each animation is part of Roassal3. Note that we have made no official announcement, simply because Roassal3 is still well behind Roassal2 in terms of offered features. Actually, you cannot do much with Roassal3, beside having cool visualization. >> >> We will tell you more soon, once we have a UML renderer and code dependency visualizer :-) >> >> We are currently working on a nice distribution that can be shipped within Pharo 8. > > :) > >

April 17, 2019

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

by Denis Kudriashov

Hi Tim. ÑÐ±, 13 Ð°Ð¿Ñ. 2019 Ð³. Ð² 13:51, Tim Mackinnon <tim(a)testit.works>: > 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? > Nothing special here. As soon as these projects support old Pharo version it just requires another PR into Pharo 7 with new version of sub-project (modifying loadCalypso in that case). Somebody should just decide that new version needs to be to back ported. > > 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 <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 17, 2019

Handling of deprecation packages

by Torsten Bergmann

Hi, in the past after each release iteration one of the first things applied to a new development image - was to remove the "DeprecatedXX" package of the previous version XX - and add a new "DeprecatedYY" package for the new pharo version YY This allowed then to mark classes that should get obsolete for version YY and put them into "DeprecatedYY" But in current Pharo 8 dev image we still have the "Deprecated70" package inside and a new "Deprecated80" is not yet opened. I know there - were some discussion about having a "migrator" tool first to help in the transition to the new release (but I guess this "migrator" could be written using P7 image, no?) - we can also not just delete "Deprecated70" as StandardFileStream, MultiByteFileStream and others are still useds in the code without giving a proper So I wonder what is the status and on plan this in P8 Thx T.

April 17, 2019

[Pharo 8.0] Build #228: ClassParser: methods polymorphic to RB-nodes for Calypso integration

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

There is a new Pharo build available! The status of the build #228 was: SUCCESS. The Pull Request #3183 was integrated: "ClassParser: methods polymorphic to RB-nodes for Calypso integration" Pull request url: https://github.com/pharo-project/pharo/pull/3183 Issue Url: https://github.com/pharo-project/pharo/issues/classParserForCalypso Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

April 17, 2019

Re: [Pharo-dev] ZnMimePart

by Alistair Grant

Hi Sven, On Mon, 15 Apr 2019 at 16:17, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > Hi Alistair, > > Sorry that it took a while to answer, but I did not forget. No problem, I'm a bit behind myself. :-) > > 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. I ended up writing a wrapper around the stream that converted random line endings to CRLF. After thinking about it a bit further I actually prefer this approach at the moment. There's a few places in the standard where it is quite specific about how to interpret the various options. Having the wrapper stream isolates the non-standard functionality and allows it to be easily removed. > > 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. I'll have to get back to this. I'm side-tracked on other stuff at the moment, but thanks for your explanation. > > 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). Great. I'll get around to tidying up my modifications and submit them as a few PRs. P.S. I've successfully scanned about 35,000 emails. Thanks again, Alistair

April 16, 2019

[Pharo 8.0] Build #227: Make size_t work inside a nested structure

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

There is a new Pharo build available! The status of the build #227 was: SUCCESS. The Pull Request #3142 was integrated: "Make size_t work inside a nested structure" Pull request url: https://github.com/pharo-project/pharo/pull/3142 Issue Url: https://github.com/pharo-project/pharo/issues/ffi Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

April 16, 2019

[Pharo 8.0] Build #226: 3188-Some-classes-have-an-users-property

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

There is a new Pharo build available! The status of the build #226 was: SUCCESS. The Pull Request #3190 was integrated: "3188-Some-classes-have-an-users-property" Pull request url: https://github.com/pharo-project/pharo/pull/3190 Issue Url: https://github.com/pharo-project/pharo/issues/3188 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

April 16, 2019

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

by Tim Mackinnon

FYI - I was able to confirm that my working 703 image continues to show the issue (Exercism+Mirage seem to cause it - but I suspect itâs Mirage rendering thumbnails in multiple threads that stresses things). Guille has come up with a filein that has some more aggressive mutex code (from my quick glance), so I am running with that to see if I can empirically show it helps. Tim Sent from my iPhone > On 16 Apr 2019, at 08:30, ducasse <stepharo(a)netcourrier.com> wrote: > > Hi tim > > I think that this is better to create a new issue. > > Stef > > >> On 15 Apr 2019, at 09:57, Tim Mackinnon <tim(a)testit.works> wrote: >> >> 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> >>>>> >>>>> >>>>> <PastedGraphic-9.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 16, 2019

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

by ducasse

Hi tim I think that this is better to create a new issue. Stef > On 15 Apr 2019, at 09:57, Tim Mackinnon <tim(a)testit.works> wrote: > > 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 <mailto:tesonep@gmail.com>" <tesonep(a)gmail.com <mailto:tesonep@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 <mailto:tesonep@gmail.com> <tesonep(a)gmail.com <mailto:tesonep@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 <mailto:tim@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> >> >> >> <PastedGraphic-9.png> >> >>> On 14 Apr 2019, at 15:16, tesonep(a)gmail.com <mailto:tesonep@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 >>> >> >> >> >> -- >> Pablo Tesone. >> tesonep(a)gmail.com <mailto:tesonep@gmail.com> >> >> -- >> Pablo Tesone. >> tesonep(a)gmail.com <mailto:tesonep@gmail.com>

April 16, 2019

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

by ducasse

I like to see tests there :) Iâm trying to write tests for the sound package and this is an kind of strange exercise. Stef > On 16 Apr 2019, at 09:23, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > >> 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