January 2013 - Pharo-dev - lists.pharo.org

[Pharo-project] about Loom profiler

by StÃ©phane Ducasse

Hi alex how Loom compares with the fixes that andreas added to the default profiler. I do not know if the code is in squeak because this code was licensed under GPL. But I would like to know if your profiler takes into account the problems solved by andreas. I did not see an announce of Loom (by the way Loom is the name of large oo memory developed by the original smalltalk team a while ago). http://objectprofile.com/loom-download.html I'm know that some people got problem with our profiler and I would like to see how we can improve it. Stef

Jan. 18, 2013

Re: [Pharo-project] [Jenkins] Old Jenkins to shut down 28.01

by Marcus Denker

On Jan 18, 2013, at 10:46 AM, Damien Cassou <damien.cassou(a)gmail.com> wrote: > > On Fri, Jan 18, 2013 at 10:26 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > On > > 28.01.2013 > > we will delete all remaining projects and tell IT to shut down the > server and slaves. > > > If you can, you could change the CSS so that background of the website is red. > > > No idea how and I would like to spend my time improving the new setupâ¦ Marcus

Jan. 18, 2013

Re: [Pharo-project] [Jenkins] Old Jenkins to shut down 28.01

by Damien Cassou

On Fri, Jan 18, 2013 at 10:26 AM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > On > > 28.01.2013 > > we will delete all remaining projects and tell IT to shut down the > server and slaves. > If you can, you could change the CSS so that background of the website is red. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

Jan. 18, 2013

[Pharo-project] [Jenkins] Old Jenkins to shut down 28.01

by Marcus Denker

Hi, Having two Jenkins setups with very similar URLs us highly confusing (I have edited the wrong project in the pastâ¦) Therefore, with the new setup in Place and all projects either already migrated or in the process of being migrated, we should put an end date. On 28.01.2013 we will delete all remaining projects and tell IT to shut down the server and slaves. Marcus

Jan. 18, 2013

Re: [Pharo-project] Where should SmalltalkHub bugs be reported?

by Nicolas Petton

Thanks Camillo :) Nico - Camillo Bruni <camillobruni(a)gmail.com> writes: > I just opened a google code project, it's been too long since we don't > have a proper issue tracker for smalltalkhub: > > https://code.google.com/p/smalltalk-hub > > > On 2013-01-17, at 18:15, "Sean P. DeNigris" <sean(a)clipperadams.com> wrote: > >> Here's a small one... StHub provides a Monticello registration snippet, which >> is cool: >> MCHttpRepository >> location: 'http://smalltalkhub.com/mc/dh83/fisleg/main' >> user: 'SeanDeNigris' >> password: '' >> But in Pharo 2.0, since there is a user but no password, dialogs pop up >> asking for credentials, which can not be ignored. Since the great majority >> of uses is for downloading, I think it'd make more sense to leave the >> username out. >> >> Cheers, >> Sean >> >> >> >> -- >> View this message in context: http://forum.world.st/Where-should-SmalltalkHub-bugs-be-reported-tp4663973.… >> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >> > > -- Nicolas Petton http://nicolas-petton.fr

Jan. 18, 2013

Re: [Pharo-project] Where should SmalltalkHub bugs be reported?

by Nicolas Petton

The username is only there if you are logged in. If not, it's not there. Do you think it should always be left out? Nico "Sean P. DeNigris" <sean(a)clipperadams.com> writes: > Here's a small one... StHub provides a Monticello registration snippet, which > is cool: > MCHttpRepository > location: 'http://smalltalkhub.com/mc/dh83/fisleg/main' > user: 'SeanDeNigris' > password: '' > But in Pharo 2.0, since there is a user but no password, dialogs pop up > asking for credentials, which can not be ignored. Since the great majority > of uses is for downloading, I think it'd make more sense to leave the > username out. > > Cheers, > Sean > > > > -- > View this message in context: http://forum.world.st/Where-should-SmalltalkHub-bugs-be-reported-tp4663973.… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > -- Nicolas Petton http://nicolas-petton.fr

Jan. 18, 2013

Re: [Pharo-project] Where should SmalltalkHub bugs be reported?

by Sean P. DeNigris

Camillo Bruni-3 wrote > I just opened a google code project Sweet, I'm first! Issue 1: Monticello Registration snippet should not supply user name -- View this message in context: http://forum.world.st/Where-should-SmalltalkHub-bugs-be-reported-tp4663973p… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Jan. 17, 2013

Re: [Pharo-project] CI Current Status

by StÃ©phane Ducasse

I can tell that working with the old infrastructure was raising the level of bird names exchanged in emails ;) Now this is getting calm and relaxed Stef >> Marcus Denker-4 wrote >>> We have moved more or less everything to the new Jenkins setup. >>> ... >>> it gets better every day. >> >> Bravo! Thanks for all the hard work, Marcus :) > > Yes, great work, from a whole team ! > > Sven >

Jan. 17, 2013

Re: [Pharo-project] Class initialisation after loading

by StÃ©phane Ducasse

> I think that forcing frequent class reinitialization and forcing users to write idempotent class initialization is consistent with Pharo's philosophical position on fixing broken things, and on good documentation and simplicity. I also think that it's a good idea. +1 :) This is also why I love so much bootstrap because it forces us to verify that initialization is working and done systematically. Stef

Jan. 17, 2013

Re: [Pharo-project] the monkey is back in town

by Esteban A. Maringolo

Me neither. But I can through this link: https://code.google.com/p/pharo/issues/detail?id=7268 Esteban A. Maringolo 2013/1/17 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > strange I cannot reach this page. > > Stef > > On Jan 16, 2013, at 7:23 PM, Camillo Bruni wrote: > >> the 100% smalltalk monkey is back at work: >> >> https://code.google.com/p/pharo/issues/detail?can=2&q=7268 >> >> let's hope it will stay like this for a while! >> > >

Jan. 17, 2013