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

[Pharo 8.0] Build #258: 3300-Could-we-have-better-comment-for-SlotemitStore-
by ci-pharo-ci-jenkins2＠inria.fr May 7, 2019

May 7, 2019

There is a new Pharo build available! The status of the build #258 was: SUCCESS. The Pull Request #3309 was integrated: "3300-Could-we-have-better-comment-for-SlotemitStore-" Pull request url: https://github.com/pharo-project/pharo/pull/3309 Issue Url: https://github.com/pharo-project/pharo/issues/3300 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #257: update Calypso 0.16.4 which fixes broken tab selection
by ci-pharo-ci-jenkins2＠inria.fr May 7, 2019

May 7, 2019

There is a new Pharo build available! The status of the build #257 was: SUCCESS. The Pull Request #3308 was integrated: "update Calypso 0.16.4 which fixes broken tab selection" Pull request url: https://github.com/pharo-project/pharo/pull/3308 Issue Url: https://github.com/pharo-project/pharo/issues/updateCalypso0164 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #256: Use Calypso 0.16.3
by ci-pharo-ci-jenkins2＠inria.fr May 6, 2019

May 6, 2019

There is a new Pharo build available! The status of the build #256 was: FAILURE. The Pull Request #3298 was integrated: "Use Calypso 0.16.3" Pull request url: https://github.com/pharo-project/pharo/pull/3298 Issue Url: https://github.com/pharo-project/pharo/issues/updateCalypso0163 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Explaining Spec2 and why Bloc is on the roadmap
by ducasse May 4, 2019

May 4, 2019

Dear Pharoers We would like to explain what is Spec 2.0 and how Bloc is on the Pharo roadmap. Spec is a way to support a way to express and reuse application interaction logic. Spec was first developed by Benjamin van Ryseghem and others while supervised by StÃ©phane Ducasse. Over the years we cleaned Spec, but we never took the time to really revisit it, and Spec was never stressed outside the scope of Pharo tools (even if there is some people who used it in their projects, this was not the general case). There was a need to deeply rethink the way we express and reuse interaction application logic. Spec 2.0 revisits fundamentally Spec. The consortium wants to acknowledge the strong financial support of Schmidt in this new development. Here is a list of points we are working on to support companies to build modern applications with Pharo. - adding support for many widgets and at the same time improving existing widgets such as fasttable - adds much better layouts (we will deprecate the interpreter design) - introducing a new way to architecture an application: Spec20 introduces the notion of application to better handle resources and window flow - revisiting the internal logic of Spec (to remove useless parts and enhance the ones that works) - adding many tests In addition we want that Spec 2.0 is not tight anymore with Morphic. Why? Because we want to make sure that: - companies can deploy desktop applications - we can reuse all the tools logic of Pharo with new widgets sets such as Brick (widgets on top of Bloc) without having to rewrite everything. This is why Spec2.0 can optionally render using Gtk3.0. It also means that in the future we can have native widgets. Now that Bloc/Brick is finally reaching a point where it can be tried and eventually adopted, we want to make sure the transition to it will not force us to throw away the tools we developed last ten years. We think that Bloc needs some effort to clean and structure it and Spec2.0 gives the time to let Bloc and Brick mature. Also, we want to make sure that in the future we will be able to adopt other backends in case we decide it (Remember new now is old tomorrow and while Bloc/Brick is new and modern, it will not remain new and modern forever). Brick needs to be ready for Pharo consumption, and to make it possible we need to move the image to converge. With Spec 2.0, in future versions we will just need to define a new backend to get all our tools working. The Pharo Board

4 3

[Pharo 8.0] Build #255: add example: LazySlot
by ci-pharo-ci-jenkins2＠inria.fr May 4, 2019

May 4, 2019

There is a new Pharo build available! The status of the build #255 was: SUCCESS. The Pull Request #3293 was integrated: "add example: LazySlot" Pull request url: https://github.com/pharo-project/pharo/pull/3293 Issue Url: https://github.com/pharo-project/pharo/issues/3292 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Visit Tokyo from 27 June to 5 of July
by ducasse May 4, 2019

May 4, 2019

