August 2015 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] we are running dependencies breaking sprints....

by phil＠highoctane.be

what's a tahe? Le 15 aoÃ»t 2015 15:49, "stepharo" <stepharo(a)free.fr> a Ã©crit : > I forgot to mention that people can help since we added a tahe > pharo-bootstrap. > > Stef > > Le 15/8/15 10:53, Tudor Girba a Ã©crit : > > This is exciting. Thanks a lot for this effort! > > Doru > > On Sat, Aug 15, 2015 at 10:50 AM, stepharo <stepharo(a)free.fr> wrote: > >> Hi guys >> >> just to let you know that we run a dependencies breaking sprint yesterday >> and it was great. >> We will redo one or two. >> Our goal is to minimise the dependencies of adding Monticello to the >> pharo bootstrap. >> What I can tell you is that having a bootstrap is bringing an >> ***AMAZING*** level of cleaner design. >> I suspected it. But when we see the real cases this is obvious and really >> important. >> I will really open a complete new world for Pharo in terms of modularity >> (of course it will take time >> but this is really really cool). >> >> Stef >> >> > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > > >

Aug. 15, 2015

Re: [Pharo-dev] we are running dependencies breaking sprints....

by Dimitris Chloupis

A "how to help with Pharo Bootstrap" article could help us help you ;) On Sat, Aug 15, 2015 at 4:49 PM stepharo <stepharo(a)free.fr> wrote: > I forgot to mention that people can help since we added a tahe > pharo-bootstrap. > > Stef > > Le 15/8/15 10:53, Tudor Girba a Ã©crit : > > This is exciting. Thanks a lot for this effort! > > Doru > > On Sat, Aug 15, 2015 at 10:50 AM, stepharo <stepharo(a)free.fr> wrote: > >> Hi guys >> >> just to let you know that we run a dependencies breaking sprint yesterday >> and it was great. >> We will redo one or two. >> Our goal is to minimise the dependencies of adding Monticello to the >> pharo bootstrap. >> What I can tell you is that having a bootstrap is bringing an >> ***AMAZING*** level of cleaner design. >> I suspected it. But when we see the real cases this is obvious and really >> important. >> I will really open a complete new world for Pharo in terms of modularity >> (of course it will take time >> but this is really really cool). >> >> Stef >> >> > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > > >

Aug. 15, 2015

Re: [Pharo-dev] Unified property API for code.

by Marcus Denker

> > > +1 for the propertyAt: / propertyAt:put: / > propertyAt:ifPresent:ifAbsent: etc... > > This is a easiest way, in my opinion, for a relation key/value. > > We should not touch Morph, but what about bloc ? Bloc seems to use the > same names as Morph. > Then we should fix Bloc. Marcus

Aug. 15, 2015

Re: [Pharo-dev] Unified property API for code.

by Ferlicot D. Cyril

Le 15/08/2015 10:24, Marcus Denker a Ã©crit : > Hi, > > I am now adding a property API to Global/Class Variables and Instance Variables (aka Slots). > > When looking at the other property APIs, we have 4 different conventions: > > 1) CompiledMethod and Behavior: > > propertyValueAt: > > 2) RB AST Nodes: > propertyAt: > > 3) Ring: > annotationNamed: > > and (4) Morphic uses: > valueOfProperty: > > > I would like to unify 1-3 as this is all the same use case: attaching meta data to the > structural model. > > I propose to unify the API to the same as the RB AST: just #propertyAt:. Morphic we should > not touch... > > Marcus > +1 for the propertyAt: / propertyAt:put: / propertyAt:ifPresent:ifAbsent: etc... This is a easiest way, in my opinion, for a relation key/value. We should not touch Morph, but what about bloc ? Bloc seems to use the same names as Morph. -- Cyril

Aug. 15, 2015

Re: [Pharo-dev] we are running dependencies breaking sprints....

by Alexandre Bergel

Yes! Thanks! This is valuable Alexandre > Le 15 aoÃ»t 2015 Ã 05:53, Tudor Girba <tudor(a)tudorgirba.com> a Ã©crit : > > This is exciting. Thanks a lot for this effort! > > Doru > >> On Sat, Aug 15, 2015 at 10:50 AM, stepharo <stepharo(a)free.fr> wrote: >> Hi guys >> >> just to let you know that we run a dependencies breaking sprint yesterday and it was great. >> We will redo one or two. >> Our goal is to minimise the dependencies of adding Monticello to the pharo bootstrap. >> What I can tell you is that having a bootstrap is bringing an ***AMAZING*** level of cleaner design. >> I suspected it. But when we see the real cases this is obvious and really important. >> I will really open a complete new world for Pharo in terms of modularity (of course it will take time >> but this is really really cool). >> >> Stef > > > > -- > www.tudorgirba.com > > "Every thing has its own flow"

