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

Re: [Pharo-project] History and SUnit

by Damien Cassou

On Wed, Oct 1, 2008 at 5:13 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > can you tell us more? http://wiki.squeak.org/squeak/SUnit%20for%203.10 -- Damien Cassou Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu)

Oct. 2, 2008

Re: [Pharo-project] How to integrate Kernel-Extensions

by StÃ©phane Ducasse

I propose to harvest the cleaning behavior. I will go over the list and check Stef On Oct 1, 2008, at 10:53 PM, Damien Pollet wrote: > Hi list, we (with Stef) are browsing Kernel-Extensions, here are some > notes for discussion, as we think there is stuff that should be merged > in Pharo. > > Null and Split-Join could be packaged on their own since they are > well-defined features. > > Most of the cleanup methods make sense, but what's the difference > between cleanUp and freeSomeSpace ? > > AppRegistry class >> removeObsolete > "AppRegistry removeObsoleteClasses" > self registeredClasses copy do:[:cls| > (cls class isObsolete or:[cls isBehavior and:[cls isObsolete]]) > ifTrue:[self unregister: cls]]. > self subclasses do:[:cls| cls removeObsolete]. > > Behavior class >> flushObsoleteSubclasses > "Behavior flushObsoleteSubclasses" > ObsoleteSubclasses finalizeValues. > > Behavior >> sourceMatchesBytecodeAt: > > Class class >> freeSomeSpace > "Fix some problems with classes. Use Smalltalk allClassesDo: since it > does not use the subclass list, which we may be modifying during this > iteration" > Smalltalk allClassesDo: [:ea | > ea fixObsoleteSuperclass. > ea removeDuplicateSubclassEntries] > > Collection >> contains: should probably be standardized as part of > the STEPS project > Collection >> reject:thenDo: and select:thenDo: should be > included and similar enumerations reimplemented in this way too > > SystemDictionary >> forgetClass: aClass logged: aBool badly > named but interesting > "Delete the class, aClass, from the system. > Note that this doesn't do everything required to dispose of a class - > to do that use Class>>removeFromSystem." > > aBool ifTrue: [SystemChangeNotifier uniqueInstance classRemoved: > aClass fromCategory: aClass category]. > SystemOrganization removeElement: aClass name. > self removeFromStartUpList: aClass. > self removeFromShutDownList: aClass. > self removeKey: aClass name ifAbsent: []. > DataStream classRemoved: aClass. > self flushClassNameCache > > SystemDictionary >> globals needs to pay attention that compiled > methods share the associations > > Number >> to: stop do: aBlock displayingProgress: aString would be > probably nicer with the block argument last > > > === To discuss: > > Collection >> removeAll: comment should explain in which cases it > is useful > "the slow way" > ^ self removeAllSuchThat: [ :each | true ] > > SequenceableCollection >> <= smells funnyâ¦ what is it useful for ? > SequenceableCollection >> replacing:with: replaces in place, not > obvious from the name > the stream methods like putOn: â¦ convenience ? are they coherent ? > > String >> withoutTrailing: probably makes sense but then this is > mostly useful for line breaksâ¦ why not a #trimLinebreak > > Set >> likeOrAdd: ok but then that should be available for any > collection (and renamed addIfAbsent:) > "Include newObject as one of the receiver's elements, but only if > not already present. Answer the oldObject." > > > === Useless: > > ProtoObject >> iconOrThumbnailOfSize: > Object >> askFor: and askFor:ifDefault: that's a workaround > > Object >> deprecated is already here > Object >> log should be packaged in a logging package since it's a > convenience method > > SequenceableCollection >> copyReplacing:with: just to type one > space less ? > > > > -- > Damien Pollet > type less, do more [ | ] http://people.untyped.org/damien.pollet > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Oct. 2, 2008

Re: [Pharo-project] Changes from COG

by StÃ©phane Ducasse

Thanks mathieu. We will include that since COG is MIT Stef On Oct 2, 2008, at 2:36 PM, Mathieu Suen wrote: > Hi, > > If you don't mind Eliot, I have taken a changeset from COG to Pharo. > You can integrate it. It should work fine > This change is for having a better CompiledMethod explorer. See > attached file. > > <BytecodeBrowsing.2.cs> > Mth > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Oct. 2, 2008

