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

[Pharo-project] Download choices :) or :(?

by DougEdmunds

Pretend you are a newbie and want to try Pharo. You get on the http://www.pharo-project.org page 1. Top right image says "Download Pharo" That downloads immediately from https://gforge.inria.fr/frs/download.php/28437/Pharo-1.2.1-OneClick.zip 2. But in the left column You can click on the heading "Download" Now you go to http://www.pharo-project.org/pharo-download which gives you two different one-click choices, but without any explanation of the difference between Cog VM and standard VM. 2A. And if you look down further on that page, there are lots of 'custom' choices, one of which is a Windows Installer, apparently of the most recent version, but that one says it uses the unexplained 'Cog' vm. 3. Wait!! On the home page, you can assume that the latest release is 1.2.1 in the left column, and this takes you to http://www.pharo-project.org/pharo-download/release-1-2-1 which now give you 3 choices to download, one of which is a one-click, but is it Cog or is it Standard? 4. Wait again!! On the home page, under Shortcuts on 'Stable Pharo' which immediately starts to download yet another version: currently Pharo-1.2.1-11.04.03.zip 5. And now you feel obligated to click the words 'Download Pharo' on the right column of the home page, thinking there may be even more versions to pick from. It takes you to another page. Deja Vu, it looks familiar.... So, newbie, was that clear enough for you? -- View this message in context: http://forum.world.st/Download-choices-or-tp3440405p3440405.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

April 10, 2011

Re: [Pharo-project] Issue 3960 in pharo: Catch all: Remove experimental + ancient backward compatibility code

by pharo＠googlecode.com

Comment #5 on issue 3960 by marcus.d...(a)gmail.com: Catch all: Remove experimental + ancient backward compatibility code http://code.google.com/p/pharo/issues/detail?id=3960 DeprecateCompat.1.cs -> move all methods that send deprecated: to Deprecated13 package -> clean up some old cruft Attachments: DeprecateCompat.1.cs 29.3 KB

April 10, 2011

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

by ZeBourk

Congratulations Laurent! And thank you for having given me the motivation to dive into smalltalk. Now I have introduced it in the company I work for, and it's really fun. I wish you success, too. Thierry 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

Re: [Pharo-project] [Vm-dev] Debugging Cog crash

by Schwab,Wilhelm K

Eliot, I modified the one-click's shell script as shown below and ran it from a terminal. It still says only "Segmentation fault." I could be doing this incorrectly or maybe not looking in the correct place for the output??? My first attempt was to add -sendTrace=9 (note case), and it complained, which is vastly better than ignoring my mistake; it also suggests that I got -sendtrace=9 correct, or it would presumably complain again. Did I botch it, or is it really quitting before it reaches Smalltalk code? If you suspect the latter, is there something else we can do to prove it, and/or what's next? I am not opposed to building from source. I avoided it for a while because I was afraid that I would "hack" the vm again and not really fix my FFI oddities. I am close to having the latter sorted, and can probably now trust myself with vm source :) Bill #!/bin/sh # path ROOT=`dirname $0` LINUX="$ROOT/Contents/Linux" RESOURCES="$ROOT/Contents/Resources" # icon gvfs-set-attribute \ "$0" \ "metadata::custom-icon" \ "file://$RESOURCES/Squeak.png" \ 2> /dev/null # execute exec "$LINUX/squeakvm" \ -sendtrace=9 \ -plugins "$LINUX" \ -encoding latin1 \ -vm-display-X11 \ "$RESOURCES/Pharo.image"

April 10, 2011

Re: [Pharo-project] Issue 3981 in pharo: #<= on SourcedMethodReference is very slow

by pharo＠googlecode.com

Updates: Cc: johanbri...(a)me.com Benjamin...(a)gmail.com Comment #1 on issue 3981 by marianopeck: #<= on SourcedMethodReference is very slow http://code.google.com/p/pharo/issues/detail?id=3981 (No comment was entered for this change.)

April 10, 2011

Re: [Pharo-project] Issue 3960 in pharo: Catch all: Remove experimental + ancient backward compatibility code

by pharo＠googlecode.com

Comment #4 on issue 3960 by marcus.d...(a)gmail.com: Catch all: Remove experimental + ancient backward compatibility code http://code.google.com/p/pharo/issues/detail?id=3960 remove #hInitScrollBarTEMPORARY in Scrollpane Attachments: Scrollpane.1.cs 669 bytes

April 10, 2011

[Pharo-project] Issue 3981 in pharo: #<= on SourcedMethodReference is very slow

by pharo＠googlecode.com

Status: Accepted Owner: marcus.d...(a)gmail.com New issue 3981 by marcus.d...(a)gmail.com: #<= on SourcedMethodReference is very slow http://code.google.com/p/pharo/issues/detail?id=3981 ... as it accesses the sources. (it slows down rendering "senders of" a lot. And there I wonder why we sort them for time at all?)

April 10, 2011

Re: [Pharo-project] Issue 3980 in pharo: TestResource fails to makeAvailable an never recovers

by pharo＠googlecode.com

Updates: Status: FixProposed Comment #1 on issue 3980 by guillerm...(a)gmail.com: TestResource fails to makeAvailable an never recovers http://code.google.com/p/pharo/issues/detail?id=3980 current should be assigned to nil, not to false. fix proposed in the inbox Name: SLICE-Issue-3980-TestResource-fails-to-makeAvailable-an-never-recovers-GuillermoPolito.1 Author: GuillermoPolito Time: 10 April 2011, 9:31:08 pm UUID: 8959ec71-7ade-47e0-bc26-d0d32d4075c7 Ancestors: Dependencies: SUnit-GuillermoPolito.40123 current initialized to nil in makeAvailable

April 10, 2011

Re: [Pharo-project] TestResource bug?

by Guillermo Polito

Yep, thanks for the response! Issue 3980 <http://code.google.com/p/pharo/issues/detail?id=3980>: TestResource fails to makeAvailable an never recovers On Sun, Apr 10, 2011 at 6:42 PM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > > 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

[Pharo-project] Issue 3980 in pharo: TestResource fails to makeAvailable an never recovers

by pharo＠googlecode.com

Status: Accepted Owner: guillerm...(a)gmail.com New issue 3980 by guillerm...(a)gmail.com: TestResource fails to makeAvailable an never recovers http://code.google.com/p/pharo/issues/detail?id=3980 Using Pharo 1.2 TestResource>>makeAvailable "This method must be the _only_ way to set a notNil value for the unique instance (current). First, obtain a candidate instance and set current to a notNil placeholder (any notNil object not an instance of me would do; this version uses false). Next, check any subordinate resources needed by this resource. Lastly, setUp the candidate and put it in current if it is available, ensuring that it is torn down otherwise." | candidate | current := false. candidate := self new. .... And everywhere in the class, the check over the current var is done like current isNil ifTrue: .... So once that var is initialized, but the makeAvailable fails, it always fails...

April 10, 2011