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

Re: [Pharo-dev] Updating ZeroConf! Please do not use it until new advice!

by Thierry Goubier

Hi Esteban, the links to the effectives VMs and images behind the scripts haven't changed? Thierry Le 07/04/2015 17:24, Esteban Lorenzano a Ã©crit : > okâ¦ success :) > now, this is the change: > > from now, each version is married with one vm. > > so, if you download /30+vm it will download the Pharo30 image with its corresponding "vm30" > > which means some links do not have sense anymore: > > /vm > /vmLatest > > but you have > > /vm12 > ... > /vm20 > /vm30 > /vm40 > /vmLatest40 > > the concept of âlatest vmâ is also now married to development imageâ¦ while an image is being developed (40 now, 50 next week), it will have a âlatestâ vmâ¦ but once releases, release will come with a âblessedâ vmâ¦ the one is good for you to use. > > of course, that does not means vmâs are not exchangeable, as usualâ¦ it means we are blessing one version of the vm to be used with one version of the image. > > Now, the vm will download just ONE source version (vm30 will download PharoV3.sources)â¦ so we can keep many version without bloating our downloads. > > Also, this prepares us to future non compatible VM versions (like Spur), so is a good change. > > I hope it is clear for you :) > > cheers, > Esteban > > > >> On 07 Apr 2015, at 16:56, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> >> Ok, retrying. DO NOT USE THEM! >> >> Esteban >> >>> On 07 Apr 2015, at 16:20, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>> >>> ok, you can use it now. Update failed and I need to leave for half na hourâ¦. I will retry later. >>> >>> cheers, >>> Esteban >>> >>>> On 07 Apr 2015, at 16:03, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>>> >>>> thatâ¦ we need to change it :P >>> >> > > > >

April 7, 2015

Re: [Pharo-dev] [Pharo-users] Updating ZeroConf! Please do not use it until new advice!

by Sven Van Caekenberghe

Good work, thanks. > On 07 Apr 2015, at 17:24, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > okâ¦ success :) > now, this is the change: > > from now, each version is married with one vm. > > so, if you download /30+vm it will download the Pharo30 image with its corresponding "vm30" > > which means some links do not have sense anymore: > > /vm > /vmLatest > > but you have > > /vm12 > ... > /vm20 > /vm30 > /vm40 > /vmLatest40 > > the concept of âlatest vmâ is also now married to development imageâ¦ while an image is being developed (40 now, 50 next week), it will have a âlatestâ vmâ¦ but once releases, release will come with a âblessedâ vmâ¦ the one is good for you to use. > > of course, that does not means vmâs are not exchangeable, as usualâ¦ it means we are blessing one version of the vm to be used with one version of the image. > > Now, the vm will download just ONE source version (vm30 will download PharoV3.sources)â¦ so we can keep many version without bloating our downloads. > > Also, this prepares us to future non compatible VM versions (like Spur), so is a good change. > > I hope it is clear for you :) > > cheers, > Esteban > > > >> On 07 Apr 2015, at 16:56, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> >> Ok, retrying. DO NOT USE THEM! >> >> Esteban >> >>> On 07 Apr 2015, at 16:20, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>> >>> ok, you can use it now. Update failed and I need to leave for half na hourâ¦. I will retry later. >>> >>> cheers, >>> Esteban >>> >>>> On 07 Apr 2015, at 16:03, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>>> >>>> thatâ¦ we need to change it :P >>> >> > >

April 7, 2015

Re: [Pharo-dev] modifying ASTs

by Thierry Goubier

Le 07/04/2015 17:47, Yuriy Tymchuk a Ã©crit : > One more question. How do I get the new source string? Because if I > use #sourceCode I get old code, if I use #printString it also puts > extra parenthesis. #formattedCode Thierry > Uko > >> On 07 Apr 2015, at 17:39, Thierry Goubier >> <thierry.goubier(a)gmail.com> wrote: >> >> Le 07/04/2015 17:24, Marcus Denker a Ã©crit : >>> >>>> On 07 Apr 2015, at 17:20, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> >>>> wrote: >>>> >>>> Hi, I need to change source code of a method by for example >>>> adding a pragma. Can I just manipulate itâs AST without >>>> carrying about source code anchors? Because it seems that I >>>> have to set from/to values and it looks painful. >>>> >>> >>> I would do the change, print the code and recompile itâ¦ not nice, >>> but for now the easiest. >> >> I conccur with Marcus. It's good enough; RB works this way. >> >> Note that you can change the AST without bothering with the from/to >> stuff, in most cases (except syntax errors messages?). >> >>> (this way they old AST gets garbage collected and the new one has >>> all the offsets into the text correct). >> >> It's a lot easier than trying to shift the offsets depending on >> what you have added/not added. >> >>> I would like to explore if we canât build a system where >>> everything we manipulate is ASTsâ¦ >> >> You're the compiler guy: everything is an AST :) >> >> Thierry >> > > > >

