- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [Pharo 7.0-dev] Build #135: 20434-use-Ring2-during-the-bootstrap

by Sven Van Caekenberghe

> On 20 Sep 2017, at 11:40, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > More infos about Ring2: > > https://www.slideshare.net/esug/metamodeling-of-custom-pharo-images The cartoons on the slides are hilarious ! >> On 20 Sep 2017, at 11:32, ci-pharo-ci-jenkins2(a)inria.fr wrote: >> >> There is a new Pharo build available! >> >> The status of the build #135 was: SUCCESS. >> >> The Pull Request #294 was integrated: "20434-use-Ring2-during-the-bootstrap" >> Pull request url: https://github.com/pharo-project/pharo/pull/294 >> >> Issue Url: https://pharo.fogbugz.com/f/cases/20434 >> Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2… > >

Sept. 20, 2017

Re: [Pharo-dev] [Pharo 7.0-dev] Build #135: 20434-use-Ring2-during-the-bootstrap

by Marcus Denker

More infos about Ring2: https://www.slideshare.net/esug/metamodeling-of-custom-pharo-images > On 20 Sep 2017, at 11:32, ci-pharo-ci-jenkins2(a)inria.fr wrote: > > There is a new Pharo build available! > > The status of the build #135 was: SUCCESS. > > The Pull Request #294 was integrated: "20434-use-Ring2-during-the-bootstrap" > Pull request url: https://github.com/pharo-project/pharo/pull/294 > > Issue Url: https://pharo.fogbugz.com/f/cases/20434 > Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Sept. 20, 2017

[Pharo 7.0-dev] Build #135: 20434-use-Ring2-during-the-bootstrap

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

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

Sept. 20, 2017

Re: [Pharo-dev] Bloc status

by Tudor Girba

Hi, > On Sep 20, 2017, at 10:23 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > >> >> On 20 Sep 2017, at 10:12, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> >> Hi, >> >>> On Sep 20, 2017, at 9:22 AM, Norbert Hartl <norbert(a)hartl.name> wrote: >>> >>> >>> >>>> Am 19.09.2017 um 22:50 schrieb Tudor Girba <tudor(a)tudorgirba.com>: >>>> >>>> Hi, >>>> >>>> Thanks for the question :). >>>> >>>> Indeed, the summary of Stef is quite good. >>>> >>>> Here are some additions: >>>> - Indeed, Bloc gets stable. Recently, we learned that we can optimize the layouts even more and Alex Syrel will work on that in the next couple of weeks, but this will not impact users. >>> >>> can't this be done later? I would prefer that making Bloc and Brick usable is the first target. >> >> I can sympathize with that. We also want to get to a usable state as soon as possible. >> >> However, we have a different way of prioritizing and this might seem somewhat counter intuitive. I strongly believe that some things cannot be rushed and that continuously investing in the underlying infrastructure pays off in the mid-term. So, when we see an opportunity to rephrase our understanding we take it earlier rather than later. This is one of these cases. >> > > But it is clear (having spend 10 years in the Squeak communityâ¦) that there is a danger in that, tooâ¦ will there ever be a point were you will *not* > be able to do things better? > > Ah, I even gave a talk about that: > > https://www.slideshare.net/MarcusDenker/perfection-feedback-loops-or-why-wo… > > > ;-) I agree. However, I see differences: - We choose to invest our energy in things that have a concrete outlook, often using time boxes and guided through a lot of experimentation. - If you get the cost of experimentation lower, you can simply perform more experiments and this increases the chances of producing surprising results. - The output is tangible and is constant, which means that we do not get stuck in an endless loop. It might take longer than people expect, but on the other hand, the results are consistently surprising. - In the meantime, Bloc is usable since half a year (the tutorial from ESUG was also given at PharoDays and works out of the box). And perhaps another thing that is not so clear: Bloc is a team effort and we, at feenk, are part of that team effort. From feenkâs point of view, we see it as an investment and we commit to make Bloc a platform that others can use for the next 10 years. For example, Alex works exclusively on this. As we are a commercial entity, for us this is a business issue, not a hobby. This means that we have all incentives to finish things so that we can build what we actually want to build :). Doru > Marcus -- www.tudorgirba.com www.feenk.com âLive like you mean it."

Sept. 20, 2017

Re: [Pharo-dev] Bloc status

