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

[Pharo 8.0] Build #64: 2489-DatePrintFormatTester-should-be-removed
by ci-pharo-ci-jenkins2＠inria.fr Feb. 11, 2019

Feb. 11, 2019

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

1 0

[Pharo 8.0] Build #63: 2476-Cleaning-initialize-categorisation
by ci-pharo-ci-jenkins2＠inria.fr Feb. 11, 2019

Feb. 11, 2019

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

1 0

Esteban's ChangeLog week of 4 February 2019
by estebanlm＠gmail.com Feb. 11, 2019

Feb. 11, 2019

Hello! This is my weekly ChangeLog, from 4 February 2019 to 10 February 2019. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=4/2/2019&to=10/2/2019 ChangeLog ========= 9 February 2019: ---------------- * === On layouts As you know, I've been working on layouts for Spec 2. The basic layouts I want to have available next week(s) are four: * +SpecBoxLayout+ : A simple way to place components horizontally or vertically * +SpecPanedLayout+ : Same as box layout, but with a resizable splitter (and it will allow just two... if you want more you will need to compose). * +SpecGridLayout+ : To place components in a grid (x,y coordinates and spans) * +SpecXYLayout+ : This could be renamed as +SpecAbsoluteLayout+ and it's name says all, it will allow absolute location of components (obviously, in relation with its parent). For a second phase there will be a couple more +SpecFlowLayout+ and a kasowari layout (without name yet :P). The ones on first phase are the most important ones. In particular, we have detected that with first three (Box, Paned, Grid) we can reproduce everything we have currently in Pharo. The second phase will add possibilities for the future. Anyway, I have "kind-of-working" the first three, but I have problems when applying layouts here and there, because morphic time to time wants to behave differently than asked. One of the problems is that for this layouts, to make them behave correctly (and without a lot of work from users), I will need to add the concept of "minimum, preferred and maximum" extent. Reason why I'm playing with a small implementation of styling... which most probably will go away once I find the best way to handle this constraints. So, this week I have nothing finished, just a pointer to my current work: [https://github.com/estebanlm/Spec/tree/dev-2.0](https://github.com/estebanl… 7 February 2019: ---------------- * Small fix-a-day: [https://github.com/pharo-project/pharo/pull/2452](https://github.com/pharo-… cheers! Esteban

6 7

[Pharo 8.0] Build #62: 2486-Class-builder-should-call-initializeSlot-on-instance-migration
by ci-pharo-ci-jenkins2＠inria.fr Feb. 11, 2019

Feb. 11, 2019

There is a new Pharo build available! The status of the build #62 was: FAILURE. The Pull Request #2487 was integrated: "2486-Class-builder-should-call-initializeSlot-on-instance-migration" Pull request url: https://github.com/pharo-project/pharo/pull/2487 Issue Url: https://pharo.fogbugz.com/f/cases/2486 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

atRandom & integer agnosticism
by David Richards Feb. 11, 2019

Feb. 11, 2019

Hello community. Kindly consider: | n i r | n := ( 2 ** 256 ) - 1 . "the largest 256-bit value" i := ( 0 to: n ) . "the interval 0 to 2**256-1" "Produce three sets of computed test results." 3 timesRepeat: [ Transcript show: ( r := i atRandom ) ; cr . Transcript show: ( r asByteArray hex ) ; cr . ] According to comments in Pharo library code, atRandom fails for integer magnitudes greater than 2**30 . A reason for this limitation is not given, and it's not clear to a novice such as myself why the computed result of atRandom is permitted to sometimes be in conflict with the semantics of atRandom . Can anyone provide a basic explanation of the rationale for a 'broken' atRandom ? Alternatively, is this a known bug? Thanks. dr

3 4

[Pharo 8.0] Build #61: 2480-Remove-GTSpotterDoubleLinkedList
by ci-pharo-ci-jenkins2＠inria.fr Feb. 11, 2019

Feb. 11, 2019

There is a new Pharo build available! The status of the build #61 was: SUCCESS. The Pull Request #2481 was integrated: "2480-Remove-GTSpotterDoubleLinkedList" Pull request url: https://github.com/pharo-project/pharo/pull/2481 Issue Url: https://pharo.fogbugz.com/f/cases/2480 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[ANN] Registration for Pharo Days 2019 open!
by Esteban Lorenzano Feb. 11, 2019

Feb. 11, 2019

