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

Re: [Pharo-project] Draft Pharo 1.2.1 Release Announcement

by Marcus Denker

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.

April 5, 2011

Re: [Pharo-project] Draft Pharo 1.2.1 Release Announcement

by Adrian Lienhard

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? Cheers, Adrian On Apr 5, 2011, at 21:15 , Sven Van Caekenberghe wrote: > OK, the board approved the draft, so here is the 1.2.1 release announcement: > > http://homepage.mac.com/svc/Pharo/pharo-1.2.1-release.html > > Adrian will put it on the website, next an official mail should be sent to the mailing lists. > > Then we should all try to spread the word! > > Even if it was a bit long winding in the end, this is a release to be proud of. > > Sven > >

April 5, 2011

Re: [Pharo-project] Draft Pharo 1.2.1 Release Announcement

by Marcus Denker

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.

April 5, 2011

Re: [Pharo-project] Draft Pharo 1.2.1 Release Announcement

by Casimiro de Almeida Barreto

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. Best regards, CdAB

April 5, 2011

Re: [Pharo-project] abouth nautilus and the removal of CodeHolder hierarchy

by Alain Plantec

Le 05/04/2011 20:57, StÃ©phane Ducasse a Ã©crit : > A new browser :) > Supporting > - groups > - package > - declarative menus > - environment selection > - scoped actions > - soon refactoring > > but right now a bit too slow because of the HUGGGGGGEEEEEE trees build by TreeMorphTreeMorph yes, maybe MorphTreeMorph is not the good tree to use here. why not use a simpler one ? Alain >> Squeaksource simply says "A new browser" >> >> Cheers, >> Alexandre > >

April 5, 2011

Re: [Pharo-project] abouth nautilus and the removal of CodeHolder hierarchy

by Michael Roberts

Hi, how does it relate to glamourost? thanks, Mike On Tue, Apr 5, 2011 at 7:57 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > > On Apr 5, 2011, at 5:31 PM, Alexandre Bergel wrote: > >> Hi Guys, >> >> Maybe I missed part of the discussion, but what is Nautilus? > > A new browser :) > Supporting > Â Â Â Â - groups > Â Â Â Â - package > Â Â Â Â - declarative menus > Â Â Â Â - environment selection > Â Â Â Â - scoped actions > Â Â Â Â - soon refactoring > > but right now a bit too slow because of the HUGGGGGGEEEEEE trees build by TreeMorphTreeMorph > >> Squeaksource simply says "A new browser" >> >> Cheers, >> Alexandre > > >

April 5, 2011

Re: [Pharo-project] A lil simplification of MorphTreeNodeMorph

by Alain Plantec

Le 05/04/2011 20:08, Igor Stasenko a Ã©crit : > Cut out some code and extra morphs. > It speeds up rendering to 60% of original. cool thanks for reviewing this code! > @Benjamin > Please verify if it positioning stuff correctly. Because in my image > Settings are now OK. > > @all > I need your feedback to know if it works correctly in other places, > where tree morph used. you need to remove all references to spacers inst var since it seems to be not used anymore now. another point, try all examples in Morphic-MorphTreeWidget-Examples. now, the height of each row is constant. It is because of the RowLayout that is used for MorphTreeNodeMorph instead of a ProportionalLayout. see ClassTreeExample before and after your changes. ClassTreeExample new openOn: Object cheers Alain

April 5, 2011

Re: [Pharo-project] Draft Pharo 1.2.1 Release Announcement

by laurent laffont

On Tue, Apr 5, 2011 at 9:15 PM, Sven Van Caekenberghe <sven(a)beta9.be> wrote: > OK, the board approved the draft, so here is the 1.2.1 release > announcement: > > http://homepage.mac.com/svc/Pharo/pharo-1.2.1-release.html > > Adrian will put it on the website, next an official mail should be sent to > the mailing lists. > > Then we should all try to spread the word! > > Even if it was a bit long winding in the end, this is a release to be proud > of. > French translation here: http://code.google.com/p/pharo/wiki/Pharo12FrenchAnnouncement Laurent > > Sven > > >