by Marcus Denker

> On 20 Sep 2017, at 10:12, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Hi, > >> On Sep 20, 2017, at 9:22 AM, Norbert Hartl <norbert(a)hartl.name> wrote: >> >> >> >>> Am 19.09.2017 um 22:50 schrieb Tudor Girba <tudor(a)tudorgirba.com>: >>> >>> Hi, >>> >>> Thanks for the question :). >>> >>> Indeed, the summary of Stef is quite good. >>> >>> Here are some additions: >>> - Indeed, Bloc gets stable. Recently, we learned that we can optimize the layouts even more and Alex Syrel will work on that in the next couple of weeks, but this will not impact users. >> >> can't this be done later? I would prefer that making Bloc and Brick usable is the first target. > > I can sympathize with that. We also want to get to a usable state as soon as possible. > > However, we have a different way of prioritizing and this might seem somewhat counter intuitive. I strongly believe that some things cannot be rushed and that continuously investing in the underlying infrastructure pays off in the mid-term. So, when we see an opportunity to rephrase our understanding we take it earlier rather than later. This is one of these cases. > But it is clear (having spend 10 years in the Squeak communityâ¦) that there is a danger in that, tooâ¦ will there ever be a point were you will *not* be able to do things better? Ah, I even gave a talk about that: https://www.slideshare.net/MarcusDenker/perfection-feedback-loops-or-why-wo… ;-) Marcus

Sept. 20, 2017

[Pharo 7.0-dev] Build #134: 20431-Move-initialization-of-Color-InstructionStream-and-SmallInteger

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

There is a new Pharo build available! The status of the build #134 was: SUCCESS. The Pull Request #290 was integrated: "20431-Move-initialization-of-Color-InstructionStream-and-SmallInteger" Pull request url: https://github.com/pharo-project/pharo/pull/290 Issue Url: https://pharo.fogbugz.com/f/cases/20431 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Sept. 20, 2017

[Pharo 7.0-dev] Build #133: 20437 recategorized methods

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

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

Sept. 20, 2017

Re: [Pharo-dev] Bloc status

by Tudor Girba

Hi, > On Sep 20, 2017, at 9:22 AM, Norbert Hartl <norbert(a)hartl.name> wrote: > > > >> Am 19.09.2017 um 22:50 schrieb Tudor Girba <tudor(a)tudorgirba.com>: >> >> Hi, >> >> Thanks for the question :). >> >> Indeed, the summary of Stef is quite good. >> >> Here are some additions: >> - Indeed, Bloc gets stable. Recently, we learned that we can optimize the layouts even more and Alex Syrel will work on that in the next couple of weeks, but this will not impact users. > > can't this be done later? I would prefer that making Bloc and Brick usable is the first target. I can sympathize with that. We also want to get to a usable state as soon as possible. However, we have a different way of prioritizing and this might seem somewhat counter intuitive. I strongly believe that some things cannot be rushed and that continuously investing in the underlying infrastructure pays off in the mid-term. So, when we see an opportunity to rephrase our understanding we take it earlier rather than later. This is one of these cases. Cheers, Doru > Norbert >> - We have just finished an alpha version of the editor that is both moldable and scalable. Itâs alpha because there are still things to fine tune in the area of selection, insertion and deletion. >> - Having an editor is significant step because it is the most expensive (and the riskiest) widget mechanism. >> - After the layouts and editor we will focus on the model for interaction and animation of widgets and play with various classes of applications. >> - In the meantime, Theo Mugnier worked with Alain Plantec and did a brilliant job at providing an initial version of a SVG import-export. There are still things to do, but this is really cool work. >> >> I prefer to not go into estimations because I prefer to allow for the space to build crazy things, but we will work intensively on Bloc and Brick over the coming months, likely well into next year. >> >> Cheers, >> Doru >> >> >> >>> On Sep 19, 2017, at 8:46 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: >>> >>> Hi Torsten >>> >>> I will let Doru present it in more detail but I think that he is in vacation. >>> Now here is my take from the discussion I got at ESUG. >>> >>> - Bloc is getting stable and people should really start to use it. >>> This is why we did the bloc tutorial. We need more on that front. >>> I plan to use it for some projects >>> during the lectures I will give at Prague. >>> BTW I would like to have a turtle for my new book. :) >>> >>> - Brick >>> The text editor was a really important element to build widgets. >>> The text editor model is basically the second iteration based on >>> TxText attempt. >>> It scales well. >>> >>> As soon as we start to have widgets we should do a Spec mapping >>> and see how we can get rid of the middle man (the adapter should not >>> be used at runtime). >>> >>> Bloc and Brick are not on the Pharo 70 roadmap because the process >>> should be fixed before. >>> But we would love to have bloc and brick as preview. >>> >>> Esteban is currently working with Ronnie for the SDL integration, >>> headless image and others. >>> >>> Stef >>> >>> >>> >>> >>> >>>> On Tue, Sep 19, 2017 at 5:51 PM, Torsten Bergmann <astares(a)gmx.de> wrote: >>>> Hi, >>>> >>>> what is the current status of Bloc and Brick? >>>> How likely is it that Bloc goes into Pharo 7? >>>> >>>> Anyone able to give a short update on current work >>>> and plans? >>>> >>>> Thanks >>>> T. >>>> >>> >> >> -- >> www.tudorgirba.com >> www.feenk.com >> >> "We are all great at making mistakes." > -- www.tudorgirba.com www.feenk.com "Obvious things are difficult to teach."