[Pharo-project] Package browser bugs

by StÃ©phane Ducasse

Hi david 2 bugs: - when I select a class in a hierarchy when I click on package, the package is not selected - the drag and drop on a package does not work with me. Let me know if you need a more precise example Stef

Oct. 2, 2008

[Pharo-project] Changes from COG

by Mathieu Suen

Hi, If you don't mind Eliot, I have taken a changeset from COG to Pharo. You can integrate it. It should work fine This change is for having a better CompiledMethod explorer. See attached file. Mth

Oct. 2, 2008

[Pharo-project] Fwd: [squeak-dev] re: Squeak 4

by StÃ©phane Ducasse

for information. I will continue to harvest etoy removals and gary/simon enh. Stef > From: Craig Latta <craig(a)netjam.org> > Date: October 1, 2008 10:49:14 PM CEDT > To: squeak-dev(a)lists.squeakfoundation.org > Subject: [squeak-dev] re: Squeak 4 > Reply-To: The general-purpose Squeak developers list <squeak-dev(a)lists.squeakfoundation.org > > > > > Hi Stef-- > > > Just out of curiosity on which version is based Squeak 4. > > Squeak 3.2? > > Well, that question is mostly meaningless when so much is > removed. :) The most recent significant thing in there is support > for weak references, which I think comes from 3.2. The VMs are all > the latest, though. > > > -C

Oct. 2, 2008

Re: [Pharo-project] A .mcz of Pinesoft's accumulatedfixesapplicableto Pharo

by Gary Chambers

Indeed. I've poked around a bit and it doesn't pick up stuff in image for new packages it would seem. Only changes for previous versions of the package being merged. I think it looks possible to change it to do so though! Gary. ----- Original Message ----- From: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> To: "An open mailing list to discuss any topics related to an open-sourceSmalltalk" <pharo-project(a)lists.gforge.inria.fr> Sent: Thursday, October 02, 2008 11:27 AM Subject: Re: [Pharo-project] A .mcz of Pinesoft's accumulatedfixesapplicableto Pharo > Ok I think that this is a MC "bug" > > Stef > On Oct 2, 2008, at 11:12 AM, Gary Chambers wrote: > >> Though that seems to make no difference... >> >> Gary >> ----- Original Message ----- From: "Gary Chambers" >> <gazzaguru2(a)btinternet.com >> > >> To: "An open mailing list to discuss any topics related to anopen- >> sourceSmalltalk" <pharo-project(a)lists.gforge.inria.fr> >> Sent: Thursday, October 02, 2008 10:06 AM >> Subject: Re: [Pharo-project] A .mcz of Pinesoft's accumulated >> fixesapplicableto Pharo >> >> >>> Hi Stef, my fault. The override methods are not categorised properly, >>> I'll fix and send a gain if you like. >>> >>> Gary. >> >> _______________________________________________ >> 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

Oct. 2, 2008

Re: [Pharo-project] A .mcz of Pinesoft's accumulated fixesapplicableto Pharo

by StÃ©phane Ducasse

Ok I think that this is a MC "bug" Stef On Oct 2, 2008, at 11:12 AM, Gary Chambers wrote: > Though that seems to make no difference... > > Gary > ----- Original Message ----- From: "Gary Chambers" <gazzaguru2(a)btinternet.com > > > To: "An open mailing list to discuss any topics related to anopen- > sourceSmalltalk" <pharo-project(a)lists.gforge.inria.fr> > Sent: Thursday, October 02, 2008 10:06 AM > Subject: Re: [Pharo-project] A .mcz of Pinesoft's accumulated > fixesapplicableto Pharo > > >> Hi Stef, my fault. The override methods are not categorised >> properly, I'll fix and send a gain if you like. >> >> Gary. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Oct. 2, 2008

Re: [Pharo-project] A .mcz of Pinesoft's accumulated fixesapplicableto Pharo

by Gary Chambers

Though that seems to make no difference... Gary ----- Original Message ----- From: "Gary Chambers" <gazzaguru2(a)btinternet.com> To: "An open mailing list to discuss any topics related to anopen-sourceSmalltalk" <pharo-project(a)lists.gforge.inria.fr> Sent: Thursday, October 02, 2008 10:06 AM Subject: Re: [Pharo-project] A .mcz of Pinesoft's accumulated fixesapplicableto Pharo > Hi Stef, my fault. The override methods are not categorised properly, I'll > fix and send a gain if you like. > > Gary. >

