- Pharo-dev - lists.pharo.org

Re: [Pharo-project] export information to PDF
by StÃ©phane Ducasse Oct. 26, 2010

Oct. 26, 2010

if it works yes and if it does not pollutes everything. So Esteban if you can package this behavior into a package we are interested. Probably look in 3.9 but I'm not sure that it was working there. On Oct 25, 2010, at 12:42 AM, Esteban Lorenzano wrote: > Some time ago, there was a functionality to export a morph as a .ps file, I don't remember in which pharo version that function was lost...maybe it is in a package, and can be loaded, I really don't know, but it should be nice :) > > Cheers, > Esteban > > On 2010-10-24 09:58:09 -0300, name name <onor16(a)gmail.com> said: > >> Hello, >> Could you tell me how can I export (or where I can found ) information that >> I can get with a getter into a .pdf file? >> Thanks >> > ass=3D"text-cell">=A0=A0=A0=A0 Hello, Could you tell me how can I ex= >> port (or where I can found )=20 >> =A0information that I can get with a getter into a .pdf file? >> Thanks >> =09 >> =09 >> =09 >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

3 2

[Pharo-project] is there a way to gofer a configurationOf?
by stephane ducasse Oct. 26, 2010

Oct. 26, 2010

Hi I would like in particular to do Gofer new squeaksource: 'Citezen'; package: 'ConfigurationOfCitezen; push and that all the dependent packages get pushed stef

2 1

Re: [Pharo-project] [squeak-dev] How weak finalization affects the performance
by Igor Stasenko Oct. 26, 2010

Oct. 26, 2010