Sept. 20, 2017

Re: [Pharo-dev] Bloc status

by Norbert Hartl

> Am 19.09.2017 um 22:50 schrieb Tudor Girba <tudor(a)tudorgirba.com>: > > Hi, > > Thanks for the question :). > > Indeed, the summary of Stef is quite good. > > Here are some additions: > - Indeed, Bloc gets stable. Recently, we learned that we can optimize the layouts even more and Alex Syrel will work on that in the next couple of weeks, but this will not impact users. can't this be done later? I would prefer that making Bloc and Brick usable is the first target. Norbert > - We have just finished an alpha version of the editor that is both moldable and scalable. Itâs alpha because there are still things to fine tune in the area of selection, insertion and deletion. > - Having an editor is significant step because it is the most expensive (and the riskiest) widget mechanism. > - After the layouts and editor we will focus on the model for interaction and animation of widgets and play with various classes of applications. > - In the meantime, Theo Mugnier worked with Alain Plantec and did a brilliant job at providing an initial version of a SVG import-export. There are still things to do, but this is really cool work. > > I prefer to not go into estimations because I prefer to allow for the space to build crazy things, but we will work intensively on Bloc and Brick over the coming months, likely well into next year. > > Cheers, > Doru > > > >> On Sep 19, 2017, at 8:46 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: >> >> Hi Torsten >> >> I will let Doru present it in more detail but I think that he is in vacation. >> Now here is my take from the discussion I got at ESUG. >> >> - Bloc is getting stable and people should really start to use it. >> This is why we did the bloc tutorial. We need more on that front. >> I plan to use it for some projects >> during the lectures I will give at Prague. >> BTW I would like to have a turtle for my new book. :) >> >> - Brick >> The text editor was a really important element to build widgets. >> The text editor model is basically the second iteration based on >> TxText attempt. >> It scales well. >> >> As soon as we start to have widgets we should do a Spec mapping >> and see how we can get rid of the middle man (the adapter should not >> be used at runtime). >> >> Bloc and Brick are not on the Pharo 70 roadmap because the process >> should be fixed before. >> But we would love to have bloc and brick as preview. >> >> Esteban is currently working with Ronnie for the SDL integration, >> headless image and others. >> >> Stef >> >> >> >> >> >>> On Tue, Sep 19, 2017 at 5:51 PM, Torsten Bergmann <astares(a)gmx.de> wrote: >>> Hi, >>> >>> what is the current status of Bloc and Brick? >>> How likely is it that Bloc goes into Pharo 7? >>> >>> Anyone able to give a short update on current work >>> and plans? >>> >>> Thanks >>> T. >>> >> > > -- > www.tudorgirba.com > www.feenk.com > > "We are all great at making mistakes."

Sept. 20, 2017

Pharo-Launcher Windows 10 requires admin privilg

by Alex Laurie

Latest version of Pharo launcher requires Admin privileges to launch properly. If it doesn't have Admin permission it throws a "stdout does not exist." error. Not sure if this is the right mailing list for the launcher, if not let me know. Cheers, Alex

Sept. 20, 2017