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

Re: [Pharo-project] removing the DockingBar and TheWorldMainDockingBar

by StÃ©phane Ducasse

Another one :) Cleaning the inspector. Stef

Sept. 20, 2008

Re: [Pharo-project] removing the DockingBar and TheWorldMainDockingBar

by StÃ©phane Ducasse

Version 2 On Sep 20, 2008, at 10:07 PM, StÃ©phane Ducasse wrote: > first one of a long series. > I will go over all the extensions of gary removal and slowly removed > them all and check the senders. > Please have a look. > > > "Change Set: removalIsUniClass > Date: 20 September 2008 > Author: Stephane.Ducasse > > Remove isUniClass and fix senders. > Note that for senders that were defined in Etoy I just removed > their body" > > > <EtoyRemoval-001-removalIsUniClass. > 1.cs>_______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 20, 2008

Re: [Pharo-project] Interesting post about Smalltalk and the effect of success (sorry for those who already saw this on Squeak Dev)

by StÃ©phane Ducasse

Hi simon Why did you post this here. Because we forked? Sorry but we had to. Stef > Hi all - as I said in my subject, I've already posted this on Squeak- > Dev, but I thought those on here who don't subscribe to that list > might be interested, too: > > http://www.robvens.nl/en/blog/The-Smalltalk-Trap.html > > Cheers, > Simon > > > ******************************************************************************************************************************************* > > 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

Sept. 20, 2008

Re: [Pharo-project] Interesting post about Smalltalk and the effect of success (sorry for those who already saw this on Squeak Dev)

by StÃ©phane Ducasse

I think that this is not like that that he will really bring smalltalk back. Concertation is equals to death. Have a look at Squeak. Stef PS: a good friend of mine once told me: "do not shit where you eat" and I keep that in mind even when cleaning squeak. I know that this more difficult to build things than to clean them. Still I would not let this blog out there because it will not produce anything positive, just scared more people from Smalltalk. > Hi all - as I said in my subject, I've already posted this on Squeak- > Dev, but I thought those on here who don't subscribe to that list > might be interested, too: > > http://www.robvens.nl/en/blog/The-Smalltalk-Trap.html > > Cheers, > Simon > > > ******************************************************************************************************************************************* > > 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

Sept. 20, 2008

Re: [Pharo-project] removing the DockingBar and TheWorldMainDockingBar

by StÃ©phane Ducasse

first one of a long series. I will go over all the extensions of gary removal and slowly removed them all and check the senders. Please have a look. "Change Set: removalIsUniClass Date: 20 September 2008 Author: Stephane.Ducasse Remove isUniClass and fix senders. Note that for senders that were defined in Etoy I just removed their body"

Sept. 20, 2008

[Pharo-project] Interesting post about Smalltalk and the effect of success (sorry for those who already saw this on Squeak Dev)

by Simon Kirk

Hi all - as I said in my subject, I've already posted this on Squeak- Dev, but I thought those on here who don't subscribe to that list might be interested, too: http://www.robvens.nl/en/blog/The-Smalltalk-Trap.html Cheers, Simon ****************************************************************************************************************************************** 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

Sept. 20, 2008

Re: [Pharo-project] removing the DockingBar and TheWorldMainDockingBar

by StÃ©phane Ducasse

I could produce some changeset going over gary removal. Let me know. This is too much fun to finally remove etoy. Stef On Sep 20, 2008, at 9:28 PM, Marcus Denker wrote: > > On 20.09.2008, at 21:20, StÃ©phane Ducasse wrote: > >> Hi gary >> >> to relax from real men work (fixing my house :), I was browsing >> your package. >> I would like to know what is the semantics of self flag: #toRemove >> why did you keep the method in general do we have to look at the >> senders? >> > > another question is if it's really good to use monticello for the > removal... if we load it, > it moves all overrides into the removal-override category. These we > then would have to re-categorize > by hand. > > Maybe for a change like this, a changeset might be better... > > Marcus > >> Stef >> >> >>> Hi Stef. >>> >>> Been busy with work-work so haven't had time to review the EToys >>> removal. There are some methods identified that have not been >>> verified for removal vs. modification, but I've attached the mcz >>> here anyway. >>> >>> There are a few removals in TheWorldMainDockingBar in the etoys >>> removals, no mods there. >>> >>> The DockingBarMorph is, however, used in Polymorph for toolbars. >>> There is a potential conflict in Project>>finalEnterActions that >>> is defined in both Polymorph and EToysRemoval, the EToysRemoval >>> version should work with Polymorph though (based on Polymorph >>> version with an additional removal of "world presenter >>> positionStandardPlayer"). This will cause problems when updating >>> Polymorph though, until I get some time to split off the overrides >>> into a separate package. >>> >>> As for Etoys removal, the package contains changed methods and >>> stubs (flagged for removal). There are some manual steps required >>> to get rid of extra cruft (mostly preferences and scripting forms). >>> >>> Regards, 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: Friday, September 12, 2008 4:59 PM >>> Subject: [Pharo-project] removing the DockingBar and >>> TheWorldMainDockingBar >>> >>> >>>> Hi all >>>> >>>> I was ready to remove the novice mode and I think that we should >>>> remove DockingBar and TheWorldMainDockingBar >>>> Now gary it may introduce conflicts with etoy removal. >>>> What do you think? >>>> When will you send us the etoy removal? >>>> >>>> Stef >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> Pharo-project(a)lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> <Pinesoft-Removals-EToys-gvc. >>> 6.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 > > -- > Marcus Denker -- denker(a)iam.unibe.ch > http://www.iam.unibe.ch/~denker > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Sept. 20, 2008

