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

[Pharo-project] Fwd: Actions done in 1.3
by Igor Stasenko April 6, 2011

April 6, 2011

---------- Forwarded message ---------- From: Igor Stasenko <siguctua(a)gmail.com> Date: 6 April 2011 13:55 Subject: Re: [Pharo-project] Actions done in 1.3 To: laurent laffont <laurent.laffont(a)gmail.com> On 6 April 2011 10:30, laurent laffont <laurent.laffont(a)gmail.com> wrote: > > On Wed, Apr 6, 2011 at 10:17 AM, Igor Stasenko <siguctua(a)gmail.com> wrote: >> >> Planning is also important. >> >> Time is good, but another thing is i think we should think about, >> what features we want to be in new release, and do not release until >> they delivered. > > I don't really like this. I prefer rhythm, agility. Timeboxing enables > maximum value in each release. If a feature is really important, it will be > on time. If not on time, it means it was no so important. > Always green test is a must-have. > >> >> Besides bug fixing and minor improvements, there should be some >> functionality which we want to have in new release, > > That should be a goal, but don't delay a release because the feature is not > here. If releases are often ( for example every 3 months), shorter, it won't > be a big problem to wait for the next one. > I prefer to have a release *now* without my feature and wait 3 months for > the next release than no release and waiting for 3 months more with less and > less energy. > But you don't have to wait, if you want to stay on bleeding edge, you know how to do that. Just go to hudson and dowload freshly built 1.3 image. Because if you can pick any image at any moment and declare it new release, then i don't understand why do we need releases at all? What makes release to be release , when you can download latest version at any moment? That's why i saying that from release to release cleanup and fixes is good, but there should be some major functional changes, which worth to be labeled as a new version. And if you don't have them, then there is no point to make a release. > Laurent. > -- Best regards, Igor Stasenko AKA sig. -- Best regards, Igor Stasenko AKA sig.

2 1

[Pharo-project] [COTDC] 42 - ExpanderMorphContracted
by laurent laffont April 6, 2011

April 6, 2011

Today: ExpanderMorphContracted Comment Of The Day Contest - One Day One Comment Rules: #1: Each day a not commented class is elected. Each day the best comment will be integrated with name of the author(s). #2: If you cannot comment it, deprecate it. Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest Laurent

2 2

[Pharo-project] ConfigurationOfSoapOpera in 1.2 broken
by laurent laffont April 6, 2011

April 6, 2011

Hi, I would like to use SOAP in Pharo. I've seen there's ConfigurationOfSoapOpera but it's broken. I've fixed deprecations of XMLSupport. But now it searches for a XMLWriter which no longer exists it seems. Someone use SOAP here ? Laurent Laffont - @lolgzs <http://twitter.com/#!/lolgzs> Pharo Smalltalk Screencasts: http://www.pharocasts.com/ Blog: http://magaloma.blogspot.com/ Developer group: http://cara74.seasidehosting.st

1 0

Re: [Pharo-project] Draft Pharo 1.2.1 Release Announcement
by Marcus Denker April 5, 2011

April 5, 2011

On Apr 5, 2011, at 10:28 PM, Adrian Lienhard wrote: > Thanks, Sven! > > I've put the page online > - as a blog entry on the news page: http://www.pharo-project.org/news > - the release page: http://www.pharo-project.org/pharo-download/release-1-2-1 > > (I've slightly edited some of the bullet point items to fit on one line) > > Thanks Laurent for the translation. I've linked to the wiki page you created. > > As far as I see there's one thing missing on the website: the download sticker for the one click image (top right on the page) still points to 1.1.1. I'll try to change the sticker and link tomorrow morning. > > Regarding the one click image, on the download page we linked to 1.1.1 with and without COG. Do we still have this distinction? > Yes. 1.2 is the last release with Cog / nonCog. (we need to use and test using cog... e.g. hudson needs to use cog. This is planed for 1.3) Therefore, this is not correct: Pharo 1.2.1 One-Click is the easiest to get started: it includes all needed components (image, change and source file as well as a fast, compatible Cog VM) in one package that requires no installation the linked image does not use Cog. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

3 3

Re: [Pharo-project] Remove #class as a Compiler optimization
by Marcus Denker April 5, 2011

April 5, 2011

On Apr 5, 2011, at 12:32 PM, Mariano Martinez Peck wrote: > > > On Tue, Apr 5, 2011 at 12:09 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > On 5 April 2011 11:33, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > > So....I tried with running all tests of a PharoCore 1.3 and I've got this: > > > > cog vm with optimization > > Time to run all tests:116506 > > > > cog vm without optimization > > Time to run all tests:121930 > > > > 121930 - 116506 ----> 5424 > > ((5424 * 100) / 116506) asFloat ---> 4.655554220383499 > > > > So...in Cog, running all test, there is an overhead of 4.6% > > > > Do we want to pay it ? > > > > I would...but I am all ears. > > > 5% for #class message? > this is too much. or you also removed other optimized sends? > > > Only that one. For #== I got 4.3. And doing both together (#class and #==) I got 9.05% :( > > And removing the #class optimization in a Interpreter VM gives me almost as in cog: 4.7% > > maybe I am doing something wrong... > can you try in 1.2? We did some compiler changes that are not yet fully done.... e.g. Issue 3940: BlockNode has undeclared ivar optimizedMessageNode -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

