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

Re: [Pharo-project] Fuel for Squeak stupid questions

by Mariano Martinez Peck

On Mon, Oct 8, 2012 at 8:30 AM, Max Leske <maxleske(a)gmail.com> wrote: > Looking at the failing tests I see that the objects really are supposed to > be different (comparison with #~~). What fails is the equality check (#=) > and for Date that is the method Timespan>>=. The problem that occurs there > is a really old (and annoying one), namely that the timezone offset is > handled inconsistently: the materialized object has the correct offset > while the original object doesn't. > > I think it could work if you just remove Date>>fuelAccept: . Can you try? > So: > - FLBasicSerializationTest>>testDate fails because of timezone offset > - FLBasicSerializationTest>>testGradientFillStyle fails because Object>>= > isn't overridden in any subclass and therefore identity is checked, which > fails > - (same as above for FLBasicInMemorySerializationTest) > > The other failures seem to be due to implementation differences between > Pharo and Squeak (I didn't really look into them) but I couldn't find one > test that seemed to fail because of hashing problems. > Yes, I didn't really understand the thing with the hashes. I don't think there should be a problem there. Something obvious is that a normal object that is serialized will probabyt have a different identityHash than the materialized object. Thanks! > I'll see if I can come up with a test case. > > Cheers, > Max > > > On 07.10.2012, at 16:38, Max Leske <maxleske(a)gmail.com> wrote: > > The two objects I looked at where a string and an OrderedCollection. I > wouldn't conclude that the problem is class specific... > > On 07.10.2012, at 16:12, "Edgar J. De Cleene" <edgardec2005(a)gmail.com> > wrote: > > > > > On 10/7/12 10:51 AM, "Max Leske" <maxleske(a)gmail.com> wrote: > > > Following you example, in Squeak FLBasicSerializationTest>>#testDate > > materialized largeIdentityHash = 2571 > > anObject. largeIdentityHash = *1094 > * > > So why Date serializaded object gives this and the rest of objects no ? > > Edgar > > > -- Mariano http://marianopeck.wordpress.com

Oct. 8, 2012

[Pharo-project] [update 2.0] #20326

by Marcus Denker

20326 ----- Issue 6772: Incorrect MorphTreeNodeMorph>>selectionFrame http://code.google.com/p/pharo/issues/detail?id=6772 Issue 6754: Nautilus Browser Restricted Package by Regex http://code.google.com/p/pharo/issues/detail?id=6754 -- Marcus Denker -- http://marcusdenker.de

Oct. 8, 2012

Re: [Pharo-project] Global session object?

by Marcus Denker

Hello, Yes, this sounds good. Marcus On Oct 8, 2012, at 5:11 AM, Igor Stasenko <siguctua(a)gmail.com> wrote: > I wanna have this: > > SmalltalkImage>>snapshot: save andQuit: quit > ... > resuming ifTrue: [ session := self newSession ]. > ... > > (where session is additional instance variable of SmalltalkImage). > > SmalltalkImage>>newSession > "Just answer unique object, which never can be identical to any > previous session object, > this is all what we need for detecting session change. > A session object don't needs to carry any state (we have plenty of > other objects in image which can do this for us). it just needs to be > unique" > > ^ Object new. > > SmalltalkImage>>session > ^ session > > then, i can write in own code: > > Smalltalk session == mySession ifFalse: [ self initForNewSession. > mySession := Smalltalk session ] > > So, basically, this little addition allows you to detect whether > session changed or not between > two different calls to your code (given that you remembered the > previous session somewhere). > Currently we don't have such feature, and looking how some existing > code deals with session management, > i see how it can be simplified. > If you want to do something similar today, you will need to register > in startup list.. which IMO stinks ;) > > i don't like using startup lists, since you never know , what is the > right order of resource initialization, > and what inter-dependencies they may form, and changing dependencies > over time will require changing startup order, again and again. Not > fun. > This technique allows you to lazily re-initialize any of your > object(s) due to session change, once the control flow hits your code, > but not before. > (so you don't have to do all accounting at image startup time, you > doing it only when it required/requested, which means shorter image > startup time). > > The notion of session is highly important for external resource management. > > I using it in NativeBoost from very beginning, and wanna propose to > use it globally. > > > -- > Best regards, > Igor Stasenko. > -- Marcus Denker -- http://marcusdenker.de

Oct. 8, 2012

Re: [Pharo-project] Fuel for Squeak stupid questions

by Max Leske

Looking at the failing tests I see that the objects really are supposed to be different (comparison with #~~). What fails is the equality check (#=) and for Date that is the method Timespan>>=. The problem that occurs there is a really old (and annoying one), namely that the timezone offset is handled inconsistently: the materialized object has the correct offset while the original object doesn't. So: - FLBasicSerializationTest>>testDate fails because of timezone offset - FLBasicSerializationTest>>testGradientFillStyle fails because Object>>= isn't overridden in any subclass and therefore identity is checked, which fails - (same as above for FLBasicInMemorySerializationTest) The other failures seem to be due to implementation differences between Pharo and Squeak (I didn't really look into them) but I couldn't find one test that seemed to fail because of hashing problems. I'll see if I can come up with a test case. Cheers, Max On 07.10.2012, at 16:38, Max Leske <maxleske(a)gmail.com> wrote: > The two objects I looked at where a string and an OrderedCollection. I wouldn't conclude that the problem is class specific... > > On 07.10.2012, at 16:12, "Edgar J. De Cleene" <edgardec2005(a)gmail.com> wrote: > >> >> >> >> On 10/7/12 10:51 AM, "Max Leske" <maxleske(a)gmail.com> wrote: >> >> >> Following you example, in Squeak FLBasicSerializationTest>>#testDate >> >> materialized largeIdentityHash = 2571 >> >> anObject. largeIdentityHash = 1094 >> >> >> So why Date serializaded object gives this and the rest of objects no ? >> >> Edgar >>

Oct. 8, 2012

[Pharo-project] Global session object?

by Igor Stasenko

I wanna have this: SmalltalkImage>>snapshot: save andQuit: quit ... resuming ifTrue: [ session := self newSession ]. ... (where session is additional instance variable of SmalltalkImage). SmalltalkImage>>newSession "Just answer unique object, which never can be identical to any previous session object, this is all what we need for detecting session change. A session object don't needs to carry any state (we have plenty of other objects in image which can do this for us). it just needs to be unique" ^ Object new. SmalltalkImage>>session ^ session then, i can write in own code: Smalltalk session == mySession ifFalse: [ self initForNewSession. mySession := Smalltalk session ] So, basically, this little addition allows you to detect whether session changed or not between two different calls to your code (given that you remembered the previous session somewhere). Currently we don't have such feature, and looking how some existing code deals with session management, i see how it can be simplified. If you want to do something similar today, you will need to register in startup list.. which IMO stinks ;) i don't like using startup lists, since you never know , what is the right order of resource initialization, and what inter-dependencies they may form, and changing dependencies over time will require changing startup order, again and again. Not fun. This technique allows you to lazily re-initialize any of your object(s) due to session change, once the control flow hits your code, but not before. (so you don't have to do all accounting at image startup time, you doing it only when it required/requested, which means shorter image startup time). The notion of session is highly important for external resource management. I using it in NativeBoost from very beginning, and wanna propose to use it globally. -- Best regards, Igor Stasenko.

Oct. 8, 2012

[Pharo-project] How do I add Keyboard Shortcuts to the ChangesBrowser?

by Camillo Bruni

How do I do that? I am very lazy, each time I have to move my hand to the mouse I get exhausted... For refactorings we have this nice ChangesBrowser that pops up. I would like to add the following features: - default selection on the first item in the list - up/down changes selection - CMD+s accept the changes - ESC close the window how can I add the link to the keymapping shortcuts within this spec thingy?

Oct. 7, 2012

Re: [Pharo-project] outdated wiki entries

by Camillo Bruni

nice looks already much better ;) On 2012-10-07, at 21:52, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > I removed a couple of them. > > Stef > > On Oct 7, 2012, at 9:37 PM, StÃ©phane Ducasse wrote: > >> I will do a pass on them. >> >> >> On Oct 7, 2012, at 8:48 PM, Camillo Bruni wrote: >> >>> If I look at the wiki on >>> >>> https://code.google.com/p/pharo/w/list >>> >>> I see a lot of entries that are no longer valid and outdated... >>> I will delete all the entries without changes in the last year and >>> which have no value to developers. If anyone wants these entries >>> back they are safely archived in the google's svn. >>> >>> best >>> cami >>> >> >> > >

Oct. 7, 2012

Re: [Pharo-project] outdated wiki entries

by StÃ©phane Ducasse

I removed a couple of them. Stef On Oct 7, 2012, at 9:37 PM, StÃ©phane Ducasse wrote: > I will do a pass on them. > > > On Oct 7, 2012, at 8:48 PM, Camillo Bruni wrote: > >> If I look at the wiki on >> >> https://code.google.com/p/pharo/w/list >> >> I see a lot of entries that are no longer valid and outdated... >> I will delete all the entries without changes in the last year and >> which have no value to developers. If anyone wants these entries >> back they are safely archived in the google's svn. >> >> best >> cami >> > >

Oct. 7, 2012

Re: [Pharo-project] outdated wiki entries

by StÃ©phane Ducasse

I will do a pass on them. On Oct 7, 2012, at 8:48 PM, Camillo Bruni wrote: > If I look at the wiki on > > https://code.google.com/p/pharo/w/list > > I see a lot of entries that are no longer valid and outdated... > I will delete all the entries without changes in the last year and > which have no value to developers. If anyone wants these entries > back they are safely archived in the google's svn. > > best > cami >

Oct. 7, 2012

[Pharo-project] outdated wiki entries

by Camillo Bruni

If I look at the wiki on https://code.google.com/p/pharo/w/list I see a lot of entries that are no longer valid and outdated... I will delete all the entries without changes in the last year and which have no value to developers. If anyone wants these entries back they are safely archived in the google's svn. best cami

Oct. 7, 2012