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

[Pharo-project] A question about UIManager

by StÃ©phane Ducasse

Hi pharoers I was trying to change MenuMorph direct reference to use UIManager because I was thinking that a popup menu should not open alone but this is the responsibility of the UIManager and I was not happy. why because we have these UIManager default and I started to think about them (ok I'm dead nearly sleeping at 9 in the evening because I took too much sun and walk today). My gut feeling is that at least for UI code, any UI element could have an access to the current UIManager via an instance variable or a message. self uiManager. Now may be the UI World should point to the UIMAnager and each graphical element should access it like that. For non UI class then this is a different story. But I would like to get your point of view on that point. Tx stef

April 10, 2011

[Pharo-project] [BlogPost] Building the VM from scratch using Git and CMakeVMMaker

by Mariano Martinez Peck

Hi folks. This post took me a lot of time, so at least I will try to share it: http://marianopeck.wordpress.com/2011/04/10/building-the-vm-from-scratch-us… Hopefully it is useful for you. Any kind of feedback is more than welcome. Cheers -- Mariano http://marianopeck.wordpress.com

April 10, 2011

Re: [Pharo-project] Issue 3931 in pharo: Move all Exceptions-Kernel to Kernel-Exceptions

by pharo＠googlecode.com

Updates: Status: FixProposed Comment #1 on issue 3931 by marcus.d...(a)gmail.com: Move all Exceptions-Kernel to Kernel-Exceptions http://code.google.com/p/pharo/issues/detail?id=3931 cs attached Attachments: Exceptions.1.cs 1.8 KB

April 10, 2011

Re: [Pharo-project] TestResource bug?

by Marcus Denker

On Apr 9, 2011, at 5:40 PM, Guillermo Polito wrote: > Hi! I'm using pharo 1.2 and I've found a little problem in here > > TestResource>>makeAvailable > ... > Is this a bug or i'm doing a mistake? Shouldn't current := false be changed be changed by current := nil. ?? > Yes, I think you are right... can you add a bugreport? -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

April 10, 2011

Re: [Pharo-project] Have started an independent developer activity - Thank you

by Vanessa PeÃ±a

Congratulations and best luck! Thank you so much for sharing :) Cheers, Vanessa. On Sat, Apr 9, 2011 at 4:34 AM, laurent laffont <laurent.laffont(a)gmail.com>wrote: > Hi, > > I discovered Smalltalk and Pharo almost three years ago and just after read > Chad Fowler book "Passionate Programmer" (1st edition title was "My job went > to India"). These have changed my developer life, how I perceive software > and that great technology is fun, people doing it more. You're a cool > community and I'm proud to be there. > > Now I've started an aside (paid :) independent developer activity thanks to > a cool guy. That would not be possible without all the stuff I learn every > day from the community and the urge to continue you give me. > > Each time I've made a step forward (open a blog, write ProfStef, fix bugs, > create PharoCasts) I've been amazed that the generated effects were those > described in Passionate Programmer (go read it !) The last chapter is "Go > independent" so now I need the sequel ;) > > Special big thank you to StÃ©phane Ducasse - you're crazy :) Long live Pharo > ! > > > PS: nice piece of Passionate Programmer: > > When I was in India weeding through hundreds of candidates for only > tens of jobs, the interview team was exhausting itself and running out > of time because of a poor interview-to-hire hit rate. Heads hurting and > eyes red, we held a late-night meeting to discuss a strategic change in the > way we would go through the candidates. We had to either optimize the > process so we could interview more people or somehow interview better > people (or both). With what little was left of my voice after twelve > straight > hours of trying to drag answers out of dumbstruck programmers, I argued > for adding Smalltalk to the list of keywords our headhunters were using > to search their rÃ©sumÃ© database. But, nobody knows Smalltalk in India, > cried > the human resources director. That was my point. Nobody knew it, and > programming in Smalltalk was a fundamentally different experience than > programming in Java. The varying experience would give candidates a > different level of expectations, and the dynamic nature of the Smalltalk > environment would reshape the way a Java programmer would approach > a problem. My hope was that these factors would encourage a level of > technical maturity that I hadnât been seeing from the candidates Iâd met so > far. > The addition of Smalltalk to the requirements list yielded a candidate pool > that was tiny in contrast to our previous list. These people were diamonds > in the rough. They really understood object-oriented programming. They > were aware that Java isnât the idealistic panacea itâs sometimes made out > to be. Many of them loved to program! Where have you been for the past two > weeks? we thought. > Unfortunately, our ability to attract these developers for the salaries we > were able to pay was limited. They were calling the shots, and most of > them chose to stay where they were or to keep looking for a new job. > Though we failed to recruit many of them, we learned a valuable recruit- > ing lesson: we were more likely to extend offers to candidates with diverse > (and even unorthodox) experience than to those whose experiences were > homogenous. My explanation is that either the good people seek out > diversity, because they love to learn new things, or being forced into > alien > experiences and environments created more mature, well-rounded soft- > ware developers. I suspect itâs a little of both, but regardless of why it > works, we learned that it works. I still use this technique when looking > for developers. > > > Laurent Laffont - @lolgzs <http://twitter.com/#%21/lolgzs> > > Pharo Smalltalk Screencasts: http://www.pharocasts.com/ > Blog: http://magaloma.blogspot.com/ > Developer group: http://cara74.seasidehosting.st > > >