April 5, 2011

Re: [Pharo-project] Remove #class as a Compiler optimization

by Nicolas Cellier

Sorry, no time to read by now, so maybe I should better have shut up... Nonetheless, it much depends on services provided by OS. If we only access the wall clock, then there will be noise due to other OS processes... ... but this noise is unlikely following a gaussian with 0 mean, does it ? In this case, it makes sense to filter out the outliers, and I would say this simple stupid method could possibly work: - take the median - and the standard deviation after filtering out a fixed percentage of outliers But you probably have more ellaborated and well thought method :) Nicolas 2011/4/5 Camillo Bruni <camillo.bruni(a)inria.fr>: > > On 2011-04-05, at 15:02, Nicolas Cellier wrote: > >> Better than average, take the median > > NO! thats why you provide the standard deviation... > > you should not optimize the results prematurely but provide numbers that let you decide on the quality of the benchmarks. what you can do is optimize for systematic errors, like warm up and stuff, but nevertheless you should provide the raw results... > > read the paper... > >> Nicolas >> >> 2011/4/5 Camillo Bruni <camillo.bruni(a)inria.fr>: >>> This is exactly why you have to provide some confidence interval / deviation, otherwise it is hard to make any reasonable conclusion. >>> >>> run it 100 times and take the average and provide the standard deviation. >>> >>> I am not a big fan of relying on incomplete benchmarking results: >>> >>> Please read: http://portal.acm.org/citation.cfm?id=1297033 >>> >>> http://www.squeaksource.com/p.html provides a basic benchmarking framework under the NBenchmark package. You subclass from PBenchmarkSuite implement a method #benchXXX and run it. >>> >>> r := PBFloat run: 100. >>> r asString >>> >>> which will give decent results back :). This way it is much easier to make sense out of the numbers. >>> >>> So here again to remember: >>> >>> - number of samples >>> - average run times >>> - standard deviation >>> >>> If one of these results is missing the benchmark results are incomplete. >>> >>> best regards, >>> camillo >>> >>> >>> >>> On 2011-04-05, at 13:56, Igor Stasenko wrote: >>> >>>> VariableNode initialize. >>>> Compiler recompileAll. >>>> >>>> [ >>>> TestCase allSubclasses do: [ :cls| >>>> Â Â Â Â cls isAbstract >>>> Â Â Â Â Â Â Â Â ifFalse: [cls suite run]]. >>>> ] timeToRun >>>> >>>> 178938 >>>> 183963 >>>> >>>> >>>> >>>> (ParseNode classVarNamed: Â 'StdSelectors') removeKey: #class ifAbsent: []. >>>> Compiler recompileAll. >>>> >>>> [ >>>> TestCase allSubclasses do: [ :cls| >>>> Â Â Â Â cls isAbstract >>>> Â Â Â Â Â Â Â Â ifFalse: [cls suite run]]. >>>> ] timeToRun >>>> >>>> 187168 >>>> 184992 >>>> >>>> the deviation is too big to see if its really so big overhead. >>>> >>>> if you compare worst , you got Â 187/178 ~ 5% >>>> and if you compare the best you got >>>> 184/183 Â ~ 0.5% >>>> >>>> >>>> -- >>>> Best regards, >>>> Igor Stasenko AKA sig. >>>> >>> >>> >>> >> > > >

April 5, 2011

Re: [Pharo-project] Draft Pharo 1.2.1 Release Announcement

by StÃ©phane Ducasse

thanks a lot :) I was thinking that we could do a much faster 1.3 release. We could start to freeze it soon and remove RPackage from the list. Stef > OK, the board approved the draft, so here is the 1.2.1 release announcement: > > http://homepage.mac.com/svc/Pharo/pharo-1.2.1-release.html > > Adrian will put it on the website, next an official mail should be sent to the mailing lists. > > Then we should all try to spread the word! > > Even if it was a bit long winding in the end, this is a release to be proud of. > > Sven > >

April 5, 2011