April 7, 2015

Re: [Pharo-dev] modifying ASTs

by Yuriy Tymchuk

One more question. How do I get the new source string? Because if I use #sourceCode I get old code, if I use #printString it also puts extra parenthesis. Uko > On 07 Apr 2015, at 17:39, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > > Le 07/04/2015 17:24, Marcus Denker a Ã©crit : >> >>> On 07 Apr 2015, at 17:20, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: >>> >>> Hi, I need to change source code of a method by for example adding a pragma. Can I just manipulate itâs AST without carrying about source code anchors? Because it seems that I have to set from/to values and it looks painful. >>> >> >> I would do the change, print the code and recompile itâ¦ not nice, but for now the easiest. > > I conccur with Marcus. It's good enough; RB works this way. > > Note that you can change the AST without bothering with the from/to stuff, in most cases (except syntax errors messages?). > >> (this way they old AST gets garbage collected and the new one has all the offsets into the text correct). > > It's a lot easier than trying to shift the offsets depending on what you have added/not added. > >> I would like to explore if we canât build a system where everything we manipulate is ASTsâ¦ > > You're the compiler guy: everything is an AST :) > > Thierry >

April 7, 2015

Re: [Pharo-dev] modifying ASTs

by Thierry Goubier

Le 07/04/2015 17:24, Marcus Denker a Ã©crit : > >> On 07 Apr 2015, at 17:20, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: >> >> Hi, I need to change source code of a method by for example adding a pragma. Can I just manipulate itâs AST without carrying about source code anchors? Because it seems that I have to set from/to values and it looks painful. >> > > I would do the change, print the code and recompile itâ¦ not nice, but for now the easiest. I conccur with Marcus. It's good enough; RB works this way. Note that you can change the AST without bothering with the from/to stuff, in most cases (except syntax errors messages?). > (this way they old AST gets garbage collected and the new one has all the offsets into the text correct). It's a lot easier than trying to shift the offsets depending on what you have added/not added. > I would like to explore if we canât build a system where everything we manipulate is ASTsâ¦ You're the compiler guy: everything is an AST :) Thierry

April 7, 2015

Re: [Pharo-dev] Updating ZeroConf! Please do not use it until new advice!

by Esteban Lorenzano

okâ¦ success :) now, this is the change: from now, each version is married with one vm. so, if you download /30+vm it will download the Pharo30 image with its corresponding "vm30" which means some links do not have sense anymore: /vm /vmLatest but you have /vm12 ... /vm20 /vm30 /vm40 /vmLatest40 the concept of âlatest vmâ is also now married to development imageâ¦ while an image is being developed (40 now, 50 next week), it will have a âlatestâ vmâ¦ but once releases, release will come with a âblessedâ vmâ¦ the one is good for you to use. of course, that does not means vmâs are not exchangeable, as usualâ¦ it means we are blessing one version of the vm to be used with one version of the image. Now, the vm will download just ONE source version (vm30 will download PharoV3.sources)â¦ so we can keep many version without bloating our downloads. Also, this prepares us to future non compatible VM versions (like Spur), so is a good change. I hope it is clear for you :) cheers, Esteban > On 07 Apr 2015, at 16:56, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > Ok, retrying. DO NOT USE THEM! > > Esteban > >> On 07 Apr 2015, at 16:20, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> >> ok, you can use it now. Update failed and I need to leave for half na hourâ¦. I will retry later. >> >> cheers, >> Esteban >> >>> On 07 Apr 2015, at 16:03, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>> >>> thatâ¦ we need to change it :P >> >

April 7, 2015