Dear Pharoers/Smalltalkers from Japan (and other countries) I will visit (mainly) Tokyo from 27 of June to 5th of July 2019. I will give several talks and one is scheduled to the Smalltalk User group (Oda Tomohiro is organising it). I will give some talks to researchers and companies. Iâm really excited to meet people. Do not hesitate to contact me so that we can plan extra meetings. I really want to see what you are doing and how to support the community. Stef

1 0

[Pharo 8.0] Build #254: Typos
by ci-pharo-ci-jenkins2＠inria.fr May 3, 2019

May 3, 2019

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

1 0

[Pharo 8.0] Build #253: 3269-Make-EmergencyEvaluator-work-again
by ci-pharo-ci-jenkins2＠inria.fr May 3, 2019

May 3, 2019

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

1 0

[Pharo 8.0] Build #252: 3289-beForText-is-deprecated-but-there-are-two-senders
by ci-pharo-ci-jenkins2＠inria.fr May 3, 2019

May 3, 2019

There is a new Pharo build available! The status of the build #252 was: SUCCESS. The Pull Request #3290 was integrated: "3289-beForText-is-deprecated-but-there-are-two-senders" Pull request url: https://github.com/pharo-project/pharo/pull/3290 Issue Url: https://github.com/pharo-project/pharo/issues/3289 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

Re: [Pharo-dev] [Pharo-users] Explaining Spec2 and why Bloc is on the roadmap
by Eric Gade May 3, 2019

May 3, 2019

Stef, Exciting news all around. Is this s good opportunity to revisit theming? I made a good attempt to wrap my head around themes about a year ago or so, but it's quite complex. If now's not (understandably) the time, how will themes work with this new multiple-backend approach? On Thu, May 2, 2019 at 11:45 AM Alexandre Bergel via Pharo-users < pharo-users(a)lists.pharo.org> wrote: > Hi Stef, > > Thanks for this email. Spec 2 really looks great. > It is also great to foresee an integration of Bloc/Brick in Pharo. > > Cheers, > Alexandre > > > On May 2, 2019, at 5:27 AM, ducasse <stepharo(a)netcourrier.com> wrote: > > > > Dear Pharoers > > > > We would like to explain what is Spec 2.0 and how Bloc is on the Pharo > roadmap. > > > > Spec is a way to support a way to express and reuse application > interaction logic. > > Spec was first developed by Benjamin van Ryseghem and others while > supervised > > by StÃ©phane Ducasse. > > Over the years we cleaned Spec, but we never took the time to really > revisit it, and Spec > > was never stressed outside the scope of Pharo tools (even if there is > some people who > > used it in their projects, this was not the general case). There was a > need to deeply rethink > > the way we express and reuse interaction application logic. > > > > Spec 2.0 revisits fundamentally Spec. The consortium wants to > acknowledge the strong financial > > support of Schmidt in this new development. Here is a list of points we > are working on to support companies > > to build modern applications with Pharo. > > > > - adding support for many widgets and at the same time improving > existing widgets such as fasttable > > - adds much better layouts (we will deprecate the interpreter > design) > > - introducing a new way to architecture an application: > > Spec20 introduces the notion of application to better handle > resources and window flow > > - revisiting the internal logic of Spec (to remove useless parts > and enhance the ones that works) > > - adding many tests > > > > In addition we want that Spec 2.0 is not tight anymore with Morphic. > > Why? Because we want to make sure that: > > - companies can deploy desktop applications > > - we can reuse all the tools logic of Pharo with new widgets sets > such as Brick (widgets on top of Bloc) > > without having to rewrite everything. > > > > This is why Spec2.0 can optionally render using Gtk3.0. It also means > that in the future we can have native widgets. > > > > Now that Bloc/Brick is finally reaching a point where it can be tried > and eventually adopted, we want to > > make sure the transition to it will not force us to throw away the tools > we developed last ten years. > > We think that Bloc needs some effort to clean and structure it and > Spec2.0 gives the time to let Bloc and Brick > > mature. Also, we want to make sure that in the future we will be able to > adopt other backends in case we > > decide it (Remember new now is old tomorrow and while Bloc/Brick is new > and modern, it will not remain > > new and modern forever). > > > > Brick needs to be ready for Pharo consumption, and to make it possible > we need to move the image to converge. > > With Spec 2.0, in future versions we will just need to define a new > backend to get all our tools working. > > > > The Pharo Board > > > > > > > > > -- Eric

2 1