On 26 October 2010 10:30, Andres Valloud <avalloud(a)smalltalk.comcastbiz.net> wrote: > Why does finalization do any work when running a block which I think just > creates garbage? Â Is finalization on a per class basis (i.e.: the VM > notifies the image that some objects might be notified, and the image just > enumerates through them), or on a per object basis (i.e.: the VM maintains a > finalization queue as in VisualWorks)? > There is no per-object or per-class finalization in Squeak. One must either register an object using WeakRegistry, or add own object to weak dependents (it should answer to #finalizeValues). Squeak VM signals the semaphore each time GC happen, and actually, a finalization process could do something arbitrary to react on such event. Putting delay there ensuring that even if you put a very ineffective finalization into weak dependents, it won't affect the performance too much. > On 10/26/10 0:25 , Igor Stasenko wrote: >> >> Here the idea, which came to Chris, >> put a delay into #finalizationProcess loop: >> >> finalizationProcess >> Â Â Â Â [true] whileTrue: >> Â Â Â Â Â Â Â Â [ WeakFinalizationList initTestPair. >> Â Â Â Â Â Â Â Â FinalizationSemaphore wait. >> Â Â Â Â Â Â Â Â FinalizationLock critical: >> Â Â Â Â Â Â Â Â Â Â Â Â [ >> Â Â Â Â Â Â Â Â Â Â Â Â WeakFinalizationList checkTestPair. >> Â Â Â Â Â Â Â Â Â Â Â Â FinalizationDependents do: >> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â [:weakDependent | >> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â weakDependent ifNotNil: >> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â [weakDependent finalizeValues]]] >> Â Â Â Â Â Â Â Â Â Â Â Â ifError: >> Â Â Â Â Â Â Â Â Â Â Â Â [:msg :rcvr | rcvr error: msg]. >> Â Â Â Â Â Â Â Â 5 seconds asDelay wait. >> Â Â Â Â Â Â Â Â ]. >> >> >> And here a simple benchmark, which triggers GC often: >> >> [ Array new: 100 ] bench >> >> without delay: >> >> '2,450,000 per second.' >> '2,490,000 per second.' >> '2,490,000 per second.' >> '2,480,000 per second.' >> '2,530,000 per second.' >> >> with delay: >> >> '2,670,000 per second.' >> '2,680,000 per second.' >> '2,690,000 per second.' >> '2,730,000 per second.' >> >> roughly about ~8% faster :) >> >> But now lets put something big into weak array: >> >> | dict b | >> dict := WeakKeyDictionary new addAll: (( 1 to: 1000 ) collect: [:i | >> i->i] ); yourself. >> WeakArray addWeakDependent: dict. >> b := [ Array new: 100 ] bench. >> WeakArray removeWeakDependent: dict. >> b >> >> without delay: >> >> '1,840,000 per second.' >> '2,060,000 per second.' >> '2,130,000 per second.' >> >> with delay: >> >> '3,030,000 per second.' >> '2,880,000 per second.' >> '2,890,000 per second.' >> >> Do not forget to do: >> WeakArray restartFinalizationProcess >> >> when you changing the #finalizationProcess method, >> otherwise you won't see real numbers. >> >> So, i like the idea of putting delay there. >> Finalization is eventual, and there is no hard guarantees that it will >> happen in micro-second just after some object become garbage. >> So, be it 5 seconds or 1000 seconds not really matters. >> What is matters that with delay we win much more, by avoiding wasting >> time in finalization process too often. >> >> > > -- Best regards, Igor Stasenko AKA sig.

1 0

[Pharo-project] Fwd: Re: [squeak-dev] How weak finalization affects the performance
by Andres Valloud Oct. 26, 2010

Oct. 26, 2010

-------- Original Message -------- Subject: Re: [squeak-dev] How weak finalization affects the performance Date: Tue, 26 Oct 2010 03:30:13 -0400 From: Andres Valloud <avalloud(a)smalltalk.comcastbiz.net> Reply-To: andres.valloud(a)gmail.com <andres.valloud(a)gmail.com>, The general-purpose Squeak developers list <squeak-dev(a)lists.squeakfoundation.org> To: The general-purpose Squeak developers list <squeak-dev(a)lists.squeakfoundation.org> Why does finalization do any work when running a block which I think just creates garbage? Is finalization on a per class basis (i.e.: the VM notifies the image that some objects might be notified, and the image just enumerates through them), or on a per object basis (i.e.: the VM maintains a finalization queue as in VisualWorks)? On 10/26/10 0:25 , Igor Stasenko wrote: > Here the idea, which came to Chris, > put a delay into #finalizationProcess loop: > > finalizationProcess > [true] whileTrue: > [ WeakFinalizationList initTestPair. > FinalizationSemaphore wait. > FinalizationLock critical: > [ > WeakFinalizationList checkTestPair. > FinalizationDependents do: > [:weakDependent | > weakDependent ifNotNil: > [weakDependent finalizeValues]]] > ifError: > [:msg :rcvr | rcvr error: msg]. > 5 seconds asDelay wait. > ]. > > > And here a simple benchmark, which triggers GC often: > > [ Array new: 100 ] bench > > without delay: > > '2,450,000 per second.' > '2,490,000 per second.' > '2,490,000 per second.' > '2,480,000 per second.' > '2,530,000 per second.' > > with delay: > > '2,670,000 per second.' > '2,680,000 per second.' > '2,690,000 per second.' > '2,730,000 per second.' > > roughly about ~8% faster :) > > But now lets put something big into weak array: > > | dict b | > dict := WeakKeyDictionary new addAll: (( 1 to: 1000 ) collect: [:i | > i->i] ); yourself. > WeakArray addWeakDependent: dict. > b := [ Array new: 100 ] bench. > WeakArray removeWeakDependent: dict. > b > > without delay: > > '1,840,000 per second.' > '2,060,000 per second.' > '2,130,000 per second.' > > with delay: > > '3,030,000 per second.' > '2,880,000 per second.' > '2,890,000 per second.' > > Do not forget to do: > WeakArray restartFinalizationProcess > > when you changing the #finalizationProcess method, > otherwise you won't see real numbers. > > So, i like the idea of putting delay there. > Finalization is eventual, and there is no hard guarantees that it will > happen in micro-second just after some object become garbage. > So, be it 5 seconds or 1000 seconds not really matters. > What is matters that with delay we win much more, by avoiding wasting > time in finalization process too often. > >

1 0

[Pharo-project] How weak finalization affects the performance
by Igor Stasenko Oct. 26, 2010

Oct. 26, 2010

Here the idea, which came to Chris, put a delay into #finalizationProcess loop: finalizationProcess [true] whileTrue: [ WeakFinalizationList initTestPair. FinalizationSemaphore wait. FinalizationLock critical: [ WeakFinalizationList checkTestPair. FinalizationDependents do: [:weakDependent | weakDependent ifNotNil: [weakDependent finalizeValues]]] ifError: [:msg :rcvr | rcvr error: msg]. 5 seconds asDelay wait. ]. And here a simple benchmark, which triggers GC often: [ Array new: 100 ] bench without delay: '2,450,000 per second.' '2,490,000 per second.' '2,490,000 per second.' '2,480,000 per second.' '2,530,000 per second.' with delay: '2,670,000 per second.' '2,680,000 per second.' '2,690,000 per second.' '2,730,000 per second.' roughly about ~8% faster :) But now lets put something big into weak array: | dict b | dict := WeakKeyDictionary new addAll: (( 1 to: 1000 ) collect: [:i | i->i] ); yourself. WeakArray addWeakDependent: dict. b := [ Array new: 100 ] bench. WeakArray removeWeakDependent: dict. b without delay: '1,840,000 per second.' '2,060,000 per second.' '2,130,000 per second.' with delay: '3,030,000 per second.' '2,880,000 per second.' '2,890,000 per second.' Do not forget to do: WeakArray restartFinalizationProcess when you changing the #finalizationProcess method, otherwise you won't see real numbers. So, i like the idea of putting delay there. Finalization is eventual, and there is no hard guarantees that it will happen in micro-second just after some object become garbage. So, be it 5 seconds or 1000 seconds not really matters. What is matters that with delay we win much more, by avoiding wasting time in finalization process too often. -- Best regards, Igor Stasenko AKA sig.

1 0

[Pharo-project] About Adding/modifying in SUnit or not?
by Luc Fabresse Oct. 26, 2010

Oct. 26, 2010

Hi all, I am working on pushing environments in SystemNavigation. SystemNavigationTest previously used ClassFactoryForTestCase from SUnit for generating classes. Now I need an environment-aware ClassFactoryForTestCase. Should I directly modify ClassFactoryForTestCase since a class generator should now be environment aware? Should I subclass ClassFactoryForTestCase and put it in SUnit? Should I never changed SUnit and put it elsewhere? ;-) #Luc