Oct. 2, 2008

Re: [Pharo-project] A .mcz of Pinesoft's accumulated fixes applicableto Pharo

by Gary Chambers

Hi Stef, my fault. The override methods are not categorised properly, I'll fix and send a gain if you like. Gary. ----- Original Message ----- From: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> To: "An open mailing list to discuss any topics related to an open-sourceSmalltalk" <pharo-project(a)lists.gforge.inria.fr> Sent: Sunday, September 28, 2008 8:12 AM Subject: Re: [Pharo-project] A .mcz of Pinesoft's accumulated fixes applicableto Pharo Hi simon This is what I meant. I wanted to understand the problem because when we merge this is important to see the diff. stef On Sep 27, 2008, at 10:07 PM, Simon Kirk wrote: > Hmm, OK, I've had a dig around. > > I tried with a Pharo0.1-10074-oneclick package, and I think I see what > you mean: viewing changes via the MC browser on the package I attached > simply shows the entire method in red - even though if I go and find the > equivalent method in the image it exists and should be showing changes > instead. > > I then tried with a Pharo0.1-PolymorphTT package, as I'm more familiar > with the diff tool from Gary's work. Again, the same problem. > > However, if I load the MCZ into the package, then pick, say, > BrowserCommentTextMorph>>#hidePane and view the versions of the method, I > can then see both the original method (sd 11/20/2005 21:26) and Gary's > new version, and the differences between the two. > > So, perhaps the problem is that the Monticello browser can't show you > differences between methods when one method is in the image under one > class category, while the one in the Monticello package to be loaded is > under a different one (the method in this case is an extension, so the > method category for #hidePane would change from "displaying" to > "*Pinesoft-Fixes-Misc" > > I hope that makes sense. I would have thought you would want to keep the > original method categories, just keeping the method source from the MCZ. > > Unfortunately my knowledge of managing such changes falls well short of > knowing how to go about that :( > > Hope this has all made sense and is helpful > Cheers, > S > > On 27 Sep 2008, at 06:58, StÃ©phane Ducasse wrote: > >> >> On Sep 26, 2008, at 10:07 PM, Simon Kirk wrote: >> >>> hi Stef. >>> >>> Hmm, strange. How are you viewing the diffs? If I browse the MCZ in a >>> Monticello browser I see extensions to these classes: >>> >>> BrowserCommentTextMorph >>> BrowserRequestor >>> CanvasCharacterScanner >>> Character >>> ConnectionQueue >>> GrafPort >>> MultiCanvasCharacterScanner >>> NaturalLanguageTranslator >>> Random >>> RemoteString >>> TranscriptStream >>> >>> Is this the diffs you're talking about? If so, I think they're correct. >>> It's possible my rough list below may have missed some changes. >> >> >> I see the same but I cannot see the diff between the changes and what is >> in the image (for example in the merge >> tools I do not (changed) and the like. >> >> Stef >> >>> >>> >>> Cheers, >>> Simon >>> >>> On 26 Sep 2008, at 20:20, StÃ©phane Ducasse wrote: >>> >>>> Simon >>>> >>>> with which machine did you create you mcz? >>>> Because apparently I can see the diffs for other packages. >>>> >>>> Can somebody else check the pinesoft package I put in the pharoInbox? >>>> >>>> Stef >>>> >>>> >>>> >>>>> Hi all. >>>>> >>>>> Gary and I decided we ought to give out an MCZ of our fixes that >>>>> we've put together over the last two years. >>>>> >>>>> Obviously some of those we found have been pulled into Pharo already, >>>>> but the attached MCZ represents those that we think are still >>>>> relevant :) >>>>> >>>>> This is a rough list of the fixes: >>>>> >>>>> 1. Fixed flaky borwser comment text area sometime not showing. >>>>> >>>>> 2. Added getArgumentPermutation to support RefactoringEngine. >>>>> >>>>> 3. Fixes to CanvasCharacterScanner and MultiCanvasCharacterScanner to >>>>> correctly align the first line of text when centered/justifed etc. >>>>> >>>>> 4. Added more constant names to Character class. >>>>> >>>>> 5. Modified ConnectionQueue to not accept connections when queue is >>>>> full. >>>>> >>>>> 6. Changed GrafPort to answer a MultiDisplayScanner when appropriate >>>>> (allows subclasses of MultiNewParagraph). >>>>> >>>>> 7. NaturalLanguageTranslator startup postion move to after >>>>> PasteUpMorph since it will show a progress bar. >>>>> >>>>> 8. Fix to Random>>nextInt: to allow large numbers which would be out >>>>> of range if using Floats (as mentioned recently on dev, use of Floats >>>>> is dodgy anyway...) >>>>> >>>>> 9. Changed TranscriptStream>>clear to use a new buffer (was just >>>>> reset which could leave a massive collection). >>>>> >>>>> 10. Changed RemoteString to handle concurrent processes safely. This >>>>> one's particularly interesting: we were load-testing our Seaside app >>>>> here and getting lots of syntax errors when hitting the image with >>>>> around the 20 concurrent processes due to source file access. After >>>>> this change we were hitting it with approximately 500 concurrent >>>>> processes, and the failure was in the Java load tester (it timed >>>>> out). >>>>> >>>>> Hope just submitting a .mcz is OK! :) >>>>> >>>>> Cheers, >>>>> Simon and Gary >>>>> >>>>> >>>>> >>>>> ****************************************************************************************************************************************** >>>>> This email is from Pinesoft Limited. Its contents are confidential to >>>>> the intended recipient(s) at the email address(es) to which it has >>>>> been addressed. It may not be disclosed to or used by anyone other >>>>> than the addressee(s), nor may it be copied in anyway. If received in >>>>> error, please contact the sender, then delete it from your system. >>>>> Although this email and attachments are believed to be free of virus, >>>>> or any other defect which might affect any computer or IT system into >>>>> which they are received and opened, it is the responsibility of the >>>>> recipient to ensure that they are virus free and no responsibility is >>>>> accepted by Pinesoft for any loss or damage arising in any way from >>>>> receipt or use thereof. >>>>> ******************************************************************************************************************************************* >>>>> >>>>> >>>>> Pinesoft Limited are registered in England, Registered number: >>>>> 2914825. Registered office: 266-268 High Street, Waltham Cross, >>>>> Herts, EN8 7EA >>>>> <Pinesoft-Fixes-Misc-gvc.24.mcz> >>>>> _______________________________________________ >>>>> 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 >>> >>> >>> >>> ****************************************************************************************************************************************** >>> This email is from Pinesoft Limited. Its contents are confidential to >>> the intended recipient(s) at the email address(es) to which it has been >>> addressed. It may not be disclosed to or used by anyone other than the >>> addressee(s), nor may it be copied in anyway. If received in error, >>> please contact the sender, then delete it from your system. Although >>> this email and attachments are believed to be free of virus, or any >>> other defect which might affect any computer or IT system into which >>> they are received and opened, it is the responsibility of the recipient >>> to ensure that they are virus free and no responsibility is accepted by >>> Pinesoft for any loss or damage arising in any way from receipt or use >>> thereof. >>> ******************************************************************************************************************************************* >>> >>> >>> Pinesoft Limited are registered in England, Registered number: 2914825. >>> Registered office: 266-268 High Street, Waltham Cross, Herts, EN8 7EA >>> >>> _______________________________________________ >>> 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 > > > > ******************************************************************************************************************************************* > > This email is from Pinesoft Limited. Its contents are confidential to the > intended recipient(s) at the email address(es) to which it has been > addressed. It may not be disclosed to or used by anyone other than the > addressee(s), nor may it be copied in anyway. If received in error, > please contact the sender, then delete it from your system. Although this > email and attachments are believed to be free of virus, or any other > defect which might affect any computer or IT system into which they are > received and opened, it is the responsibility of the recipient to ensure > that they are virus free and no responsibility is accepted by Pinesoft > for any loss or damage arising in any way from receipt or use thereof. > > ******************************************************************************************************************************************* > > Pinesoft Limited are registered in England, Registered number: 2914825. > Registered office: 266-268 High Street, Waltham Cross, Herts, EN8 7EA > > _______________________________________________ > 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

Oct. 2, 2008