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

[Pharo-project] GitFS and Pharogenesis

by Max Leske

Hi folks I promised a while ago that I would keep you up to date with GitFS and Pharogenesis. Well, now that I've handed in my thesis you can read it if you like: http://scg.unibe.ch/archive/projects/Lesk11a.pdf I also wrote a short How-To on Filesystem (alas, the "old" version) and GitFS: http://scg.unibe.ch/archive/projects/Lesk11b.pdf You can find a summary of important information (loading the code etc.) on this page: http://scg.unibe.ch/research/Pharogenesis Although I'm sort of "releasing" the code for both now, please note that Pharo has progressed a bit too fast lately for me to keep up. GitFS was built on the original implementation of Filesystem and I will have to put some work into updating the implementation. I'm even thinking of starting over from scratch. Pharogenesis also depends on the old version of Filesystem. The Metacello configurations load the old Filesystem version into the image, just so you know. If you don't know what this is all about, here's the abstract of my thesis: In the Smalltalk dialects Squeak and Pharo it is difficult to view changes to source code that occurred accross major releases. This poses a problem for development as well as for code analysis: Developers often need to be able to revert code to a previous version and for code analysis there should ideally be a single source of information. We solve the problem by building a Git repository with the complete source code history of Pharo. To build the repository we propose two tools: GitFS and Pharogenesis. GitFS is an implementation of Git written entirely in Smalltalk. With GitFS we can create, read and manipulate Git repositories. Pharogenesis uses GitFS to build a Git repository from the source code that Pharogenesis extracts from the source files. We also show how Git can be used to provide a single point of access for all source code from Squeak 1 through Squeak 4 and Pharo 1 using GitFS. The source code database we built with Pharogenesis is available on github (http://www.github. com/pharogenesis/pharogenesis.git). If you have any questions, feel free to ask. Cheers, Max

April 11, 2011

[Pharo-project] Issue 3984 in pharo: Announcements announced when a test is runned

by pharo＠googlecode.com

Status: FixProposed Owner: Benjamin...(a)gmail.com Labels: Milestone-1.3 Nautilus New issue 3984 by Benjamin...(a)gmail.com: Announcements announced when a test is runned http://code.google.com/p/pharo/issues/detail?id=3984 More precisely, when the history of the test case is updated Attachments: AnnouncementsInTestCase.1.cs 2.8 KB

April 11, 2011

[Pharo-project] Issue 3983 in pharo: TestCase assertions are in accessing protocol

by pharo＠googlecode.com

Status: Accepted Owner: laurent....(a)gmail.com Labels: Type-RequestForEnhancement Difficulty-Easy New issue 3983 by laurent....(a)gmail.com: TestCase assertions are in accessing protocol http://code.google.com/p/pharo/issues/detail?id=3983 Pharo 1.2 & 1.3 Put them in asserting protocol like TestAsserter

April 11, 2011

Re: [Pharo-project] Issue 3977 in pharo: Undeclared vars in MorphTreeMorph

by pharo＠googlecode.com

Updates: Status: FixProposed Comment #3 on issue 3977 by Benjamin...(a)gmail.com: Undeclared vars in MorphTreeMorph http://code.google.com/p/pharo/issues/detail?id=3977 It should fix the issue :) Attachments: MorphTreeMorph.BenjaminVanRyseghem.1.cs 5.5 KB

April 11, 2011

Re: [Pharo-project] FAQ migration

by Max Leske

Yeah, should probably better contain the TOC to the FAQ entries. Max On 11.04.2011, at 09:40, Adrian Lienhard wrote: > > On Apr 10, 2011, at 13:16 , Mariano Martinez Peck wrote: > >> Thanks Max, I am reading it now :) >> For those who doesn't know the link: http://book.pharo-project.org/book/FAQ/ > > Hm, this page is pretty empty... > > Adrian > > BTW, there's another FAQ, which I had written over some time: http://www.pharo-project.org/documentation/faq. Does it make sense to keep both (a technical and a non-technical FAQ)? Or should we merge this one also into the book? > >

April 11, 2011

Re: [Pharo-project] Issue 3977 in pharo: Undeclared vars in MorphTreeMorph

by pharo＠googlecode.com

Comment #2 on issue 3977 by Benjamin...(a)gmail.com: Undeclared vars in MorphTreeMorph http://code.google.com/p/pharo/issues/detail?id=3977 I think it's a fix based on an out dated version because the Issue 3955introduce those variables ... The problem comes from the fix Issue 3969 attachment: TreePart2.cs (8.0 KB) :) Those fixes should be merged using a clean image ^^

April 11, 2011

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

by laurent laffont

On Sun, Apr 10, 2011 at 10:01 PM, ZeBourk <zebourk(a)gmail.com> wrote: > 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. > Cool ! Can we add it to http://www.pharo-project.org/about/success-stories ? Laurent > > 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 11, 2011

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

by Adrian Lienhard

On Apr 11, 2011, at 04:43 , Serge Stinckwich wrote: > There should be i guess just one download page. > On the first page, there is some downloads links in the three columns. > If you look at the python language website, there is only one download > page, the same for Ruby. Yep! > Adrian take care of the website if i remember. I know from experience > this a really boring task. > If we want to scale to a small team of volunteers, what could be done > to simplify the modification of pages ? > I know that the website currently used is based on Cmsbox and this is > great showcase for Pharo&Smalltalk, but > maybe an automatically generated html website with the help of tools > like webgen or something similar with the pages on a git repository > somewhere could help the management. I don't think we have a tool issue here. We already have several people that help with managing the website and that works pretty well. I think the confusion about what to download can be addressed by providing less options. Maybe we just have too many of them... The initial idea was that in particular newcomers would just download the one-click image. In the meantime we got a one-click image with and without COG. Then people asked for direct shortcuts on the home page for the stable core, the unstable core, and the stable full image. Of course this makes everything very complicated for people who don't know what they want/need. So we should think again about what images we want to provide for download and how to link them. Cheers, Adrian

April 11, 2011

Re: [Pharo-project] FAQ migration

by Adrian Lienhard

On Apr 10, 2011, at 13:16 , Mariano Martinez Peck wrote: > Thanks Max, I am reading it now :) > For those who doesn't know the link: http://book.pharo-project.org/book/FAQ/ Hm, this page is pretty empty... Adrian BTW, there's another FAQ, which I had written over some time: http://www.pharo-project.org/documentation/faq. Does it make sense to keep both (a technical and a non-technical FAQ)? Or should we merge this one also into the book?

April 11, 2011

Re: [Pharo-project] [SPAM] Nice post about files ....

by Sven Van Caekenberghe

On 11 Apr 2011, at 08:57, Geert Claes wrote: > http://gbracha.blogspot.com/2010/02/nail-files.html Indeed, it's very well put.

April 11, 2011