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

[Pharo-project] Lazy initialization [was Help with a WeakOrderedCollection and objects not being GCed]
by Nicolas Cellier Aug. 4, 2011

Aug. 4, 2011

2011/8/3 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > > On Aug 3, 2011, at 1:49 PM, Nicolas Cellier wrote: > >> Oh I see, for the SLICE, this is again the Pharo's version of >> MCPackageLoader>>basicLoad which is striking. >> In Squeak trunk it would work because removals are performed AFTER >> methodAdditions/Changes. >> In Pharo, removals are performed BEFORE, so yes, the SLICE needs to be >> split in two parts... >> Or you can just manually merge it (apply the removal after...). > > oops we should fix that > > >> I'm eager to see a true atomic load with a single massive becomeForward: :) > > Yes me too > >> IMHO, this should be coupled with lazy initializations mechanism as I >> proposed once (based on pragmas). > > Can you point us to that? > > I cannot find my original posts, maybe they remained a draft, so here it is. http://smallissimo.blogspot.com/2011/08/lazy-initialization-of-shared-varia… Nicolas

2 1

Re: [Pharo-project] Pharo 1.4 #14076 update failed.
by Marcus Denker Aug. 4, 2011

Aug. 4, 2011

On Aug 4, 2011, at 1:46 PM, Laszlo Zsolt Kiss wrote: > > aloha pharoers! > > i don' know what is the problem > My image is clean 1.4. which version? > But I geted the attached message. > Please help. > Works fine here... -- Marcus Denker -- http://marcusdenker.de

3 3

[Pharo-project] [ANN] SmalltalkHub demo online
by Torsten Bergmann Aug. 4, 2011

Aug. 4, 2011

Serge wrote >Very similar to forks in github: if you have no access to a project or >the project seems stalled, you fork the project ans apply your own >patches. But with one difference: a fork means really forking (the whole) codebase and this fork is usually available at a different location. You can (and have to) completely maintain this fork then. This could be good or bad. The more forks exist the more people can be confused... But an projects "Inbox" would be bound to the project - so project developers/admins could decide which "inbox" contribution to accept and integrate into the code base. People who provide good contributions could later be added as project developers and even when a contribution is not integrated it is close to the project for others to use. Currently we do something similar with Pharo and PharoInbox - but they are two separate projects in SqS. A default "Inbox" for any project would IMHO a nice addition. Bye T. -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de

3 2

[Pharo-project] Pharo 1.4 #14076 update failed.
by Laszlo Zsolt Kiss Aug. 4, 2011

Aug. 4, 2011

aloha pharoers! i don' know what is the problemMy image is clean 14.But I geted the attached message.Please help.Thx Best reagrdsÂ LAszlo Zsolt Kiss

1 0

[Pharo-project] [update 1.4] #14076
by Marcus Denker Aug. 4, 2011

Aug. 4, 2011

14076 ----- Issue 4596: WeakOrderedColllection array is replaced by an Array instead of a WeakArray (part 2) -- Marcus Denker -- http://marcusdenker.de

1 0

[Pharo-project] ThreadSafeTranscript
by Pavel Krivanek Aug. 4, 2011

Aug. 4, 2011

Hi, why in the latest 1.4 image is ThreadSafeTranscript back? Wasn't it replaced by TranscriptModel? It breaks Pharo-Kernel CI job (it doesn't report fail but I will fix that). -- Pavel

2 2

[Pharo-project] [update 1.4] #14075
by Marcus Denker Aug. 4, 2011

Aug. 4, 2011

14075 ----- Issue 4596: WeakOrderedColllection array is replaced by an Array instead of a WeakArray (part 1) -- Marcus Denker -- http://marcusdenker.de

1 0

[Pharo-project] [ANN] SmalltalkHub demo online
by Torsten Bergmann Aug. 4, 2011

Aug. 4, 2011

>Request: please include a way to store contributions from the public (like >maybe per-project inboxes). >Motivation: With SqS, it seems great fixes and enhancements often get lost >on old hard drives or the mailing list because the authors don't have write >access to the repo, and it's often hard to contact the admins. >Result: every contribution will be preserved and easily findable from the >project's repo, while admins maintain control over their codebase if >desired. Great idead! +1000 Bye T. -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de

2 1

[Pharo-project] [update 1.4] #14074
by Marcus Denker Aug. 4, 2011

Aug. 4, 2011

14074 ----- Issue 4565: Monticello workflow broken http://code.google.com/p/pharo/issues/detail?id=4565 Issue 4597: StrikeFont aggressive cleanup should remove DejaVu source http://code.google.com/p/pharo/issues/detail?id=4597 -- Marcus Denker -- http://marcusdenker.de

1 0

Re: [Pharo-project] Small Seaside image
by Marcus Denker Aug. 3, 2011

Aug. 3, 2011

On Aug 3, 2011, at 10:17 AM, laurent laffont wrote: > Hi, > > actually using PharoCore 1.3, loading ConfigurationOfSeaside30 Core, then ScriptLoader>>cleanUpForProduction I have a 13MB image. Is it possible to have it smaller ? (I know a next step is to be able to use PharoKernel). cleanUpForProduction should result in a Core image that is just 6.5MB... so the ConfigurationOfSeaside30 seems to load *a lot* of stuff? Maybe be a bit selective? Marcus -- Marcus Denker -- http://marcusdenker.de

3 2