April 10, 2011

Re: [Pharo-project] Issue 3958 in pharo: Remove embedded snapshotting (image level)

by pharo＠googlecode.com

Updates: Status: Closed Comment #2 on issue 3958 by marcus.d...(a)gmail.com: Remove embedded snapshotting (image level) http://code.google.com/p/pharo/issues/detail?id=3958 in 13139

April 10, 2011

[Pharo-project] [update 1.3] #13139

by Marcus Denker

13139 ----- Issue 3979: Fixing an undeclare ref in ScriptLoader Issue 3941: Paragraph (deprecated) has lots of refs to undefined temps Issue 3958: Remove embedded snapshotting (image level) -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

April 10, 2011

Re: [Pharo-project] Issue 3941 in pharo: Paragraph (deprecated) has lots of refs to undefined temps

by pharo＠googlecode.com

Updates: Status: Closed Comment #2 on issue 3941 by marcus.d...(a)gmail.com: Paragraph (deprecated) has lots of refs to undefined temps http://code.google.com/p/pharo/issues/detail?id=3941 in 13139

April 10, 2011

Re: [Pharo-project] Issue 3979 in pharo: Fixing an undeclare ref in ScriptLoader

by pharo＠googlecode.com

Updates: Status: Closed Comment #1 on issue 3979 by marcus.d...(a)gmail.com: Fixing an undeclare ref in ScriptLoader http://code.google.com/p/pharo/issues/detail?id=3979 in 13139

April 10, 2011

Re: [Pharo-project] Have started an independent developer activity - Thank you

by GermÃ¡n Arduino

Excellent Laurent! Best of luck to the new company! 2011/4/9 laurent laffont <laurent.laffont(a)gmail.com>: > Hi, > I discovered Smalltalk and Pharo almost three years ago and just after read > Chad Fowler book "Passionate Programmer" (1st edition title was "My job went > to India"). These have changed my developer life, how I perceive software > and that great technology is fun, people doing it more. You're a cool > community and I'm proud to be there. > Now I've started an aside (paid :) independent developer activity thanks to > a cool guy. That would not be possible without all the stuff I learn every > day from the community and the urge to continue you give me. > Each time I've made a step forward (open a blog, write ProfStef, fix bugs, > create PharoCasts) I've been amazed that the generated effects were those > described in Passionate Programmer (go read it !) The last chapter is "Go > independent" so now I need the sequel ;) > Special big thank you to StÃ©phane Ducasse - you're crazy :)Â Long live Pharo > ! > > PS: nice piece of Passionate Programmer: > When I was in India weeding through hundreds of candidates for only > tens of jobs, the interview team was exhausting itself and running out > of time because of a poor interview-to-hire hit rate. Heads hurting and > eyes red, we held a late-night meeting to discuss a strategic change in the > way we would go through the candidates. We had to either optimize the > process so we could interview more people or somehow interview better > people (or both). With what little was left of my voice after twelve > straight > hours of trying to drag answers out of dumbstruck programmers, I argued > for adding Smalltalk to the list of keywords our headhunters were using > to search their rÃ©sumÃ© database. But, nobody knows Smalltalk in India, cried > the human resources director. That was my point. Nobody knew it, and > programming in Smalltalk was a fundamentally different experience than > programming in Java. The varying experience would give candidates a > different level of expectations, and the dynamic nature of the Smalltalk > environment would reshape the way a Java programmer would approach > a problem. My hope was that these factors would encourage a level of > technical maturity that I hadnât been seeing from the candidates Iâd met so > far. > The addition of Smalltalk to the requirements list yielded a candidate pool > that was tiny in contrast to our previous list. These people were diamonds > in the rough. They really understood object-oriented programming. They > were aware that Java isnât the idealistic panacea itâs sometimes made out > to be. Many of them loved to program! Where have you been for the past two > weeks? we thought. > Unfortunately, our ability to attract these developers for the salaries we > were able to pay was limited. They were calling the shots, and most of > them chose to stay where they were or to keep looking for a new job. > Though we failed to recruit many of them, we learned a valuable recruit- > ing lesson: we were more likely to extend offers to candidates with diverse > (and even unorthodox) experience than to those whose experiences were > homogenous. My explanation is that either the good people seek out > diversity, because they love to learn new things, or being forced into alien > experiences and environments created more mature, well-rounded soft- > ware developers. I suspect itâs a little of both, but regardless of why it > works, we learned that it works. I still use this technique when looking > for developers. > > Laurent Laffont -Â @lolgzs > > Pharo Smalltalk Screencasts:Â http://www.pharocasts.com/ > Blog:Â http://magaloma.blogspot.com/ > Developer group:Â http://cara74.seasidehosting.st > >

April 10, 2011