3 3

[Pharo-project] private instance variables NOT objects? (Wikipedia)
by Lawson English Oct. 25, 2010

Oct. 25, 2010

In the Wikipedia entry on Smalltalk, there is this line in the history section, 3rd paragraph, added roughly a year ago: "...Smalltalk-80 added [[metaclass]]es, to help maintain the "everything is an object" (except private instance variables) paradigm by associating properties and behavior with individual classes, ..." Is this one of those esoteric details that mere mortals are not meant to understand, or is this an error? Lawson

4 3

Oct. 25, 2010

Ok we can deprecate it. On Oct 22, 2010, at 11:04 PM, Hernan Wilkinson wrote: > In a 1.1 image I have, the class HttpRequest is using that message... > > On Thu, Oct 21, 2010 at 4:08 PM, stephane ducasse <stephane.ducasse(a)free.fr> wrote: > I would like to deprecate the following method since nobody use it. > What do you think? > > Stef > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > -- > HernÃ¡n Wilkinson > Agile Software Development, Teaching & Coaching > Mobile: +54 - 911 - 4470 - 7207 > email: hernan.wilkinson(a)10Pines.com > site: http://www.10Pines.com > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

5 5

[Pharo-project] Fwd: [squeak-dev] bug in OBMetagraphBuilder>>#reference
by Mariano Martinez Peck Oct. 25, 2010

Oct. 25, 2010

lukas? ---------- Forwarded message ---------- From: Chris Muller <asqueaker(a)gmail.com> Date: Mon, Oct 25, 2010 at 6:16 PM Subject: [squeak-dev] bug in OBMetagraphBuilder>>#reference To: squeak dev <squeak-dev(a)lists.squeakfoundation.org> Hi, I just wanted to let the maintainers of OmniBrowser know, there is a bug with this method. The method reflects on its class and performs all that begin with #populate. However, it is not unusual to expect that someone's application might have a selector that also begins with the word 'populate'. And so those selectors would be performed as well. This is why, for cases like this, it is better for a tool, which is just a means, not an end, to be polite with the namespace; such as checking for 'obPopulate' perhaps rather than simply 'populate'. But that's just a mini-rant, not even the bug. The bug is, my 'populate' is not a unary message, so I get a failure on the perform, "incorrect number of arguments." I therefore always change the method to: OBMetagraphBuilder >> execute ((self class allSelectors select: [:ea | (ea beginsWith: 'populate') and: [ ea isUnary ]]) asSortedArray) do: [:selector | self perform: selector]. ^ self root Thank you, Chris

2 1

Re: [Pharo-project] what happened with Shout colors in Pharo 1.1?
by Simon Denier Oct. 25, 2010

Oct. 25, 2010

On 15 oct. 2010, at 17:31, Mariano Martinez Peck wrote: > They've changed a lot from 1.0. For example, self, super, etc, are not in "orange" or that color of 1.0. > Instances variables, are blue (instead of black), the same as parameters,etc... > > is there a way to recover the original colors? do we wanted this change or it is accidental ? I think the colors in 1.0 were inherited from the dev images build by Damien Cassou. In 1.1, the colors comes from the settings of Lukas, who maintains Shout? Am I wrong? I liked the colors in 1.0, but now I am accustomed to the current theme, which is very keen to the eye, except for two things that I change: - distinguish instance vars/class vars from other variables: I use a brownish color for that, as I want to see at once methods accessing the state of the object - distinguish class references: I use bold black as in the previous style, as I want to quickly catch hard dependencies in the code To customize colors, two solutions: 1) hack SHTextStylerST80>>defaultStyleTable 2) load latest Shout and use Settings (then you should be able to save/load your style), since there is now a Settings interface -- Simon

3 5