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

[ANN] Pharo 7.0.3
by tesonep＠gmail.com April 19, 2019

April 19, 2019

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

8 16

Recent Pharo 6.1 OSX shows lots of "Error: unsupported compressor 8 on command line"
by Tim Mackinnon April 19, 2019

April 19, 2019

I noticed that recent Pharo 6.1 zero conf downloads show lots of these errors when you run the image in the terminal. Previous versions didnât do this - is this something to do with the latest vm upgrade? ./pharo-ui PagerDuty.image /BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.30.2/Common/ChunkCompression.cpp:50: Error: unsupported compressor 8 /BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.30.2/Libraries/CompressData/CompressData.c:353: Error: Unknown compression scheme encountered for file '/System/Library/CoreServices/CoreTypes.bundle/Contents/Resources/Exceptions.plist' /BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.30.2/Common/ChunkCompression.cpp:50: Error: unsupported compressor 8 /BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleFSCompression/AppleFSCompression-96.30.2/Libraries/CompressData/CompressData.c:353: Error: Unknown compression scheme encountered for file '/System/Library/CoreServices/CoreTypes.bundle/Contents/Library/AppExceptions.bundle/Exceptions.plist' Tim

6 6

Handling of deprecation packages
by Torsten Bergmann April 19, 2019

April 19, 2019

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.

4 5

MQTT Data Broker & Client in Smalltalk
by John M McIntosh April 18, 2019

April 18, 2019

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

3 4

Re: [Pharo-dev] Roassal Animations
by Norbert Hartl April 18, 2019

April 18, 2019

Great! Will this be part of the minimal roassal? That could improve documentation quite a bit. Norbert > Am 18.04.2019 um 01:05 schrieb Alexandre Bergel <alexandre.bergel(a)me.com>: > > 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> wrote: >>> >>> >>> From: Alexandre Bergel <alexandre.bergel(a)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> >>> >>> >>> 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. >> >> :) >> >> >

3 2

Re: [Pharo-dev] Roassal Animations
by ducasse April 18, 2019

April 18, 2019

> On 27 Mar 2019, at 18:27, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > > > From: Alexandre Bergel <alexandre.bergel(a)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> > > > 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. :)

2 2

[ANN] Next Pharo Sprint: April 26
by Marcus Denker April 18, 2019

April 18, 2019

We will organize a Pharo sprint / Moose dojo April 26, starting at 10:00am. (Local Time Paris). Goals of this sprint: - Pharo 8: Fix issues from tracker https://github.com/pharo-project/pharo/issues Remote Sprint: Remotely, you can join us on Discord. During the sprint, we synchronize local and remote Pharo sprinters: http://pharo.org/contribute-events We have added a Board to coordinate the work: https://github.com/orgs/pharo-project/projects/9 Known Local Sprint meetings Lille/France: It will be at the Inria Lille, Building B, third floor (RMoD offices). As the building is not open to the public, please contact us before if you plan to come

1 0

[Pharo 8.0] Build #230: 3199 Cleanup testAsBit methods
by ci-pharo-ci-jenkins2＠inria.fr April 18, 2019

April 18, 2019

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

1 0

[Pharo 8.0] Build #229: Fixing the broken test
by ci-pharo-ci-jenkins2＠inria.fr April 18, 2019

April 18, 2019

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

1 0

Re: [Pharo-dev] Roassal Animations
by Mariano Martinez Peck April 17, 2019

April 17, 2019

Yeah I have been following Milton animarioma and they are great! On Wed, Apr 17, 2019, 20:06 Alexandre Bergel via Pharo-dev < pharo-dev(a)lists.pharo.org> wrote: > 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> > wrote: > > > *From: *Alexandre Bergel <alexandre.bergel(a)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> > > > 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. > > > :) > > > >

1 0