Re: [Pharo-project] removing the DockingBar and TheWorldMainDockingBar

by Marcus Denker

On 20.09.2008, at 21:20, StÃ©phane Ducasse wrote: > Hi gary > > to relax from real men work (fixing my house :), I was browsing your > package. > I would like to know what is the semantics of self flag: #toRemove > why did you keep the method in general do we have to look at the > senders? > another question is if it's really good to use monticello for the removal... if we load it, it moves all overrides into the removal-override category. These we then would have to re-categorize by hand. Maybe for a change like this, a changeset might be better... Marcus > Stef > > >> Hi Stef. >> >> Been busy with work-work so haven't had time to review the EToys >> removal. There are some methods identified that have not been >> verified for removal vs. modification, but I've attached the mcz >> here anyway. >> >> There are a few removals in TheWorldMainDockingBar in the etoys >> removals, no mods there. >> >> The DockingBarMorph is, however, used in Polymorph for toolbars. >> There is a potential conflict in Project>>finalEnterActions that is >> defined in both Polymorph and EToysRemoval, the EToysRemoval >> version should work with Polymorph though (based on Polymorph >> version with an additional removal of "world presenter >> positionStandardPlayer"). This will cause problems when updating >> Polymorph though, until I get some time to split off the overrides >> into a separate package. >> >> As for Etoys removal, the package contains changed methods and >> stubs (flagged for removal). There are some manual steps required >> to get rid of extra cruft (mostly preferences and scripting forms). >> >> Regards, 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: Friday, September 12, 2008 4:59 PM >> Subject: [Pharo-project] removing the DockingBar and >> TheWorldMainDockingBar >> >> >>> Hi all >>> >>> I was ready to remove the novice mode and I think that we should >>> remove DockingBar and TheWorldMainDockingBar >>> Now gary it may introduce conflicts with etoy removal. >>> What do you think? >>> When will you send us the etoy removal? >>> >>> Stef >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> <Pinesoft-Removals-EToys-gvc. >> 6.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 -- Marcus Denker -- denker(a)iam.unibe.ch http://www.iam.unibe.ch/~denker

Sept. 20, 2008

Re: [Pharo-project] removing the DockingBar and TheWorldMainDockingBar

by StÃ©phane Ducasse

Hi gary to relax from real men work (fixing my house :), I was browsing your package. I would like to know what is the semantics of self flag: #toRemove why did you keep the method in general do we have to look at the senders? Stef > Hi Stef. > > Been busy with work-work so haven't had time to review the EToys > removal. There are some methods identified that have not been > verified for removal vs. modification, but I've attached the mcz > here anyway. > > There are a few removals in TheWorldMainDockingBar in the etoys > removals, no mods there. > > The DockingBarMorph is, however, used in Polymorph for toolbars. > There is a potential conflict in Project>>finalEnterActions that is > defined in both Polymorph and EToysRemoval, the EToysRemoval version > should work with Polymorph though (based on Polymorph version with > an additional removal of "world presenter positionStandardPlayer"). > This will cause problems when updating Polymorph though, until I get > some time to split off the overrides into a separate package. > > As for Etoys removal, the package contains changed methods and stubs > (flagged for removal). There are some manual steps required to get > rid of extra cruft (mostly preferences and scripting forms). > > Regards, 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: Friday, September 12, 2008 4:59 PM > Subject: [Pharo-project] removing the DockingBar and > TheWorldMainDockingBar > > >> Hi all >> >> I was ready to remove the novice mode and I think that we should >> remove DockingBar and TheWorldMainDockingBar >> Now gary it may introduce conflicts with etoy removal. >> What do you think? >> When will you send us the etoy removal? >> >> Stef >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > <Pinesoft-Removals-EToys-gvc. > 6.mcz>_______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 20, 2008

[Pharo-project] allUnsentMessages fix

by StÃ©phane Ducasse

looking at issue http://code.google.com/p/pharo/issues/detail?id=178&colspec=ID%20Type%20Sta… I saw that allUnsentMessages implementation is wrong it should be. Behavior>> allUnsentMessages "Answer an array of all the messages defined by the receiver that are not sent anywhere in the system." ^ SystemNavigation default allUnSentMessagesIn: self selectors Stef

Sept. 20, 2008