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

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

by Tudor Girba

Hi Alain, I do not need it at this point. The Glamour code is fixed and relies on the default behavior of PluggableTextMorph. But, I was simply remarking that you have an instance variable to specify the styler per instance, but there is no way to set it. So, yes, I think it would be a good idea to add the styler: method back :). Cheers, Doru On 19 Oct 2011, at 09:15, Alain Plantec wrote: > Hi all, > If I understand well, Doru just need a PluggableTextMorph>>#styler: so that a specific styler can be directly set to an instance. > We can simply add this missing method if this is the point. > Cheers > Alain > > On 19/10/2011 09:03, StÃ©phane Ducasse wrote: >> On Oct 19, 2011, at 8:38 AM, Tudor Girba wrote: >> >>> 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. >> I do not think but I may be wrong. Have a look at the examples of Alain. >> >> Since there was not documentation at all we (ben and me) did some mistakes and passed as idiot (as usual) >> because we were so stupid not to understand the design of the code that we do not know. >> This change got waves in editor and that led lukas to complain. >> >> So yes documentation, classes comments is a way to make us doing less mistakes and feeling less utterly stupid and frustrated. >> But people do not get it because this is so cool to code for one self and look so smart. >> >> >> Stef >> > > -- www.tudorgirba.com "Next time you see your life passing by, say 'hi' and get to know her."

Oct. 19, 2011

Re: [Pharo-project] Website RSS feed broken?

by Max Leske

I'm looking into it. Max On 18.10.2011, at 16:48, Damien Cassou wrote: > On Tue, Oct 18, 2011 at 4:47 PM, Stefan Marr <pharo(a)stefan-marr.de> wrote: >> Same issue as before: Google Reader shows old entries as new. > > I confirm the problem > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Lambdas are relegated to relative obscurity until Java makes them > popular by not having them." James Iry >

Oct. 19, 2011

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

by Alain Plantec

Hi all, If I understand well, Doru just need a PluggableTextMorph>>#styler: so that a specific styler can be directly set to an instance. We can simply add this missing method if this is the point. Cheers Alain On 19/10/2011 09:03, StÃ©phane Ducasse wrote: > On Oct 19, 2011, at 8:38 AM, Tudor Girba wrote: > >> 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. > I do not think but I may be wrong. Have a look at the examples of Alain. > > Since there was not documentation at all we (ben and me) did some mistakes and passed as idiot (as usual) > because we were so stupid not to understand the design of the code that we do not know. > This change got waves in editor and that led lukas to complain. > > So yes documentation, classes comments is a way to make us doing less mistakes and feeling less utterly stupid and frustrated. > But people do not get it because this is so cool to code for one self and look so smart. > > > Stef >

Oct. 19, 2011

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

by Marcus Denker

On Oct 19, 2011, at 8:55 AM, StÃ©phane Ducasse wrote: > - Bug fixing > - Reviewing solutions that people proposed > - Integration of KeyMapper. > Yes. One goal would be to look at http://code.google.com/p/pharo/issues/list the number "423" is the enemy. It needs to be made smaller. For that, one needs to look at issues and decide: "Do we need to take action at all?" "What is that next action?" The next action is often very trivial. "code needs to be attached in a machine readable form". or "it seems there is a consensus. What is is? What do we need to *do*? Just deciding that we do *not* act on a reported issue is as valuable as integrating a fix. And even *far* more harder often. Marcus -- Marcus Denker -- http://marcusdenker.de

Oct. 19, 2011

[Pharo-project] wanna be a cool contributor?

by StÃ©phane Ducasse

Hi guys I'm quite sure that you all want to be a cool contributor? So do not forget to sign the license: http://www.pharo-project.org/license Then send a picture for http://www.pharo-project.org/community/contributors this is because we have a vibrant and active community that INRIA put money on the table. Stef

Oct. 19, 2011

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

by StÃ©phane Ducasse

On Oct 19, 2011, at 8:49 AM, Marcus Denker wrote: > > 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...) 80k even worse > > Marcus > > > -- > Marcus Denker -- http://marcusdenker.de > >

Oct. 19, 2011

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

by StÃ©phane Ducasse

On Oct 19, 2011, at 8:38 AM, Tudor Girba wrote: > 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. I do not think but I may be wrong. Have a look at the examples of Alain. Since there was not documentation at all we (ben and me) did some mistakes and passed as idiot (as usual) because we were so stupid not to understand the design of the code that we do not know. This change got waves in editor and that led lukas to complain. So yes documentation, classes comments is a way to make us doing less mistakes and feeling less utterly stupid and frustrated. But people do not get it because this is so cool to code for one self and look so smart. Stef > > 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 StÃ©phane Ducasse

On Oct 19, 2011, at 12:19 AM, Lukas Renggli wrote: > > > 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. I merged all your changes (rename of classes) during the last sprint and updated it the configuration the last sprint. We still want to use RBEngine to perform refactoring on remote images so we will start modify the version that we have in Pharo to handle that and we will maintain this version and merge your changes in. Stef

Oct. 19, 2011

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

by StÃ©phane Ducasse

Thanks lukas Here is the latest version where we explain metacello. I changed a lot and I should continue I'm half way there. The idea is that the last two pages should contain a summary of everything. So that we can write a config in a glance. Stef On Oct 19, 2011, at 12:03 AM, Dale Henrichs 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)? > > > 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. 19, 2011

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

by StÃ©phane Ducasse

- Bug fixing - Reviewing solutions that people proposed - Integration of KeyMapper. Stef On Oct 18, 2011, at 11:25 PM, Guillermo Polito wrote: > Is any desired task to focus on? Some people have asked here, so I move the discussion here. > > Guille

Oct. 19, 2011