Re: [Pharo-dev] modifying ASTs

by Marcus Denker

> On 07 Apr 2015, at 17:20, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > > Hi, I need to change source code of a method by for example adding a pragma. Can I just manipulate itâs AST without carrying about source code anchors? Because it seems that I have to set from/to values and it looks painful. > I would do the change, print the code and recompile itâ¦ not nice, but for now the easiest. (this way they old AST gets garbage collected and the new one has all the offsets into the text correct). I would like to explore if we canât build a system where everything we manipulate is ASTsâ¦ Marcus

April 7, 2015

modifying ASTs

by Yuriy Tymchuk

Hi, I need to change source code of a method by for example adding a pragma. Can I just manipulate itâs AST without carrying about source code anchors? Because it seems that I have to set from/to values and it looks painful. Uko

April 7, 2015

Re: [Pharo-dev] Contributing to Bloc

by kilon alios

thats understanable and reasonable. I am impressed with how well it emulates Morphic so far. On Tue, Apr 7, 2015 at 5:50 PM, Alain Plantec via Pharo-dev < pharo-dev(a)lists.pharo.org> wrote: > > > ---------- Forwarded message ---------- > From: Alain Plantec <alain.plantec(a)yahoo.com> > To: Pharo Development List <pharo-dev(a)lists.pharo.org> > Cc: > Date: Tue, 7 Apr 2015 16:49:38 +0200 > Subject: Re: [Pharo-dev] Contributing to Bloc > Hello, > > in fact you are running morphic widget inside bloc. The compatibility is > not 100%. > I guess here the problem is related to the global coordinate system of > Morphic. > We will try to fix it. > Thanks for reporting. > Cheers > Alain > > > On 06 Apr 2015, at 13:56, kilon alios <kilon.alios(a)gmail.com> wrote: > > another weird problem i just found is that right side down arrow menu when > clicked it opens in random location instead of bellow its icon. I tried it > with System Browser. > > By the way i am talking about already available Pharo tools and not bloc > examples. > > On Mon, Apr 6, 2015 at 2:03 PM, Nicolai Hess <nicolaihess(a)web.de> wrote: > >> 2015-04-06 10:22 GMT+02:00 kilon alios <kilon.alios(a)gmail.com>: >> >>> Hey guys, these last days I have taken a look at Bloc and really like >>> its design. So I was wondering how I can be of assistance. I am not an >>> experienced pharo jedi like you guys but I think I could do my small part >>> to help make Bloc into a replacement for Morphic. >>> >>> From what I see Bloc some issues rendering Morphs , for example tabs >>> (window groups) and some glitches here and there. >>> >> >> >> I don't know a tabs example that is build with bloc. >> The current bloc world renders a classic Morph on an AthensCanvas if they >> define a >> #drawOnAthensCanvas: method. >> If this is missing or not correctly working, we should change the >> implementation in the Athens project (Athens-Morphic). >> >> >> >> >>> >>> So how am I proceed ? How I can help ? >>> >> >> > > >

April 7, 2015

Re: [Pharo-dev] Contributing to Bloc

by kilon alios

No problem waiting for an answer. Ok then I will keep using it and reporting problems I find. Documenting is something I can do too, I am familiar with pillar , so I will send some pull requests when I get a good understanding of Bloc. Contributing examples is something I can do too, will wait for the move of bloc to a public repo I can contribute too including comments. For now I will stress tests and report and then when I am familiar enough move to other tasks. On Tue, Apr 7, 2015 at 6:01 PM, Alain Plantec via Pharo-dev < pharo-dev(a)lists.pharo.org> wrote: > > > ---------- Forwarded message ---------- > From: Alain Plantec <alain.plantec(a)yahoo.com> > To: Pharo Development List <pharo-dev(a)lists.pharo.org> > Cc: > Date: Tue, 7 Apr 2015 17:00:30 +0200 > Subject: Re: [Pharo-dev] Contributing to Bloc > > > So how am I proceed ? How I can help ? > > > sorry for the late answer, Iâm very busy â¦. > but thanks !! > for now I think the most important is to document bloc and to stress it > - by trying the examples or > - by trying to program new examples or > - by adding comments, fix the english or by asking questions. > Cheers > Alain > > > >

April 7, 2015