- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] ZeroConf scripts download progress

by Esteban Lorenzano

On 11 Jun 2014, at 10:54, Max Leske <maxleske(a)gmail.com> wrote: > > On 11.06.2014, at 15:45, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > >> >> On 11 Jun 2014, at 10:41, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: >> >>> Can the zeroconf download of the image and/or vm display a progress? >>> >>> It is... remove the --silent and --quiet arguments from curl and wget >>> respectively :) >>> >>> Thank you! >> >> mmmâ¦ I do not think so, since zeroconf scripts are intended to automated scenarios (like jenkins builds, etc.) > > We could default to silent and give the user the option to turn off the silence with a -v flagâ¦ how? (thinking on "curl get.pharo.org | bashâ usage) > >> >>> >>> Esteban A. Maringolo >>> >> >> > >

June 11, 2014

Re: [Pharo-dev] ZeroConf scripts download progress

by Max Leske

On 11.06.2014, at 15:45, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > On 11 Jun 2014, at 10:41, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > >> Can the zeroconf download of the image and/or vm display a progress? >> >> It is... remove the --silent and --quiet arguments from curl and wget >> respectively :) >> >> Thank you! > > mmmâ¦ I do not think so, since zeroconf scripts are intended to automated scenarios (like jenkins builds, etc.) We could default to silent and give the user the option to turn off the silence with a -v flag... > >> >> Esteban A. Maringolo >> > >

June 11, 2014

Re: [Pharo-dev] ZeroConf scripts download progress

by Esteban Lorenzano

On 11 Jun 2014, at 10:41, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > Can the zeroconf download of the image and/or vm display a progress? > > It is... remove the --silent and --quiet arguments from curl and wget > respectively :) > > Thank you! mmmâ¦ I do not think so, since zeroconf scripts are intended to automated scenarios (like jenkins builds, etc.) > > Esteban A. Maringolo >

June 11, 2014

ZeroConf scripts download progress

by Esteban A. Maringolo

Can the zeroconf download of the image and/or vm display a progress? It is... remove the --silent and --quiet arguments from curl and wget respectively :) Thank you! Esteban A. Maringolo

June 11, 2014

Re: [Pharo-dev] news from block :)

by FranÃ§ois Stephany

What is bloc ? I've searched in the pharo-dev list but couldn't find it :/ On Wed, Jun 11, 2014 at 2:26 PM, stepharo <stepharo(a)free.fr> wrote: > looks so exciting... > > From: Alain Plantec <alain.plantec(a)univ-brest.fr> > Subject: Bloc news > Date: 11 Jun 2014 14:10:29 GMT+2 > To: StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > Cc: Alain Plantec <alain.plantec(a)univ-brest.fr> > > Name: Bloc-Core-AlainPlantec.15 > Author: AlainPlantec > Time: 11 June 2014, 2:07:16.813171 pm > UUID: d58ae82e-b5dd-41d9-bc31-a48c3e9e5cf1 > Ancestors: Bloc-Core-AlainPlantec.14 > > - BlMorphs manage their submorphs with local coordinate. > - Drawing and drag&drop has been adapted to local coordinate > - Consequence: TransformationMorph should not be useful anymore because > each morph has its own transform (not only TransformationMorph). Each morph > uses its own transform to declare changed portions of its bounds and to > draw its submorphs. > - The world is no more a special morph: > - the hand is owned by the space > - the canvas and the display/redisplay of morphs are space > responsibilities. > This open the door to several worlds per space. > > Now the current global redrawing mechanism efficiency is not obvious. > Next actions: > - try to localize as much as possible the redrawing of morphs, > - dig several Worlds for a space > - start to comment and write a separate documentation with the help of > Stephane :) > > >

June 11, 2014

Re: [Pharo-dev] [issue tracker] back porting 4 to 3

by Marcus Denker

On 11 Jun 2014, at 14:59, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Marcus Denker-4 wrote >> When there are issues that people wan to have back ported... > > We should save this procedure in a more permanent place... > > Indeedâ¦ I will put it somewhere. > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/issue-tracker-back-porting-4-to-3-tp4762606p4762613.h… > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

June 11, 2014

Re: [Pharo-dev] [issue tracker] back porting 4 to 3

by Sean P. DeNigris

Marcus Denker-4 wrote > When there are issues that people wan to have back ported... We should save this procedure in a more permanent place... ----- Cheers, Sean -- View this message in context: http://forum.world.st/issue-tracker-back-porting-4-to-3-tp4762606p4762613.h… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

June 11, 2014

news from block :)

by stepharo

looks so exciting... From: Alain Plantec <alain.plantec(a)univ-brest.fr> Subject: Bloc news Date: 11 Jun 2014 14:10:29 GMT+2 To: StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> Cc: Alain Plantec <alain.plantec(a)univ-brest.fr> Name: Bloc-Core-AlainPlantec.15 Author: AlainPlantec Time: 11 June 2014, 2:07:16.813171 pm UUID: d58ae82e-b5dd-41d9-bc31-a48c3e9e5cf1 Ancestors: Bloc-Core-AlainPlantec.14 - BlMorphs manage their submorphs with local coordinate. - Drawing and drag&drop has been adapted to local coordinate - Consequence: TransformationMorph should not be useful anymore because each morph has its own transform (not only TransformationMorph). Each morph uses its own transform to declare changed portions of its bounds and to draw its submorphs. - The world is no more a special morph: - the hand is owned by the space - the canvas and the display/redisplay of morphs are space responsibilities. This open the door to several worlds per space. Now the current global redrawing mechanism efficiency is not obvious. Next actions: - try to localize as much as possible the redrawing of morphs, - dig several Worlds for a space - start to comment and write a separate documentation with the help of Stephane :)

June 11, 2014

Re: [Pharo-dev] [issue tracker] back porting 4 to 3

by Ben Coman

Marcus Denker wrote: > Hi, > > When there are issues that people wan to have back ported, the easiest (which worked very nicely last year) is this: > > 1) add the âback portâ issue as the *parent* of the main issue tracker entry. > 2) make sure to do a slice early, itâs very easy to do when it is not yet integrated in Pharo4 (by looking at the diff). > > > Issue 13494: Backport Pharo3 Issue 13494: some fixe > â> Issue 13494: some fix > > > Then first the slice will be validated on Pharo4, then it will get integrated there. After that, the Issue for Pharo3 will get validate > by the monkey, and the is ready integration. > > This makes sure that fixes are put to use and validated in Pharo4 before we even think about adding them to the stable release. > > Marcus > > nice idea

June 11, 2014

[issue tracker] back porting 4 to 3

by Marcus Denker

Hi, When there are issues that people wan to have back ported, the easiest (which worked very nicely last year) is this: 1) add the âback portâ issue as the *parent* of the main issue tracker entry. 2) make sure to do a slice early, itâs very easy to do when it is not yet integrated in Pharo4 (by looking at the diff). Issue 13494: Backport Pharo3 Issue 13494: some fixe â> Issue 13494: some fix Then first the slice will be validated on Pharo4, then it will get integrated there. After that, the Issue for Pharo3 will get validate by the monkey, and the is ready integration. This makes sure that fixes are put to use and validated in Pharo4 before we even think about adding them to the stable release. Marcus

June 11, 2014