- Pharo-dev - lists.pharo.org

Re: [Pharo-project] fonts on Pharo website

by Max Leske

They're good to read in Safari on MacOS but I must say I found myself wondering if I had accidentally set strange preferences to narrow the fonts :) It's just... I'm not used to seeing such a font on the web.... On 11.04.2011, at 13:47, laurent laffont wrote: > Hi, > > For me the new fonts used on www.pharo-project.org are hard to read. The rendering on Firefox / Windows is not nice too. > > What do you think ? > > Laurent Laffont

April 11, 2011

Re: [Pharo-project] Issue 3987 in pharo: Use specific KeyNotFoundError in Dictionaries

by pharo＠googlecode.com

Updates: Status: FixProposed Labels: Milestone-1.3 Comment #1 on issue 3987 by marcus.d...(a)gmail.com: Use specific KeyNotFoundError in Dictionaries http://code.google.com/p/pharo/issues/detail?id=3987 (No comment was entered for this change.)

April 11, 2011

[Pharo-project] Issue 3987 in pharo: Use specific KeyNotFoundError in Dictionaries

by pharo＠googlecode.com

Status: New Owner: ---- New issue 3987 by camillob...(a)gmail.com: Use specific KeyNotFoundError in Dictionaries http://code.google.com/p/pharo/issues/detail?id=3987 Pharo Inbox: Polymorph-Widgets-CamilloBruni.423 Collections-Unordered-CamilloBruni.108

April 11, 2011

[Pharo-project] fonts on Pharo website

by laurent laffont

Hi, For me the new fonts used on www.pharo-project.org are hard to read. The rendering on Firefox / Windows is not nice too. What do you think ? Laurent Laffont

April 11, 2011

[Pharo-project] Fwd: [Metacello] [ANN] MetacelloBrowser 1.59.1 ready for feedback

by Alexandre Bergel

DÃ©but du message transfÃ©rÃ© : > ExpÃ©diteur: Dale Henrichs <dhenrich(a)vmware.com> > Date: 11 avril 2011 00:54:01 UTC-04:00 > Destinataire: "metacello(a)googlegroups.com" <metacello(a)googlegroups.com> > Objet: [Metacello] [ANN] MetacelloBrowser 1.59.1 ready for feedback > RÃ©pondre Ã : metacello(a)googlegroups.com > > I've been using the MetacelloBrowser pretty heavily in my day to day development and I feel that it has reached a relatively stable point in terms of reliability and functionality, so now is a good time to get feedback from a wider audience of users. > > The MetacelloBrowser pretty much supports the development cycle as described in my blog post[1], with menu items or buttons to support the major operations. For the most part you shouldn't have to open the Monticello Browser when using the Metacello Browser ... if you find you have to use it let us know:). To submit bug reports, visit [2] and set the Product label to Product-Browser. > > Please use the 'documentation' menu item in the configuration list to look at the help text for a configuration (Metacello and MetacelloBrowser entries have been customized) and let me know what you think. > > The 'Load Configuration' button should let you load a configuration and then you can use the browser to load a specific version. > > There are still times when you have to 'browse' a configuration or version to had edit things, but over time I hope that we can build ui's for doing that as well. > > Press the 'Help' button to take a look at the Help available and feel free to suggest improvements. > > When you load the MetacelloBrowser, you'll get version 1.0-beta.29 of Metacello which is still under development ...there are a number of performance improvements and bugfixes in 1.0-beta.29 along with the Configuration Help System entries so don't forget to open a Help Browser and look at the 'Metacello Configruations' topic (related to the MetacelloBrowser 'documentation' menu item). > > To load do the following: > > Gofer new > squeaksource: 'MetacelloBrowser'; > package: 'ConfigurationOfMetacelloBrowser'; > load. > > then: > > (ConfigurationOfMetacelloBrowser project version: #stable) load. > > then either: > > MetacelloBrowser open. > > or > > MBOBConfigurationBrowser open. > > In Pharo, the MetacelloBrowser shows up in the Tools menu. > > I expect the MetacelloBrowser to work in: > > - Pharo1.1 and Pharo1.2 (OB or Morphic) > - Squeak 4.2 (OB) > - GLASS 1.0-beta.8.7 (OB) > > The MetacelloBrowser is still a work in progress, but your feedback now will make it possible for Alexandre and I to focus on the things that need to be addressed before we can announce general availability. > > Dale > > [1] http://gemstonesoup.wordpress.com/#walkthrough > [2] http://code.google.com/p/metacello/issues/entry

April 11, 2011

[Pharo-project] [update 1.3] #13140

by Marcus Denker

13140 ----- Issue 3977: Undeclared vars in MorphTreeMorp Issue 3931: Move all Exceptions-Kernel to Kernel-Exceptions -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

April 11, 2011

[Pharo-project] Fwd: Company using Pharo [was: Have started an independent developer activity]

by laurent laffont

Thanks Thierry ! ---------- Forwarded message ---------- From: Gmail perso <zebourk(a)gmail.com> Date: Mon, Apr 11, 2011 at 10:38 AM Subject: Re: [Pharo-project] Have started an independent developer activity - Thank you To: laurent laffont <laurent.laffont(a)gmail.com> Of course! You can add Alsim (http://ww.alsim.com/) to the list of company using Pharo. For the details, we are still in early stage of adoption, but it is really promising. As the best way to learn is to practice, we have started the development of a tool for our stock management, as the model is quite simple. The aim is to learn, and to validate some concepts too, like the use of a web interface. So we use: * Pharo * Seaside for the web part * Magma for the data persistence. For the moment, it is still in early stage of development, but it is growing quite fast. I think I will be able to give you more feed back soon. -- Thierry On lundi 11 avril 2011 at 09:52, laurent laffont wrote: 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] Issue 3931 in pharo: Move all Exceptions-Kernel to Kernel-Exceptions

by pharo＠googlecode.com

Updates: Status: Closed Labels: Milestone-1.3 Comment #2 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 in 13140

April 11, 2011

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

by pharo＠googlecode.com

Updates: Status: Closed Comment #4 on issue 3977 by marcus.d...(a)gmail.com: Undeclared vars in MorphTreeMorph http://code.google.com/p/pharo/issues/detail?id=3977 in 13140

April 11, 2011

Re: [Pharo-project] Issue 3986 in pharo: Bug with Delay during clock rollover

by pharo＠googlecode.com

Comment #1 on issue 3986 by gazzagu...(a)googlemail.com: Bug with Delay during clock rollover http://code.google.com/p/pharo/issues/detail?id=3986 (file attached, failed first time!) Attachments: DelayRolloverFix.1.cs 1.3 KB

April 11, 2011