July 2018 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Charting in Roassal2

by Shaping

Thank you , Alexandre. That's exactly what I needed to know. Adapting the whisker plots should be straightforward. Shaping From: Alexandre Bergel [mailto:alexandre.bergel@me.com] Sent: Tuesday, July 31, 2018 3:47 PM To: Pharo Development List <pharo-dev(a)lists.pharo.org> Cc: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> Subject: Re: [Pharo-dev] Charting in Roassal2 Hi! Roassal supports Whisker plots, but not exactly candlestick. You can try this: -=-=-=-=-=-=-=-=-=-=-=-= | b createList r | r := Random new. createList := [ :size :d1 :d2 | (1 to: size) collect: [ :i | d1 + (r next * (d2-d1))] ]. b := RTGrapher new. (1 to: 10) do: [ :i | | ds | ds := RTBoxPlotDataSet new. ds points: (createList value: 20 value: 0 value: 20). b add: ds.]. b -=-=-=-=-=-=-=-=-=-=-=-= Which produces: Another example: =-=-==-=-==-=-==-=-==-=-==-=-==-=-==-=-==-=-==-=-= | b ds | b := RTGrapher new. b extent: 400 @ 200. RTShape withAllSubclasses do: [ :cls | ds := RTBoxPlotDataSet new. ds points: (cls rtmethods collect: #numberOfLinesOfCode). b add: ds ]. ^ b =-=-==-=-==-=-==-=-==-=-==-=-==-=-==-=-==-=-==-=-= Which shows the distribution of methods size in Roassal Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. On Jul 27, 2018, at 8:47 PM, Shaping <shaping(a)uurda.org <mailto:shaping@uurda.org> > wrote: Hi Folks. Can anyone tell me whether we have candlestick-charting ability in Roassal2? Shaping

July 31, 2018

Re: [Pharo-dev] Charting in Roassal2

by Alexandre Bergel

