January 2020 - Pharo-dev - lists.pharo.org

Pharo key features (document)

by Pavel Krivanek

Hi, I have created a list of the key Pharo features with some images and animations that should help to explain to public what is cool on Pharo. It is based on a list formerly created for a Wikipedia article. https://github.com/pavel-krivanek/pharoMaterials/blob/master/features/Pharo… Please look at it to check if something is worth to add or change before we will try to use it somewhere for real. Cheers, -- Pavel

Jan. 5, 2020

Re: [Pharo-dev] BaselineOfZincHTTPComponents>>baseline:

by Tudor Girba

Hi, Would introducing branches in Zinc to deal with the different versions of Pharo not be an option? Cheers, Doru > On Jan 3, 2020, at 2:48 PM, Alistair Grant <akgrant0710(a)gmail.com> wrote: > > Hi Sven, > > On Fri, 3 Jan 2020 at 12:36, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> Alistair, >> >> Thanks for the write up, it is useful. >> >> However, the general situation with the relationship between Zinc HTTP Components and Pharo 8 (or its most recent version in development) is often difficult. >> >> For me, as author and maintainer of Zinc HTTP Components is had been very hard to follow the changes in the latest Pharo and to keep syncing/merging them back. >> >> Especially since some changes are not backwards compatible with Pharo 7 (the latest stable) and the previous ones (let's say 6 and 5). For me and most users that is unacceptable: HTTP is way too important to not maintain it properly. The problems with source code file access were an example of that, luckily Pablo reacted super fast. >> >> Another point of friction for me are the many cosmetic changes that were applied, often using automatic means. They do not contribute much (functionally), but cause lots of trouble (to merge, check, validate). >> >> Normally, years ago, Zinc was synced into Pharo trunk regularly (like every 6 months or so). However, this has not happened for a long time. Why ? Because I have too much work syncing/merging everything back first. >> >> So I have to put time in this, but it won't happen soon - too much other work. >> >> Some more comments inline. >> >>> On 3 Jan 2020, at 11:34, Alistair Grant <akgrant0710(a)gmail.com> wrote: >>> >>> Hi Sven, >>> >>> Following on from a discussion I started in Discord development... >>> >>> Loading Zinc SSO in Pharo 8 currently causes problems because the Zinc >>> packages in core Pharo 8 are out of sync with your repository >>> (specifically https://github.com/pharo-project/pharo/commit/45b7de2b6c901112be04230faba48… >>> caused problems for me). >> >> Hmm, I guess I missed that one, but I would of course see it when trying to merge back. >> >>> I was able to resolve the issue by modifying >>> BaselineOfZincHTTPComponents>>baseline: to remove all references to >>> the packages that are now part of core Pharo 8: >>> >>> BaselineOfZincHTTPComponents>>baseline: spec >>> <baseline> >>> spec for: #common do: [ >>> spec baseline: 'NeoJSON' with: [ spec repository: >>> 'github://svenvc/NeoJSON:v17/repository' ]. >>> spec baseline: 'XMLParser' with: [ spec repository: >>> 'github://feenkcom/XMLParser:v0.6.1/src' ]. >>> spec baseline: 'XMLWriter' with: [ spec repository: >>> 'github://feenkcom/XMLWriter:v0.6.0/src' ]. >>> "spec project: 'XML Support' with: [ spec className: >>> 'ConfigurationOfXMLSupport'; repository: >>> 'http://www.squeaksource.com/MetacelloRepository' ]." >>> spec >>> package: 'Zinc-AWS'; >>> package: 'Zinc-REST' with: [ spec requires: #('NeoJSON') ]; >>> package: 'Zinc-WebSocket-Core'; >>> package: 'Zinc-WebSocket-Tests' with: [ spec requires: >>> 'Zinc-WebSocket-Core' ]; >>> package: 'Zinc-SSO-OAuth1-Core' with: [ spec requires: >>> #('NeoJSON') ]; >>> package: 'Zinc-SSO-OAuth2-Core' with: [ spec requires: >>> #('NeoJSON') ]; >>> package: 'Zinc-SSO-OpenID-Core'; >>> package: 'Zinc-SSO-Demo' with: [ spec requires: >>> #('Zinc-SSO-OAuth1-Core' 'Zinc-SSO-OAuth2-Core' >>> 'Zinc-SSO-OpenID-Core') ]; >>> package: 'Zinc-SSO-OAuth1-Tests' with: [ spec requires: >>> #('Zinc-SSO-OAuth1-Core') ]; >>> package: 'Zinc-SSO-OpenID-Tests' with: [ spec requires: >>> #('Zinc-SSO-OpenID-Core') ]; >>> package: 'Zinc-WebDAV'; >>> package: 'Zinc-WWS-Server'; >>> package: 'Zinc-WWS-Client'. >>> spec >>> group: 'AWS' with: #('Zinc-AWS'); >>> group: 'WebDAV' with: #('Zinc-WebDAV'); >>> group: 'WebSocket' with: #('Zinc-WebSocket-Core' >>> 'Zinc-WebSocket-Tests'); >>> group: 'SSO-OAuth1' with: #('Zinc-SSO-OAuth1-Core' >>> 'Zinc-SSO-OAuth1-Tests'); >>> group: 'SSO-OAuth2' with: #('Zinc-SSO-OAuth2-Core'); >>> group: 'SSO-OpenID' with: #('Zinc-SSO-OpenID-Core' >>> 'Zinc-SSO-OpenID-Tests'); >>> group: 'SSO-Demo' with: #('Zinc-SSO-OAuth1-Core' >>> 'Zinc-SSO-OAuth2-Core' 'Zinc-SSO-OpenID-Core'); >>> group: 'SSO' with: #('SSO-OAuth1' 'SSO-OAuth2' >>> 'SSO-OpenID' 'SSO-Demo' 'Zinc-SSO-Demo'); >>> group: 'WWS' with: #('Zinc-WWS-Server' 'Zinc-WWS-Client'); >>> group: 'REST' with: #('Zinc-REST') ] >>> >>> >>> This isn't directly usable by you since it replaces 'XML Support' with >>> XMLParser and XMLWriter and it would break Pharo 7. >> >> I don't think using feenk repos is a solution > > That's why I wrote that it isn't directly usable - it references > feenk, which will obviously have to be removed, and it is Pharo 8 > specific, more on that below. > >> , especially since Torsten did official ports of the XML stuff. I would then certainly not use a old metacello configuration in squeak source, but would go to all GitHub/Tonel. >> >>> But if we modified it to put in checks for Pharo 7 vs Pharo 8 it would >>> somewhat future proof the code against changes made in core Pharo 8. >> >> Like I said, I really want to support two versions back (so today 7 and 6). > > I think what I'm proposing would support this. To expand a bit more, > the idea is to have: > > baseline: spec > <baseline> > > SystemVersion current major <= 7 > ifTrue: [ self baseline7: spec ] > ifFalse: [ self baseline: spec ] > > > baseline7: would be the existing baseline. The new baseline: would be > changed to remove all the references to the packages in core Pharo 8 > (similar to the example above, but without the feenk references). > > >> I would like that Pharo code developers that make changes to Zinc/Zodiac packages at the very least acknowledge and be careful of the fact that Zinc exists outside of one particular Pharo image and has to support some older versions. > > This obviously isn't a panacea, but it will at least reduce the impact > of some changes made in the pharo-project repository. > > I'm happy to submit a PR if you agree, > > Cheers, > Alistair -- feenk.com "Every successful trip needs a suitable vehicle."

Jan. 5, 2020

[Pharo 8.0] Build #1098: Updating the version of iceberg

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

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

Jan. 4, 2020

[Pharo 8.0] Build #1097: fix typo in Pharo-WelcomeHelp text

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

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

Jan. 3, 2020

Re: [Pharo-dev] BaselineOfZincHTTPComponents>>baseline:

by Alistair Grant

Hi Sven, On Fri, 3 Jan 2020 at 12:36, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > Alistair, > > Thanks for the write up, it is useful. > > However, the general situation with the relationship between Zinc HTTP Components and Pharo 8 (or its most recent version in development) is often difficult. > > For me, as author and maintainer of Zinc HTTP Components is had been very hard to follow the changes in the latest Pharo and to keep syncing/merging them back. > > Especially since some changes are not backwards compatible with Pharo 7 (the latest stable) and the previous ones (let's say 6 and 5). For me and most users that is unacceptable: HTTP is way too important to not maintain it properly. The problems with source code file access were an example of that, luckily Pablo reacted super fast. > > Another point of friction for me are the many cosmetic changes that were applied, often using automatic means. They do not contribute much (functionally), but cause lots of trouble (to merge, check, validate). > > Normally, years ago, Zinc was synced into Pharo trunk regularly (like every 6 months or so). However, this has not happened for a long time. Why ? Because I have too much work syncing/merging everything back first. > > So I have to put time in this, but it won't happen soon - too much other work. > > Some more comments inline. > > > On 3 Jan 2020, at 11:34, Alistair Grant <akgrant0710(a)gmail.com> wrote: > > > > Hi Sven, > > > > Following on from a discussion I started in Discord development... > > > > Loading Zinc SSO in Pharo 8 currently causes problems because the Zinc > > packages in core Pharo 8 are out of sync with your repository > > (specifically https://github.com/pharo-project/pharo/commit/45b7de2b6c901112be04230faba48… > > caused problems for me). > > Hmm, I guess I missed that one, but I would of course see it when trying to merge back. > > > I was able to resolve the issue by modifying > > BaselineOfZincHTTPComponents>>baseline: to remove all references to > > the packages that are now part of core Pharo 8: > > > > BaselineOfZincHTTPComponents>>baseline: spec > > <baseline> > > spec for: #common do: [ > > spec baseline: 'NeoJSON' with: [ spec repository: > > 'github://svenvc/NeoJSON:v17/repository' ]. > > spec baseline: 'XMLParser' with: [ spec repository: > > 'github://feenkcom/XMLParser:v0.6.1/src' ]. > > spec baseline: 'XMLWriter' with: [ spec repository: > > 'github://feenkcom/XMLWriter:v0.6.0/src' ]. > > "spec project: 'XML Support' with: [ spec className: > > 'ConfigurationOfXMLSupport'; repository: > > 'http://www.squeaksource.com/MetacelloRepository' ]." > > spec > > package: 'Zinc-AWS'; > > package: 'Zinc-REST' with: [ spec requires: #('NeoJSON') ]; > > package: 'Zinc-WebSocket-Core'; > > package: 'Zinc-WebSocket-Tests' with: [ spec requires: > > 'Zinc-WebSocket-Core' ]; > > package: 'Zinc-SSO-OAuth1-Core' with: [ spec requires: > > #('NeoJSON') ]; > > package: 'Zinc-SSO-OAuth2-Core' with: [ spec requires: > > #('NeoJSON') ]; > > package: 'Zinc-SSO-OpenID-Core'; > > package: 'Zinc-SSO-Demo' with: [ spec requires: > > #('Zinc-SSO-OAuth1-Core' 'Zinc-SSO-OAuth2-Core' > > 'Zinc-SSO-OpenID-Core') ]; > > package: 'Zinc-SSO-OAuth1-Tests' with: [ spec requires: > > #('Zinc-SSO-OAuth1-Core') ]; > > package: 'Zinc-SSO-OpenID-Tests' with: [ spec requires: > > #('Zinc-SSO-OpenID-Core') ]; > > package: 'Zinc-WebDAV'; > > package: 'Zinc-WWS-Server'; > > package: 'Zinc-WWS-Client'. > > spec > > group: 'AWS' with: #('Zinc-AWS'); > > group: 'WebDAV' with: #('Zinc-WebDAV'); > > group: 'WebSocket' with: #('Zinc-WebSocket-Core' > > 'Zinc-WebSocket-Tests'); > > group: 'SSO-OAuth1' with: #('Zinc-SSO-OAuth1-Core' > > 'Zinc-SSO-OAuth1-Tests'); > > group: 'SSO-OAuth2' with: #('Zinc-SSO-OAuth2-Core'); > > group: 'SSO-OpenID' with: #('Zinc-SSO-OpenID-Core' > > 'Zinc-SSO-OpenID-Tests'); > > group: 'SSO-Demo' with: #('Zinc-SSO-OAuth1-Core' > > 'Zinc-SSO-OAuth2-Core' 'Zinc-SSO-OpenID-Core'); > > group: 'SSO' with: #('SSO-OAuth1' 'SSO-OAuth2' > > 'SSO-OpenID' 'SSO-Demo' 'Zinc-SSO-Demo'); > > group: 'WWS' with: #('Zinc-WWS-Server' 'Zinc-WWS-Client'); > > group: 'REST' with: #('Zinc-REST') ] > > > > > > This isn't directly usable by you since it replaces 'XML Support' with > > XMLParser and XMLWriter and it would break Pharo 7. > > I don't think using feenk repos is a solution That's why I wrote that it isn't directly usable - it references feenk, which will obviously have to be removed, and it is Pharo 8 specific, more on that below. >, especially since Torsten did official ports of the XML stuff. I would then certainly not use a old metacello configuration in squeak source, but would go to all GitHub/Tonel. > > > But if we modified it to put in checks for Pharo 7 vs Pharo 8 it would > > somewhat future proof the code against changes made in core Pharo 8. > > Like I said, I really want to support two versions back (so today 7 and 6). I think what I'm proposing would support this. To expand a bit more, the idea is to have: baseline: spec <baseline> SystemVersion current major <= 7 ifTrue: [ self baseline7: spec ] ifFalse: [ self baseline: spec ] baseline7: would be the existing baseline. The new baseline: would be changed to remove all the references to the packages in core Pharo 8 (similar to the example above, but without the feenk references). > I would like that Pharo code developers that make changes to Zinc/Zodiac packages at the very least acknowledge and be careful of the fact that Zinc exists outside of one particular Pharo image and has to support some older versions. This obviously isn't a panacea, but it will at least reduce the impact of some changes made in the pharo-project repository. I'm happy to submit a PR if you agree, Cheers, Alistair

Jan. 3, 2020

Re: [Pharo-dev] BaselineOfZincHTTPComponents>>baseline:

by Sven Van Caekenberghe

Alistair, Thanks for the write up, it is useful. However, the general situation with the relationship between Zinc HTTP Components and Pharo 8 (or its most recent version in development) is often difficult. For me, as author and maintainer of Zinc HTTP Components is had been very hard to follow the changes in the latest Pharo and to keep syncing/merging them back. Especially since some changes are not backwards compatible with Pharo 7 (the latest stable) and the previous ones (let's say 6 and 5). For me and most users that is unacceptable: HTTP is way too important to not maintain it properly. The problems with source code file access were an example of that, luckily Pablo reacted super fast. Another point of friction for me are the many cosmetic changes that were applied, often using automatic means. They do not contribute much (functionally), but cause lots of trouble (to merge, check, validate). Normally, years ago, Zinc was synced into Pharo trunk regularly (like every 6 months or so). However, this has not happened for a long time. Why ? Because I have too much work syncing/merging everything back first. So I have to put time in this, but it won't happen soon - too much other work. Some more comments inline. > On 3 Jan 2020, at 11:34, Alistair Grant <akgrant0710(a)gmail.com> wrote: > > Hi Sven, > > Following on from a discussion I started in Discord development... > > Loading Zinc SSO in Pharo 8 currently causes problems because the Zinc > packages in core Pharo 8 are out of sync with your repository > (specifically https://github.com/pharo-project/pharo/commit/45b7de2b6c901112be04230faba48… > caused problems for me). Hmm, I guess I missed that one, but I would of course see it when trying to merge back. > I was able to resolve the issue by modifying > BaselineOfZincHTTPComponents>>baseline: to remove all references to > the packages that are now part of core Pharo 8: > > BaselineOfZincHTTPComponents>>baseline: spec > <baseline> > spec for: #common do: [ > spec baseline: 'NeoJSON' with: [ spec repository: > 'github://svenvc/NeoJSON:v17/repository' ]. > spec baseline: 'XMLParser' with: [ spec repository: > 'github://feenkcom/XMLParser:v0.6.1/src' ]. > spec baseline: 'XMLWriter' with: [ spec repository: > 'github://feenkcom/XMLWriter:v0.6.0/src' ]. > "spec project: 'XML Support' with: [ spec className: > 'ConfigurationOfXMLSupport'; repository: > 'http://www.squeaksource.com/MetacelloRepository' ]." > spec > package: 'Zinc-AWS'; > package: 'Zinc-REST' with: [ spec requires: #('NeoJSON') ]; > package: 'Zinc-WebSocket-Core'; > package: 'Zinc-WebSocket-Tests' with: [ spec requires: > 'Zinc-WebSocket-Core' ]; > package: 'Zinc-SSO-OAuth1-Core' with: [ spec requires: > #('NeoJSON') ]; > package: 'Zinc-SSO-OAuth2-Core' with: [ spec requires: > #('NeoJSON') ]; > package: 'Zinc-SSO-OpenID-Core'; > package: 'Zinc-SSO-Demo' with: [ spec requires: > #('Zinc-SSO-OAuth1-Core' 'Zinc-SSO-OAuth2-Core' > 'Zinc-SSO-OpenID-Core') ]; > package: 'Zinc-SSO-OAuth1-Tests' with: [ spec requires: > #('Zinc-SSO-OAuth1-Core') ]; > package: 'Zinc-SSO-OpenID-Tests' with: [ spec requires: > #('Zinc-SSO-OpenID-Core') ]; > package: 'Zinc-WebDAV'; > package: 'Zinc-WWS-Server'; > package: 'Zinc-WWS-Client'. > spec > group: 'AWS' with: #('Zinc-AWS'); > group: 'WebDAV' with: #('Zinc-WebDAV'); > group: 'WebSocket' with: #('Zinc-WebSocket-Core' > 'Zinc-WebSocket-Tests'); > group: 'SSO-OAuth1' with: #('Zinc-SSO-OAuth1-Core' > 'Zinc-SSO-OAuth1-Tests'); > group: 'SSO-OAuth2' with: #('Zinc-SSO-OAuth2-Core'); > group: 'SSO-OpenID' with: #('Zinc-SSO-OpenID-Core' > 'Zinc-SSO-OpenID-Tests'); > group: 'SSO-Demo' with: #('Zinc-SSO-OAuth1-Core' > 'Zinc-SSO-OAuth2-Core' 'Zinc-SSO-OpenID-Core'); > group: 'SSO' with: #('SSO-OAuth1' 'SSO-OAuth2' > 'SSO-OpenID' 'SSO-Demo' 'Zinc-SSO-Demo'); > group: 'WWS' with: #('Zinc-WWS-Server' 'Zinc-WWS-Client'); > group: 'REST' with: #('Zinc-REST') ] > > > This isn't directly usable by you since it replaces 'XML Support' with > XMLParser and XMLWriter and it would break Pharo 7. I don't think using feenk repos is a solution, especially since Torsten did official ports of the XML stuff. I would then certainly not use a old metacello configuration in squeak source, but would go to all GitHub/Tonel. > But if we modified it to put in checks for Pharo 7 vs Pharo 8 it would > somewhat future proof the code against changes made in core Pharo 8. Like I said, I really want to support two versions back (so today 7 and 6). > What do you think? > > Thanks, > Alistair I would like that Pharo code developers that make changes to Zinc/Zodiac packages at the very least acknowledge and be careful of the fact that Zinc exists outside of one particular Pharo image and has to support some older versions. Sven

Jan. 3, 2020

BaselineOfZincHTTPComponents>>baseline:

by Alistair Grant

Hi Sven, Following on from a discussion I started in Discord development... Loading Zinc SSO in Pharo 8 currently causes problems because the Zinc packages in core Pharo 8 are out of sync with your repository (specifically https://github.com/pharo-project/pharo/commit/45b7de2b6c901112be04230faba48… caused problems for me). I was able to resolve the issue by modifying BaselineOfZincHTTPComponents>>baseline: to remove all references to the packages that are now part of core Pharo 8: BaselineOfZincHTTPComponents>>baseline: spec <baseline> spec for: #common do: [ spec baseline: 'NeoJSON' with: [ spec repository: 'github://svenvc/NeoJSON:v17/repository' ]. spec baseline: 'XMLParser' with: [ spec repository: 'github://feenkcom/XMLParser:v0.6.1/src' ]. spec baseline: 'XMLWriter' with: [ spec repository: 'github://feenkcom/XMLWriter:v0.6.0/src' ]. "spec project: 'XML Support' with: [ spec className: 'ConfigurationOfXMLSupport'; repository: 'http://www.squeaksource.com/MetacelloRepository' ]." spec package: 'Zinc-AWS'; package: 'Zinc-REST' with: [ spec requires: #('NeoJSON') ]; package: 'Zinc-WebSocket-Core'; package: 'Zinc-WebSocket-Tests' with: [ spec requires: 'Zinc-WebSocket-Core' ]; package: 'Zinc-SSO-OAuth1-Core' with: [ spec requires: #('NeoJSON') ]; package: 'Zinc-SSO-OAuth2-Core' with: [ spec requires: #('NeoJSON') ]; package: 'Zinc-SSO-OpenID-Core'; package: 'Zinc-SSO-Demo' with: [ spec requires: #('Zinc-SSO-OAuth1-Core' 'Zinc-SSO-OAuth2-Core' 'Zinc-SSO-OpenID-Core') ]; package: 'Zinc-SSO-OAuth1-Tests' with: [ spec requires: #('Zinc-SSO-OAuth1-Core') ]; package: 'Zinc-SSO-OpenID-Tests' with: [ spec requires: #('Zinc-SSO-OpenID-Core') ]; package: 'Zinc-WebDAV'; package: 'Zinc-WWS-Server'; package: 'Zinc-WWS-Client'. spec group: 'AWS' with: #('Zinc-AWS'); group: 'WebDAV' with: #('Zinc-WebDAV'); group: 'WebSocket' with: #('Zinc-WebSocket-Core' 'Zinc-WebSocket-Tests'); group: 'SSO-OAuth1' with: #('Zinc-SSO-OAuth1-Core' 'Zinc-SSO-OAuth1-Tests'); group: 'SSO-OAuth2' with: #('Zinc-SSO-OAuth2-Core'); group: 'SSO-OpenID' with: #('Zinc-SSO-OpenID-Core' 'Zinc-SSO-OpenID-Tests'); group: 'SSO-Demo' with: #('Zinc-SSO-OAuth1-Core' 'Zinc-SSO-OAuth2-Core' 'Zinc-SSO-OpenID-Core'); group: 'SSO' with: #('SSO-OAuth1' 'SSO-OAuth2' 'SSO-OpenID' 'SSO-Demo' 'Zinc-SSO-Demo'); group: 'WWS' with: #('Zinc-WWS-Server' 'Zinc-WWS-Client'); group: 'REST' with: #('Zinc-REST') ] This isn't directly usable by you since it replaces 'XML Support' with XMLParser and XMLWriter and it would break Pharo 7. But if we modified it to put in checks for Pharo 7 vs Pharo 8 it would somewhat future proof the code against changes made in core Pharo 8. What do you think? Thanks, Alistair

Jan. 3, 2020

[Pharo 8.0] Build #1096: 5420-Menus-not-accessible-when-SHIFT-is-pressed

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

There is a new Pharo build available! The status of the build #1096 was: SUCCESS. The Pull Request #5422 was integrated: "5420-Menus-not-accessible-when-SHIFT-is-pressed" Pull request url: https://github.com/pharo-project/pharo/pull/5422 Issue Url: https://github.com/pharo-project/pharo/issues/5420 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Jan. 2, 2020

Fix for PlotMorph

by Hilaire

Stephan Eggermont, During this holiday I help my son with a data mining project, we use PlotMorph for 2D graphic. We have this little fix to PlotMorph: ------------------------------------------------------------------------ PlotSeties>>scaleTo: anRectangle height: heightInteger maxPoint: maxPoint minPoint: minPoint Â Â Â | drawExtent scaleFrom scaleTo | Â Â Â *drawExtent := maxPoint - minPoint.* Â Â Â drawExtent isZero Â Â Â Â Â Â ifTrue: [^ self]. Â Â Â scaleFrom := 0 @ 0 rectangle: drawExtent. Â Â Â scaleTo := anRectangle. Â Â Â points do: Â Â Â Â Â Â [:point | Â Â Â Â Â Â Â Â Â | tempPoint | Â Â Â Â Â Â Â Â Â tempPoint := point - minPoint scaleFrom: scaleFrom to: scaleTo. Â Â Â Â Â Â Â Â Â point scaledPoint: tempPoint x @ (heightInteger - tempPoint y)] ------------------------------------------------------------------------ Without this change, the code below does not work properly (scaling is not right): ------------------------------------------------------------------------ | m | m := PlotMorph plotPoints: { 0@0 . 0.59(a)0.88. 0.49(a)0.xn--49-qia }. m openInWindow. ------------------------------------------------------------------------ Thanks Hilaire -- Dr. Geo http://drgeo.eu

Jan. 1, 2020

Re: [Pharo-dev] Happy new year!

by Cyril Ferlicot

On Tue 31 Dec 2019 at 11:45, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > Hi, > > Just that, happy new year to everybody! :) > For 2020, letâs make a great Pharo 8 release and an even better Pharo 9. > > Cheers! > Esteban > Happy new year everyone! :) -- Cyril Ferlicot https://ferlicot.fr

Jan. 1, 2020