November 2012 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Are the any Fuel file analysis tools/techniques?

by Yanni Chiu

On 04/11/12 6:43 AM, Mariano Martinez Peck wrote: > But this only works for the serialization, not for the materialization. FLMaterializer>>materializeFromFileNamed: aFilename ^ (self materializationFromFileNamed: aFilename) root I've been using #materializeFromFileNamed: in my code, but I just happened to pick #materializationFromFileNamed: while debugging another problem, a moment ago. When I inspect the resulting FLMaterialization object, I can see the clusters - which is exacting what I was looking for a few days ago. By scanning the clusters, it should have been easy to figure out what objects should never have been serialized (e.g. WASession). Which was a critical clue to figure out where to look for where the extra objects were coming from.

Nov. 5, 2012

Re: [Pharo-project] About a object life

by Edgar J. De Cleene

On 11/4/12 4:33 PM, "Craig Latta" <craig(a)netjam.org> wrote: > > Hi Edgar-- > > Do you really want to know how old an object is, or just whether > it's older than some other object? If you don't care about degrading the > identity hash distribution, you could steal a few bits from the object > header for a counter. Craig: Like to know how old an object is. As my reply to Hans-Martin, guess this is not possible in current Pharo/Squeak. Nice to read you ! Edgar

Nov. 4, 2012

Re: [Pharo-project] PluggableListMorph error, how to debug ?

by Alexandre Bergel

Excellent tip!! Alexandre On Nov 4, 2012, at 2:37 PM, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: > In Pharo 1.4, browse Morph > Find the method fullDrawOn: > > and replace > > on: Error do: [:err | > self setProperty: #errorOnDraw toValue: true. > self setProperty: #drawError toValue: err freeze. > ^ self drawErrorOn: aCanvas > ] > > by: > value > > Now you will have a debugger instead of the red square of death > > But do it at you own risk ^^ > Ben > > On Nov 4, 2012, at 6:04 PM, laurent laffont wrote: > >> Hi, >> >> sometimes I have a PluggableListMorph that displays a big red square (see attached screenshot). How can I debug why this happens ? >> >> <image.png> >> >> Cheers, >> >> Laurent > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Nov. 4, 2012

Re: [Pharo-project] About a object life

by Craig Latta

Hi Edgar-- Do you really want to know how old an object is, or just whether it's older than some other object? If you don't care about degrading the identity hash distribution, you could steal a few bits from the object header for a counter. -C -- Craig Latta www.netjam.org/resume +31 6 2757 7177 + 1 510 396 5727

Nov. 4, 2012

Re: [Pharo-project] 20381 running the test does not work ...

by StÃ©phane Ducasse

do you know what is the ProgressIndicatorMorph and LoggingSystemProgressItemMorph (which inherits from Object)? I will start to group all the classes into a separate package. Potentially rename them so that we can edit them and try to fix that. Stef On Nov 4, 2012, at 11:30 AM, Camillo Bruni wrote: > definitely the hierarchy is mess there. And there are indeed only 4 items needed > - the Global displayed SystemProgressMorph which contains multiple progress indicators > and the logics to force update the UI even when stuff runs in the UI thread > - the item (title + progress bar) > - the progress bar > - the job item (title + progress bar + interrupt button)

Nov. 4, 2012

Re: [Pharo-project] PluggableListMorph error, how to debug ?

by laurent laffont

Cool :) Laurent On Sun, Nov 4, 2012 at 6:13 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>wrote: > In pharo2.0 you can click on it and it opens a debugger. > > Stef > > On Nov 4, 2012, at 6:04 PM, laurent laffont wrote: > > > Hi, > > > > sometimes I have a PluggableListMorph that displays a big red square > (see attached screenshot). How can I debug why this happens ? > > > > <image.png> > > > > Cheers, > > > > Laurent > > >

Nov. 4, 2012

Re: [Pharo-project] PluggableListMorph error, how to debug ?

by laurent laffont

Thanks for the tip ! Laurent On Sun, Nov 4, 2012 at 6:37 PM, Benjamin < benjamin.vanryseghem.pharo(a)gmail.com> wrote: > In Pharo 1.4, browse Morph > Find the method fullDrawOn: > > and replace > > on: Error do: [:err | > self setProperty: #errorOnDraw toValue: true. > self setProperty: #drawError toValue: err freeze. > ^ self drawErrorOn: aCanvas > ] > > by: > value > > Now you will have a debugger instead of the red square of death > > But do it at you own risk ^^ > Ben > > On Nov 4, 2012, at 6:04 PM, laurent laffont wrote: > > > Hi, > > > > sometimes I have a PluggableListMorph that displays a big red square > (see attached screenshot). How can I debug why this happens ? > > > > <image.png> > > > > Cheers, > > > > Laurent > > >

Nov. 4, 2012

Re: [Pharo-project] PluggableListMorph error, how to debug ?

by Benjamin

In Pharo 1.4, browse Morph Find the method fullDrawOn: and replace on: Error do: [:err | self setProperty: #errorOnDraw toValue: true. self setProperty: #drawError toValue: err freeze. ^ self drawErrorOn: aCanvas ] by: value Now you will have a debugger instead of the red square of death But do it at you own risk ^^ Ben On Nov 4, 2012, at 6:04 PM, laurent laffont wrote: > Hi, > > sometimes I have a PluggableListMorph that displays a big red square (see attached screenshot). How can I debug why this happens ? > > <image.png> > > Cheers, > > Laurent

Nov. 4, 2012

Re: [Pharo-project] PluggableListMorph error, how to debug ?

by StÃ©phane Ducasse

In pharo2.0 you can click on it and it opens a debugger. Stef On Nov 4, 2012, at 6:04 PM, laurent laffont wrote: > Hi, > > sometimes I have a PluggableListMorph that displays a big red square (see attached screenshot). How can I debug why this happens ? > > <image.png> > > Cheers, > > Laurent

Nov. 4, 2012

[Pharo-project] PluggableListMorph error, how to debug ?

by laurent laffont

Hi, sometimes I have a PluggableListMorph that displays a big red square (see attached screenshot). How can I debug why this happens ? [image: Inline image 1] Cheers, Laurent

Nov. 4, 2012