October 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] IS Smalltalk Source also an object?

by Marcus Denker

On Oct 18, 2011, at 9:31 PM, Nicolas Cellier wrote: > 2011/10/18 Schwab,Wilhelm K <bschwab(a)anest.ufl.edu>: >> Maybe I've played too much football without a helmet or did too much C programming, > > Yes, and yes, that's why you missed Eliot's answer ;) > http://permalink.gmane.org/gmane.comp.lang.smalltalk.pharo.devel/55024 > > Nicolas > > > but I see two questions popping out of this: (1) is source an object > in Smalltalk; So yes, I have been convinced that it is an object (as even a string is an object). (yet, we should think if with the resources we have today as opposed to 1978, can't we do even better? I always wonder how smalltalk would look like if they would have had 4GB of RAM instead of 256KB...) Marcus -- Marcus Denker -- http://marcusdenker.de

Oct. 19, 2011

Re: [Pharo-project] Can this be improved in Glamourous?

by Tudor Girba

Hi, Thanks. It is fixed now by removing the explicit setting of a styler. However, I do not quite understand why not being able to set the styler on a per PluggableTextMorph instance basis is a good idea. You still have an instance variable for the styler, but you do not have the possibility to set it from the outside. You can only change the styler for the entire image by changing the StylingClass class variable. Cheers, Doru On 18 Oct 2011, at 21:37, StÃ©phane Ducasse wrote: > Probably that the GLMMorphicSmalltalkCodeRenderer rely on the old (and buggy way we used to use the styler) > and doru may have to look at the shoutexample package to see how to invoke shout. > > Stef > >> Hi guys. So...now that ConfigurationOfGrease seem to work (in latest 1.3 from Hudson), I can load: >> >> (ConfigurationOfGlamoroust project version: #development) load: #('GT-Inspector' 'GT-Playground' ). >> >> However, if I evaluate: >> GTInspector openOn: 'mariano' >> >> I have the attached PharoDebug.log >> >> Basically, in GLMMorphicSmalltalkCodeRenderer >> textMorphForModel: aTextModel >> >> morph >> styler: styler; >> >> morph DNU styler: . >> >> >> Thanks! >> >> On Mon, Oct 17, 2011 at 2:53 PM, <csrabak(a)bol.com.br> wrote: >> Em 16/10/2011 18:20, Marcus Denker < marcus.denker(a)inria.fr > escreveu: >>> Hello, >> >>> Can people in general *delete* the quoted email parts to a level >>> that one does need to scroll down 5 pages to read the answer? >> >> +1 >> >> It is really a must for us that want to keep with the volume of e-mails but have to be parsimonious on the time spent for it. >> >> -- >> Cesar Rabak >> >> >> >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> >> <PharoDebug.log> > > -- www.tudorgirba.com "Don't give to get. Just give."

Oct. 19, 2011

Re: [Pharo-project] ConfigurationOfGrease stable does not load in Pharo 1.3

by Lukas Renggli

On Wednesday, 19 October 2011, Lukas Renggli <renggli(a)gmail.com> wrote: > Ok, it is broken indeed: > > http://jenkins.lukas-renggli.ch/job/Seaside%203.0%20(Metacello)/3/console > > At starting point I use a normal Pharo 1.3, but with e tests unloaded. And it is because a too old version or a forked version of RB is loaded. Lukas > > On Wednesday, 19 October 2011, Dale Henrichs <dhenrich(a)vmware.com> wrote: >> Great! >> >> Yes...that's the one ...I've subscribe to the rss feed for the Metacello build (Looks like you kicked one off already) so I'll be able to respond to those issues... >> >> Presumably you'll trigger builds not only when the config changes, but when underlying platform changes as well? Or is it better to schedule it to build once a day (or when config changes)? > > I can observe a single directory per project. Should I trigger the build with changes to the Metacello repository? My machine cannot handle too many builds. It is old and very slow. > > Lukas > > >> >> >> Dale >> ----- Original Message ----- >> | From: "Lukas Renggli" <renggli(a)gmail.com> >> | To: Pharo-project(a)lists.gforge.inria.fr >> | Sent: Tuesday, October 18, 2011 2:44:58 PM >> | Subject: Re: [Pharo-project] ConfigurationOfGrease stable does not load in Pharo 1.3 >> | >> | > It would be useful if you used the ConfigurationOfSeaside30 and >> | > ConfigurationOfGrease in your continuous integration server for >> | > seaside. There have been a number of issues that would have been >> | > uncovered much earlier if you included the configurations in your >> | > tests ... >> | >> | I can do that. Which one? >> | >> | Gofer new >> | squeaksource: 'MetacelloRepository'; >> | package: 'ConfigurationOfSeaside30'; >> | load. >> | (Smalltalk at: #ConfigurationOfSeaside30) load. >> | >> | Lukas >> | >> | -- >> | Lukas Renggli >> | www.lukas-renggli.ch >> | >> | >> >> > > -- > Lukas Renggli > www.lukas-renggli.ch > -- Lukas Renggli www.lukas-renggli.ch

Oct. 18, 2011

Re: [Pharo-project] ConfigurationOfGrease stable does not load in Pharo 1.3

by Lukas Renggli

Ok, it is broken indeed: http://jenkins.lukas-renggli.ch/job/Seaside%203.0%20(Metacello)/3/console At starting point I use a normal Pharo 1.3, but with e tests unloaded. On Wednesday, 19 October 2011, Dale Henrichs <dhenrich(a)vmware.com> wrote: > Great! > > Yes...that's the one ...I've subscribe to the rss feed for the Metacello build (Looks like you kicked one off already) so I'll be able to respond to those issues... > > Presumably you'll trigger builds not only when the config changes, but when underlying platform changes as well? Or is it better to schedule it to build once a day (or when config changes)? I can observe a single directory per project. Should I trigger the build with changes to the Metacello repository? My machine cannot handle too many builds. It is old and very slow. Lukas > > > Dale > ----- Original Message ----- > | From: "Lukas Renggli" <renggli(a)gmail.com> > | To: Pharo-project(a)lists.gforge.inria.fr > | Sent: Tuesday, October 18, 2011 2:44:58 PM > | Subject: Re: [Pharo-project] ConfigurationOfGrease stable does not load in Pharo 1.3 > | > | > It would be useful if you used the ConfigurationOfSeaside30 and > | > ConfigurationOfGrease in your continuous integration server for > | > seaside. There have been a number of issues that would have been > | > uncovered much earlier if you included the configurations in your > | > tests ... > | > | I can do that. Which one? > | > | Gofer new > | squeaksource: 'MetacelloRepository'; > | package: 'ConfigurationOfSeaside30'; > | load. > | (Smalltalk at: #ConfigurationOfSeaside30) load. > | > | Lukas > | > | -- > | Lukas Renggli > | www.lukas-renggli.ch > | > | > > -- Lukas Renggli www.lukas-renggli.ch

Oct. 18, 2011

Re: [Pharo-project] ConfigurationOfGrease stable does not load in Pharo 1.3

by Dale Henrichs

Great! Yes...that's the one ...I've subscribe to the rss feed for the Metacello build (Looks like you kicked one off already) so I'll be able to respond to those issues... Presumably you'll trigger builds not only when the config changes, but when underlying platform changes as well? Or is it better to schedule it to build once a day (or when config changes)? Dale ----- Original Message ----- | From: "Lukas Renggli" <renggli(a)gmail.com> | To: Pharo-project(a)lists.gforge.inria.fr | Sent: Tuesday, October 18, 2011 2:44:58 PM | Subject: Re: [Pharo-project] ConfigurationOfGrease stable does not load in Pharo 1.3 | | > It would be useful if you used the ConfigurationOfSeaside30 and | > ConfigurationOfGrease in your continuous integration server for | > seaside. There have been a number of issues that would have been | > uncovered much earlier if you included the configurations in your | > tests ... | | I can do that. Which one? | | Gofer new | squeaksource: 'MetacelloRepository'; | package: 'ConfigurationOfSeaside30'; | load. | (Smalltalk at: #ConfigurationOfSeaside30) load. | | Lukas | | -- | Lukas Renggli | www.lukas-renggli.ch | |

Oct. 18, 2011

Re: [Pharo-project] ConfigurationOfGrease stable does not load in Pharo 1.3

by Lukas Renggli

Done. http://jenkins.lukas-renggli.ch/job/Seaside%203.0%20(Metacello)/ On 18 October 2011 23:44, Lukas Renggli <renggli(a)gmail.com> wrote: >> It would be useful if you used the ConfigurationOfSeaside30 and ConfigurationOfGrease in your continuous integration server for seaside. There have been a number of issues that would have been uncovered much earlier if you included the configurations in your tests ... > > I can do that. Which one? > > Gofer new > Â Â squeaksource: 'MetacelloRepository'; > Â Â package: 'ConfigurationOfSeaside30'; > Â Â load. > (Smalltalk at: #ConfigurationOfSeaside30) load. > > Lukas > > -- > Lukas Renggli > www.lukas-renggli.ch > -- Lukas Renggli www.lukas-renggli.ch

Oct. 18, 2011

Re: [Pharo-project] ConfigurationOfGrease stable does not load in Pharo 1.3

by Lukas Renggli

> It would be useful if you used the ConfigurationOfSeaside30 and ConfigurationOfGrease in your continuous integration server for seaside. There have been a number of issues that would have been uncovered much earlier if you included the configurations in your tests ... I can do that. Which one? Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfSeaside30'; load. (Smalltalk at: #ConfigurationOfSeaside30) load. Lukas -- Lukas Renggli www.lukas-renggli.ch

Oct. 18, 2011

[Pharo-project] About the pharo Sprint before the smalltalks

by Guillermo Polito

Is any desired task to focus on? Some people have asked here, so I move the discussion here. Guille

Oct. 18, 2011

Re: [Pharo-project] ConfigurationOfGrease stable does not load in Pharo 1.3

by Dale Henrichs

Lukas, The "fixed" configuration has new versions of nearly all of the grease packages committed by both you and Philippe. I haven't looked to see when the packages were committed, but they presumably were updated since the last release of Seaside/Grease which was a month ago. It would be useful if you used the ConfigurationOfSeaside30 and ConfigurationOfGrease in your continuous integration server for seaside. There have been a number of issues that would have been uncovered much earlier if you included the configurations in your tests ... In the past testing the configurations would have uncovered dependency issues that were masked by the fact that you don't test Grease independently of Seaside (or at least didn't at the time). This time around, the platform moved out from under the configuration... You'd only need to build one or two additional images using the configurations to completely test the Seaside eco-system ... as it stands now configuration problems are left for the end users to find and that's not correct. Dale ----- Original Message ----- | From: "Lukas Renggli" <renggli(a)gmail.com> | To: Pharo-project(a)lists.gforge.inria.fr | Sent: Tuesday, October 18, 2011 1:41:22 PM | Subject: Re: [Pharo-project] ConfigurationOfGrease stable does not load in Pharo 1.3 | | > Looking at the aftermath of this ConfigurationOfGrease issue, it | > appears that you and Philippe published a several new packages for | > Grease and those new packages were not included in the | > ConfigurationOfGrease that everyone else uses. | | Thank you for the offer to update the configurations, I really | appreciate that. | | Though, I am not aware of any changes in the past weeks and our | builds | work just fine. | | Lukas | | -- | Lukas Renggli | www.lukas-renggli.ch | |

Oct. 18, 2011

Re: [Pharo-project] ConfigurationOfGrease stable does not load in Pharo 1.3

by Lukas Renggli

> Looking at the aftermath of this ConfigurationOfGrease issue, it appears that you and Philippe published a several new packages for Grease and those new packages were not included in the ConfigurationOfGrease that everyone else uses. Thank you for the offer to update the configurations, I really appreciate that. Though, I am not aware of any changes in the past weeks and our builds work just fine. Lukas -- Lukas Renggli www.lukas-renggli.ch

Oct. 18, 2011