8 15

Re: [Pharo-project] [Pharo-users] Last pending things for Pharo 1.2
by Marcus Denker April 5, 2011

April 5, 2011

On Apr 4, 2011, at 5:05 PM, Mariano Martinez Peck wrote: > > > On Sat, Mar 12, 2011 at 8:19 PM, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > So....here is the list of things I guess are pending: > In general, for all pending things adding entries in the bug tracker is the only way ti make sure they are not forgotten. > 1) "Release" all configurations included in Pharo (this is, ConfigurationOfPharo and all it dependencies). I mean, we should NOT use or depend on #development versions. > > so...can someone check this is done? GUillermo and me did it once...but it seems a lot of stuff was updated once again I just gave up and took the image yesterday. Like you did for 1.1: Just build it once, don't care that it is repeatable. > > 2) Update the one click image to use latest cog images and "pharo prepared vms". There are some issues regarding this... > > Marcus, which is the status of this one ? I updated the one-click image with the last cog VM. For the one-click, it is identical to 1.1 with the only change that I put the windows VM I got from Torsten. > > 3) Write down all the things/summary done in Pharo 1.2 > > consider as done in nobody else comes with something better, > > 5) Update SystemVersion current -->> Pharo1.2rc2 of 27 January 2011 update 12340 > > > SystemVersion current ->> Pharo1.2.1 of 2 April 2011 update 12345 > > so..it is ok, isn't it ? can we forget this item ? > > 6) Condense sources? condense changes? #cleanUpForRelease > > Marcus, is that necessary ? > > DEVImageCreator >> cleanUps > > ScriptLoader new cleanUpForRelease. > "In Pharo 1.1 condenseChanges is VERY slow because of the new method trailers. So condensingChanges each time even when it is not needed is not a good idea anymore. So in case a condenseChanges is needed it should be done explicitly. > Smalltalk condenseChanges." > Smalltalk garbageCollect. > > I did that and I put that comment. Now that they are faster and that we have Hudson, should I put back the Smalltalk condenseChanges ? is there anything else needed? do we need a condenseSources ? > CondenseChange and CondenseSource is broken right now. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

3 2

Re: [Pharo-project] [Pharo-users] Last pending things for Pharo 1.2
by Marcus Denker April 5, 2011

April 5, 2011

On Apr 5, 2011, at 11:06 PM, Mariano Martinez Peck wrote: > > I just gave up and took the image yesterday. Like you did for 1.1: Just build it once, don't care that it is repeatable. > > Sorry, I didn't understand. The Pharo 1.1 was repeatable (in the same core) since all the Metacello versions were frozen. > In 1.2 seemingly not, it changes by the phase of the moon what is loaded. Yes... someone needs to look at that. Somone needed to look at that for months. At the same time, 1.3 does not even had a build *ever*. > >> >> 2) Update the one click image to use latest cog images and "pharo prepared vms". There are some issues regarding this... >> > >> Marcus, which is the status of this one ? > > I updated the one-click image with the last cog VM. > > For the one-click, it is identical to 1.1 with the only change that I put the windows VM I got from Torsten. > > > But 1.1 was not-Cog (Cog 1.1.1 was cog). So...we are shipping the Pharo One Click 1.2 with the Interpreter VM instead of Cog ? > or did you mean 1.1.1 ? if so, it would be good to update to latest Cog. The cog version used for 1.1.1 had several problems (I think the run:with:in: crashes the image -> TestCoverage) > I updated the cog One-Click to the latest Cog vm released last week. Yes, we need to have everthing build by Hudson automatically... but on the other hand, we need to release and not postpone forever. We had 3 Months to fix everything, we did not, we would not fix in another 3 months. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

[Pharo-project] Issue 3831 in pharo: 1.2 full image workspace has description on how to load O2
by pharo＠googlecode.com April 5, 2011

April 5, 2011

Status: Accepted Owner: marcus.d...(a)gmail.com Labels: Milestone-1.2-DevImage New issue 3831 by marcus.d...(a)gmail.com: 1.2 full image workspace has description on how to load O2 http://code.google.com/p/pharo/issues/detail?id=3831 ... but O2 does not work in 1.2 So we should remove the description.

1 6

Re: [Pharo-project] Draft Pharo 1.2.1 Release Announcement
by Marcus Denker April 5, 2011

April 5, 2011

On Apr 5, 2011, at 10:21 PM, Casimiro de Almeida Barreto wrote: > I suggest some corrections at: "DEVImageWorkspaces > openExternalProjectWorkspace". > > O2 does not install according to instructions and installing it other > ways result in error. > Aida has pending dependencies (Swazoo, I guess because Seaside installs > Swazoo2) > etc. > I removed the O2 description!!!!! I removed it, waited for Hudson to build the release, downloaded, checked, and it was gone. There is even a tracker entry: http://code.google.com/p/pharo/issues/detail?id=3831 So now why in the world is it there now? I think we should really find someone else for managing the Full image build scripts. I am definitly to dumb to get anything to work. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

2 1

April 5, 2011

Hi guys to help us in the future I started http://code.google.com/p/pharo/wiki/ActionsInPharoOneDotThree The list starts to get long... Stef

1 0