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

[Pharo 8.0] Build #254: Typos

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

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…

May 3, 2019

[Pharo 8.0] Build #253: 3269-Make-EmergencyEvaluator-work-again

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

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…

May 3, 2019

[Pharo 8.0] Build #252: 3289-beForText-is-deprecated-but-there-are-two-senders

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

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…

May 3, 2019

Re: [Pharo-dev] [Pharo-users] Explaining Spec2 and why Bloc is on the roadmap

by StÃ©phane Ducasse

Hi Eric I do not really know and let esteban answer. In GTK3 the themes are based on CSS. Now for Morphic we still do it the old way. Now in P8 we started to clean the themes but if you want to help you are welcomed because our plates are quite full. Stef > On 2 May 2019, at 20:38, Eric Gade <eric.gade(a)gmail.com> wrote: > > 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 <mailto:pharo-users@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 <mailto:stepharo@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 -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr http://www.synectique.eu / http://www.pharo.org 03 59 35 87 52 Assistant: Julie Jonas FAX 03 59 57 78 50 TEL 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza Villeneuve d'Ascq 59650 France

May 3, 2019

[Pharo 8.0] Build #251: 3276-adding-initializeSlots-may-break-instance-initialization

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

There is a new Pharo build available! The status of the build #251 was: FAILURE. The Pull Request #3277 was integrated: "3276-adding-initializeSlots-may-break-instance-initialization" Pull request url: https://github.com/pharo-project/pharo/pull/3277 Issue Url: https://github.com/pharo-project/pharo/issues/3276 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

May 3, 2019

Re: [Pharo-dev] Explaining Spec2 and why Bloc is on the roadmap

by Ben Coman

Thanks for the background info Steph. On Thu, 2 May 2019 at 17:28, ducasse <stepharo(a)netcourrier.com> wrote: > Spec 2.0 revisits fundamentally Spec. > - adds much better layouts (we will deprecate the interpreter design) A very long time ago that I was debugging a Spec app was that debugging INTO the framework from application code would take 30 odd steps before it got to evaluate the block passed by the application code. Sorry thats a bit vague, but I'm hoping deprecating the interpreter will improve such experience. As a general comment also, architectures using stored blocks for configuration rather than passing in an "object with defined methods" seems a lot "less live". Changing the code inside the block doesn't change the behaviour of existing elements. But maybe the "methods" way has its own issues. cheers -ben

May 3, 2019

Re: [Pharo-dev] [Pharo-users] Explaining Spec2 and why Bloc is on the roadmap

by Eric Gade

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

May 2, 2019

Re: [Pharo-dev] Explaining Spec2 and why Bloc is on the roadmap

by Alexandre Bergel

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 > > >

May 2, 2019

[ANN] Pharo Consortium New Academic Member: ISCLab

by Marcus Denker

The Pharo Consortium is very happy to announce that ISCLab has joined the Consortium as an Academic Member. About - ISCLab: Intelligent Software Construction Laboratory, Department of Computer Science, FCFM, University of Chile. The ISCLab develops methodologies to build software systems that are both resource efficient (CPU, memory, energy) and adequate with modern software development techniques. We push further the knowledge frontier of Software Engineering with innovative methodologies, rigorous empirical evaluations, and valuable software artifacts. https://isclab.dcc.uchile.cl - Pharo Consortium: http://consortium.pharo.org The goal of the Pharo Consortium is to allow companies and institutions to support the ongoing development and future of Pharo. Individuals can support Pharo via the Pharo Association: http://association.pharo.org

May 2, 2019

Explaining Spec2 and why Bloc is on the roadmap

by ducasse

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

May 2, 2019