Aug. 15, 2015

Re: [Pharo-dev] we are running dependencies breaking sprints....

by stepharo

I forgot to mention that people can help since we added a tahe pharo-bootstrap. Stef Le 15/8/15 10:53, Tudor Girba a Ã©crit : > This is exciting. Thanks a lot for this effort! > > Doru > > On Sat, Aug 15, 2015 at 10:50 AM, stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>> wrote: > > Hi guys > > just to let you know that we run a dependencies breaking sprint > yesterday and it was great. > We will redo one or two. > Our goal is to minimise the dependencies of adding Monticello to > the pharo bootstrap. > What I can tell you is that having a bootstrap is bringing an > ***AMAZING*** level of cleaner design. > I suspected it. But when we see the real cases this is obvious and > really important. > I will really open a complete new world for Pharo in terms of > modularity (of course it will take time > but this is really really cool). > > Stef > > > > > -- > www.tudorgirba.com <http://www.tudorgirba.com> > > "Every thing has its own flow"

Aug. 15, 2015

Re: [Pharo-dev] we are running dependencies breaking sprints....

by Dimitris Chloupis

yeap this is extremely important in making pharo far more flexible. It would be great if one day making custom images is just a few clicks away. Image fitting to the exact needs of its users instead of trying to cram everything into a single image. On Sat, Aug 15, 2015 at 11:50 AM stepharo <stepharo(a)free.fr> wrote: > Hi guys > > just to let you know that we run a dependencies breaking sprint > yesterday and it was great. > We will redo one or two. > Our goal is to minimise the dependencies of adding Monticello to the > pharo bootstrap. > What I can tell you is that having a bootstrap is bringing an > ***AMAZING*** level of cleaner design. > I suspected it. But when we see the real cases this is obvious and > really important. > I will really open a complete new world for Pharo in terms of modularity > (of course it will take time > but this is really really cool). > > Stef > >

Aug. 15, 2015

Re: [Pharo-dev] we are running dependencies breaking sprints....

by Thierry Goubier

Le 15/08/2015 10:50, stepharo a Ã©crit : > Hi guys > > just to let you know that we run a dependencies breaking sprint > yesterday and it was great. > We will redo one or two. > Our goal is to minimise the dependencies of adding Monticello to the > pharo bootstrap. > What I can tell you is that having a bootstrap is bringing an > ***AMAZING*** level of cleaner design. > I suspected it. But when we see the real cases this is obvious and > really important. > I will really open a complete new world for Pharo in terms of modularity > (of course it will take time > but this is really really cool). Yes! Thierry > Stef > >

Aug. 15, 2015

Re: [Pharo-dev] we are running dependencies breaking sprints....

by phil＠highoctane.be

Boostrapping is removing a ton of black magic indeed. There will be not one Pharo but the Pharo one needs for a given purpose. That's awesome. Phil Le 15 aoÃ»t 2015 10:50, "stepharo" <stepharo(a)free.fr> a Ã©crit : > Hi guys > > just to let you know that we run a dependencies breaking sprint yesterday > and it was great. > We will redo one or two. > Our goal is to minimise the dependencies of adding Monticello to the pharo > bootstrap. > What I can tell you is that having a bootstrap is bringing an > ***AMAZING*** level of cleaner design. > I suspected it. But when we see the real cases this is obvious and really > important. > I will really open a complete new world for Pharo in terms of modularity > (of course it will take time > but this is really really cool). > > Stef > >

Aug. 15, 2015

Re: [Pharo-dev] we are running dependencies breaking sprints....

by Ben Coman

On Sat, Aug 15, 2015 at 4:50 PM, stepharo <stepharo(a)free.fr> wrote: > Hi guys > > just to let you know that we run a dependencies breaking sprint yesterday > and it was great. We will redo one or two. > Our goal is to minimise the dependencies of adding Monticello to the pharo > bootstrap. What I can tell you is that having a bootstrap is bringing > an ***AMAZING*** level of cleaner design. I suspected it. But when we > see the real cases this is obvious and really important. > I will really open a complete new world for Pharo in terms of modularity (of > course it will take time but this is really really cool). > > Stef > Sounds like food for an academic paper - addressing one of the key complaints from detractors about Smalltalk. While you want to position Pharo as going beyond Smalltalk, reproducibility of an Image remains an argument available to detractors. cheers -ben

Aug. 15, 2015