Hi! Roassal supports Whisker plots, but not exactly candlestick. You can try this: -=-=-=-=-=-=-=-=-=-=-=-= | b createList r | r := Random new. createList := [ :size :d1 :d2 | (1 to: size) collect: [ :i | d1 + (r next * (d2-d1))] ]. b := RTGrapher new. (1 to: 10) do: [ :i | | ds | ds := RTBoxPlotDataSet new. ds points: (createList value: 20 value: 0 value: 20). b add: ds.]. b -=-=-=-=-=-=-=-=-=-=-=-= Which produces: Another example: =-=-==-=-==-=-==-=-==-=-==-=-==-=-==-=-==-=-==-=-= | b ds | b := RTGrapher new. b extent: 400 @ 200. RTShape withAllSubclasses do: [ :cls | ds := RTBoxPlotDataSet new. ds points: (cls rtmethods collect: #numberOfLinesOfCode). b add: ds ]. ^ b =-=-==-=-==-=-==-=-==-=-==-=-==-=-==-=-==-=-==-=-= Which shows the distribution of methods size in Roassal Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On Jul 27, 2018, at 8:47 PM, Shaping <shaping(a)uurda.org> wrote: > > Hi Folks. > > Can anyone tell me whether we have candlestick-charting ability in Roassal2? > > > Shaping

July 31, 2018

[Pharo 7.0-dev] Build #1147: 22218 Cleanup System-OSEnvironments and deprecate OSEnvironment(class)>>default

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

There is a new Pharo build available! The status of the build #1147 was: SUCCESS. The Pull Request #1605 was integrated: "22218 Cleanup System-OSEnvironments and deprecate OSEnvironment(class)>>default" Pull request url: https://github.com/pharo-project/pharo/pull/1605 Issue Url: https://pharo.fogbugz.com/f/cases/22218 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

July 31, 2018

[Pharo 7.0-dev] Build #1146: 21755-We-should-renamed-Matrix-into-its-old-name-Array2D

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

There is a new Pharo build available! The status of the build #1146 was: SUCCESS. The Pull Request #1650 was integrated: "21755-We-should-renamed-Matrix-into-its-old-name-Array2D" Pull request url: https://github.com/pharo-project/pharo/pull/1650 Issue Url: https://pharo.fogbugz.com/f/cases/21755 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

July 31, 2018

[Pharo 7.0-dev] Build #1145: 22061-assert-should-be-rewritten-in-terms-of-assertdescription

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

There is a new Pharo build available! The status of the build #1145 was: SUCCESS. The Pull Request #1661 was integrated: "22061-assert-should-be-rewritten-in-terms-of-assertdescription" Pull request url: https://github.com/pharo-project/pharo/pull/1661 Issue Url: https://pharo.fogbugz.com/f/cases/22061 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

July 30, 2018

[Pharo 7.0-dev] Build #1144: new Method Finder

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

There is a new Pharo build available! The status of the build #1144 was: FAILURE. The Pull Request #1662 was integrated: "new Method Finder" Pull request url: https://github.com/pharo-project/pharo/pull/1662 Issue Url: https://pharo.fogbugz.com/f/cases/finder Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

July 30, 2018

[Pharo 7.0-dev] Build #1143: 22085 - Fix for infinite debugger

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

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

July 30, 2018

[Pharo 7.0-dev] Build #1142: 22251-Open-Repository-with-Monticello-gives-DNU

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

There is a new Pharo build available! The status of the build #1142 was: SUCCESS. The Pull Request #1656 was integrated: "22251-Open-Repository-with-Monticello-gives-DNU" Pull request url: https://github.com/pharo-project/pharo/pull/1656 Issue Url: https://pharo.fogbugz.com/f/cases/22251 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

July 30, 2018

Re: [Pharo-dev] Esteban's ChangeLog week of 23 July 2018

by Esteban Lorenzano

Hi Nico, > On 30 Jul 2018, at 09:02, Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> wrote: > > Hi Esteban, > I encountered this problem a few months ago. > I tried to document FFI with a serie of stackoverflow questions > https://stackoverflow.com/questions/49783882/how-one-deals-with-typedefs-in… <https://stackoverflow.com/questions/49783882/how-one-deals-with-typedefs-in…> > https://stackoverflow.com/questions/49784522/how-one-supports-both-32-and-6… <https://stackoverflow.com/questions/49784522/how-one-supports-both-32-and-6…> Thankfully this is kind of trivial with UFFI (once identified the problem), look at: https://github.com/pharo-project/pharo/pull/1660 <https://github.com/pharo-project/pharo/pull/1660> > > After a deep analysis, I think that FFI needs a serious refactoring (plugin code + image code). Been there, done that :) UFFI is a complete revamp of the image side code. I didnât touch the backend (since our philosophy is to put as much as possible into the image, this was possible) but I think it needs a serious re-think at least in two fields: - basic types needs to be the generic (uint32, uint64, etc.). - external datas have no meaningful use and it adds complexity. - callback logic needs to be moved from Alien to FFI > But I have stopped that work in the middle... (no time available for a few months). > The next thing I wanted to do is to study all your efforts with UFFI, and how you found workarounds for other pitfalls like > https://stackoverflow.com/questions/49784253/how-one-deals-with-multiple-po… <https://stackoverflow.com/questions/49784253/how-one-deals-with-multiple-po…> > https://stackoverflow.com/questions/49783443/how-one-defines-a-fixed-size-a… <https://stackoverflow.com/questions/49783443/how-one-defines-a-fixed-size-a…> > https://stackoverflow.com/questions/49783126/how-one-defines-a-union-type-i… <https://stackoverflow.com/questions/49783126/how-one-defines-a-union-type-i…> > https://stackoverflow.com/questions/49782651/how-one-aligns-structure-field… <https://stackoverflow.com/questions/49782651/how-one-aligns-structure-field…> Solved in UFFI. Cheers, Esteban > > Cheers > > > 2018-07-30 8:00 GMT+02:00 <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>>: > Hello! > > This is my weekly ChangeLog, from 23 July 2018 to 29 July 2018. > You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=23/7/2018&to=29/7/2018 <http://log.smallworks.eu/web/search?from=23/7/2018&to=29/7/2018> > > ChangeLog > ========= > > 27 July 2018: > ------------- > > * I found a problem that was making win64 bit version to crash: size_t implementation on UFFI was not resolving properly there (since it was mapped to a long, which is not correct on win64 architecture). > > To fix it, I changed FFISizeT type to work as FFILong, with different "real types" depending on architecture. > > Now, there is a problem to solve because structures using this type (like +LGitStringArray+) need to be regenerated, which may generate some difficulties... will see. > > > 23 July 2018: > ------------- > > * So well. Spent the full day debugging libgit2 without symbol information :( > > There is some problem with adding paths to an index and I still cannot figure out what's the problem. > > I'll continue trying tomorrow. > > > cheers! > Esteban > >

July 30, 2018

[Pharo 7.0-dev] Build #1141: 22089-Integrate-new-Calypso-0115

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

There is a new Pharo build available! The status of the build #1141 was: FAILURE. The Pull Request #1507 was integrated: "22089-Integrate-new-Calypso-0115" Pull request url: https://github.com/pharo-project/pharo/pull/1507 Issue Url: https://pharo.fogbugz.com/f/cases/22089 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

July 30, 2018