Dear all, I am pleased to announce that registration for Pharo Days 2019 is now open! Pharo days is a gathering of the Pharo community to exchange, discuss and code with your online colleagues. Join us to share your experiences and help to make a better Pharo! To register, please proceed to the Pharo Days 2019 web page: https://pharo.org/2019PharoDays <https://pharo.org/2019PharoDays>, or go directly to the association event: https://association.pharo.org/event-3255426 <https://association.pharo.org/event-3255426>. (Yes, the schedule is still to be defined, stay tuned). If there are any questions or problems, I am happy to answer them. Esteban Ps: Iâm sorry for multiple posts ;)

1 0

ConfigurationOfGrease for Pharo8
by Alistair Grant Feb. 11, 2019

Feb. 11, 2019

Hi All, It looks like Grease is still hosted on smalltalkhub - if not, please let me know where. Are there any objections to me updating ConfigurationOfGrease>>release1: to load on Pharo8? The updated method is (apologies for loss of formatting): release1: aSpec <symbolicVersion:#'release1'> aSpec for: #'pharo3.x' version: #'release1.3'. aSpec for: #'pharo4.x' version: #'release1.3'. aSpec for: #'pharo5.x' version: #'release1.3'. aSpec for: #'pharo6.x' version: #'release1.3'. aSpec for: #'pharo7.x' version: #'release1.3'. aSpec for: #'pharo8.x' version: #'release1.3'. aSpec for: #'squeak5.x' version: #'release1.3'. aSpec for: #'gs3.x' version: #'release1.3'. aSpec for: #'pharo1.x' version: #'release1.2'. aSpec for: #'pharo2.x' version: #'release1.2'. aSpec for: #'squeak4.x' version: #'release1.2'. aSpec for: #'gs2.x' version: #'release1.2' The change is the addition of the #'pharo8.x' line. Thanks, Alistair

6 12

[Pharo 8.0] Build #60: 2474-Cleaning-printing-protocols
by ci-pharo-ci-jenkins2＠inria.fr Feb. 9, 2019

Feb. 9, 2019

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

1 0

Roadmap for Pharo 8.0
by Esteban Lorenzano Feb. 8, 2019

Feb. 8, 2019

Hi list, We started Pharo 8.0 development and we wanted to share (and discuss, if needed) what is our current Roadmap for Pharo 8.0. As you can see, Windows is getting some love, and also UI. Anyway, here it is: Image === 1) Missing parts for headless VM to work (explained a bit later) 2) We need to improve Epicea speed. And in general, source access speed. We want to remove the old changes file (since Epicea already does that works and a lot more). 3) Improve Refactors 4) Improve Calypso 5) Introduce Spec2 (our re-work on this framework). - We also want to migrate our tools to it (Inspector, Debugger, Spotter and Calypso are the remaining parts). We will see how much of this migration can be done. VM/Low-level side === 1) headless vm We want to have a real headless VM and make it our default VM. To it, most of the work vm-side is already made by Ronie, but there are missing parts: - a build on windows - image side capabilities: we use SDL2 to start the world, and it mostly works... but not completely. One cool thing of this is that we will -finally- be able to clean the event handling, which is ugly (and works bad). 2) Windows several missing/non working parts: - file primitives are slow. This is because they rely in old APIs and we need to put them in "state of the art". - libgit2 does not processes long paths. We workarounded the problem with tonel, but at a point we need to take care about this. Real problem with this is we need to contribute the solution to libgit2, but this is also good Open Source policy (contributing back). - OSSubprocess in windows. We believe we need to extend OSSubprocess (our solution to communicate with system) to windows. And we believe is possible ;) 3) ThreadedFFI. It is already too much time since we have this in agenda. Is time to make it real. 4) memory policies. Tweaking the VM to enhance its memory usage is possible, but hard. We want to adopt an scheme of "memory policies" that will allow users to pick what they need. Process === 1) We will add multiple source directories to Iceberg. This is needed to allow us to put all Pharo sub-projects into an unique project without breaking modularisations. Others === 1) Launcher - Launcher us getting a new UI - Tests - It needs to be more solid (in part, that's the reason why we want OSSubprocess in windows). 2) Cargo - We need to revisit cargo (a new dependency manager) and at a point decide if it will fly or not :) Nice to have (most probably not this version, but in our TODO) : - embedded VM - event driven VM - what happens if we split VM into main thread and vm thread?

6 5