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

[Pharo-project] Removing a trait from a class

by Hilaire Fernandes

I can't remove a trait from a class using UI tools. (pharo 10050) How can I remove it programmatically ? Next with this same class, message from this trait are not reachable, the MNU is raised but the hierarchy is not right as IFIETayage1 is not a subclass of IFIExoMorph. However IFIExoMorph is using the same trait as IFIEtayage. It looks like there is mismatch in the classes with traits. (see screenshot) Now I realize my last istoa release suffer from this problem :) Hilaire -- http://blog.ofset.org/hilaire

Dec. 2, 2008

Re: [Pharo-project] [update] #10185

by StÃ©phane Ducasse

Ok this is true that we can load it after. >>> Installer was loaded by accident when I loaded Polymorph. It was >>> not there before we loaded Polymoph. > And it added a bunch of undfined references to classes not there. Ah this should be fixed. >

Dec. 2, 2008

Re: [Pharo-project] UIMananger

by StÃ©phane Ducasse

The problem is that I'm scared about this global variable. Stef > Do you all think it might be a good idea to extend the UIManager > protocol to include things like colour pickers (and other, like > print etc.)? > I'm sure we can all think of things that would be desirable as > standard "utility" dialogs. Best to get the interface in early to > ensure adoption. > > Regards, Gary. > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Dec. 2, 2008

Re: [Pharo-project] Issue 364 & 365

by StÃ©phane Ducasse

salut francois est-ce que tu peux signer la license et me l'envoyer :) Stef On Dec 1, 2008, at 2:15 PM, Francois Stephany wrote: > Hi, > > I've got those two DNU (issue 364 and 365) when playing with the > latest Pharo-dev. As they do not appear in Pharo-core, should i send > my patches to pharo-inbox ? > > Thanks, > > > Francois > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Dec. 2, 2008

Re: [Pharo-project] free fonts

by StÃ©phane Ducasse

+1 On Nov 30, 2008, at 4:39 PM, David Mitchell wrote: > Please don't include any font with ambiguous licensing! Wouldn't want > to bring back a fonts clause to the license! > > On Sun, Nov 30, 2008 at 5:33 AM, Adrian Lienhard <adi(a)netstyle.ch> > wrote: >> >> On Nov 30, 2008, at 10:35 , StÃ©phane Ducasse wrote: >> >>> http://www.pinvoke.com/font/ >>> >>> I think that for the demo mode we should get a better font since >>> italic "" >>> is not working well. >> >> Yes, and not only for the demo font, but *all* default fonts should >> be >> reconsidered now that we have the machinery in place. >> >> I don't think that the fonts of www.pinvoke.com/font/ are >> particularly well >> suited. >> >> From a mail I sent on September 22, considering the code font I >> wrote: >> >> I think Bitstream Vera Sans Mono would be quite good. >> I slightly prefer Monaco, which is shipped with OS X, but I don't >> know its >> license (http://en.wikipedia.org/wiki/Monaco_(typeface)) >> >> For an evaluation of programmer fonts see http://www.lowing.org/ >> fonts/ >> Another list can be found here: >> http://wiki.macromates.com/Main/AlternativeFonts >> The latter list, for example includes >> http://www.ms-studio.com/FontSales/anonymous.html which looks nice >> too. >> >> Adrian >> >> >>> >>> Now it would be great to have a set of free font for pharo. >>> >>> stef >>> >>> _______________________________________________ >>> 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 >> > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Dec. 2, 2008

Re: [Pharo-project] About ecompletion

by StÃ©phane Ducasse

How Program History Can Improve Code Completion Romain Robbes ~ Michele Lanza ASE 2008 (12% acceptance) ~ to appear ~ IEEE CS, 2008 his pageweb is not up to date I can send you his Phd On Dec 1, 2008, at 12:50 PM, Damien Cassou wrote: > On Sun, Nov 30, 2008 at 7:16 PM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> I wanted to share that with you. I'm reading the PhD of Romain >> Robbes and >> he has an excellent chapter on measuring different strategies for >> code >> completion. >> One of the best algorithm is to keep a list with the recently >> modified >> methods >> and the messages they send. >> >> His benchmark shows a drastic improvement even compared with >> ecompletion >> with RoelTyper. >> >> So david do you store the recently modified methods globally for >> all the >> browsers? >> Is it easily accessible? >> >> He also mentioned that we get even better results by combining >> RoelTyper and then this approach... any taker? this is important to >> have >> much better >> editing tools. > > I guess Romain already did something to be able to compare the > results. Where is his work? > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Dec. 2, 2008

Re: [Pharo-project] [update] #10185

by Marcus Denker

On 02.12.2008, at 10:41, StÃ©phane Ducasse wrote: > > > why do you unload Installer? >> -- unloads packages: Installer, 39Deprecated, FlexibleVocablaries, >> Pinesoft-Removals-EToys, ToolBuilder-MVC > > Because I think that this is important to have it. May be a small > version: Installer and MCInstaller? > > amazing.... when I see all the stuff that was in there... > Installer was loaded by accident when I loaded Polymorph. It was not there before we loaded Polymoph. And it added a bunch of undfined references to classes not there. Marcus > >> >> -- remove preferences #timeStampsInMenuTitles >> #personalizedWorldMenu #abbreviatedBrowserButtons >> >> Here is a full list of removals: >> -------------------------------- >> FileList2, Everything from Installer* >> Smalltalk removeClassNamed: #Vocabulary! >> Smalltalk removeClassNamed: #BOBTransformationMorph! >> >> TilePadMorph removeSelector: #prepareToUndoDropOf:! >> TileMorph removeSelector: #scriptEdited! >> TilePadMorph removeSelector: #addCustomMenuItems:hand:! >> TilePadMorph removeSelector: #restoreDefaultTile! >> TilePadMorph removeSelector: #setToBearDefaultLiteral! >> TilePadMorph removeSelector: #setType:! >> TileMorph removeSelector: #slotName! >> StandardScriptingSystem removeSelector: #colorForType:! >> Slider removeSelector: #wantsSlot! >> SimpleHierarchicalListMorph removeSelector: #installModelIn:! >> PluggableTextMorph removeSelector: #installModelIn:! >> PluggableListMorph removeSelector: #installModelIn:! >> ScrollPane removeSelector: #wantsSlot! >> BlobMorph removeSelector: #installModelIn:! >> PolygonMorph removeSelector: #installModelIn:! >> PasteUpMorph removeSelector: #abandonVocabularyPreference! >> MorphicModel removeSelector: #compileAccessForSlot:! >> MorphicModel removeSelector: #compilePropagationMethods! >> MorphicModel removeSelector: #initString! >> MorphicModel removeSelector: #installModelIn:! >> MorphicModel removeSelector: #recomputeBounds! >> MorphicModel removeSelector: #slotName! >> MorphicModel removeSelector: #slotSelectorFor:! >> MorphicModel removeSelector: #wantsSlot! >> HandMorph removeSelector: #addKeyboardListener:! >> HandMorph removeSelector: #checkForMoreKeyboard! >> HandMorph removeSelector: #generateWindowEvent:! >> HandMorph removeSelector: #isCapturingGesturePoints! >> HandMorph removeSelector: #keyboardListeners:! >> HandMorph removeSelector: #removeKeyboardListener:! >> HandMorph removeSelector: #targetOffset:! >> Morph removeSelector: #altSpecialCursor3! >> Morph removeSelector: #beThisWorldsModel! >> Morph removeSelector: #choosePartName! >> Morph removeSelector: #imageFormWithout:andStopThere:! >> Morph removeSelector: #inAScrollPane! >> Morph removeSelector: #initString! >> Morph removeSelector: #installModelIn:! >> Morph removeSelector: #isModalShell! >> Morph removeSelector: #morphReport! >> Morph removeSelector: #morphReportFor:! >> Morph removeSelector: #morphReportFor:on:indent:! >> Morph removeSelector: #nameInModel! >> Morph removeSelector: #obtrudesBeyondContainer! >> Morph removeSelector: #okayToExtractEasily! >> Morph removeSelector: #textToPaste! >> Morph removeSelector: #yellowButtonGestureDictionaryOrName:! >> Preferences class removeSelector: #chooseInsertionPointColor! >> Preferences class removeSelector: #chooseKeyboardFocusColor! >> ColorTheme class removeSelector: #apply! >> ColorTheme class removeSelector: #applyTheme:! >> ColorTheme class removeSelector: #current:! >> ColorTheme class removeSelector: #defaultTheme! >> ColorTheme removeSelector: #apply! >> ColorTheme removeSelector: #balloonColor! >> ColorTheme removeSelector: #dark:! >> ColorTheme removeSelector: #defaultWorldColor! >> ColorTheme removeSelector: #dialogTextBoxBorderColor! >> ColorTheme removeSelector: #dialogTextBoxColor! >> ColorTheme removeSelector: #initialize! >> ColorTheme removeSelector: #insertionPointColor! >> ColorTheme removeSelector: #keyboardFocusColor! >> ColorTheme removeSelector: #labelForColor:! >> ColorTheme removeSelector: #light:! >> ColorTheme removeSelector: #textHighlightColor! >> CodeHolder removeSelector: #abbreviatedWordingFor:! >> Preferences class removeSelector: #abbreviatedBrowserButtons! >> Preferences class removeSelector: #chooseEToysFont! >> Preferences class removeSelector: #chooseEToysTitleFont! >> Preferences class removeSelector: #letUserPersonalizeMenu! >> Preferences class removeSelector: #personalizeUserMenu:! >> Preferences class removeSelector: #personalizedWorldMenu! >> Preferences class removeSelector: #timeStampsInMenuTitles! >> PasteUpMorph removeSelector: #yellowButtonClickOnDesktopWithEvent:! >> >> >> -- >> 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 >> > > > _______________________________________________ > 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

Dec. 2, 2008

Re: [Pharo-project] some analyses

by StÃ©phane Ducasse

> >> Hi guys >> >> if you want to help simply. >> Once etoy methods are removed from Morph, Object, PasteUpMorph >> we will not rush and remove Etoy before we need to identify in Etoy >> the reference >> >> made to MorphicExtras classes since some of them are etoyonly. >> So if you have a little script I accept it :). >> > > In addition, we should try to hunt down more unsent messages... > there are very many of > those everwhere. Yes but unsent messages are not wrong per se. So we should go slowly. stef

Dec. 2, 2008

Re: [Pharo-project] some analyses

by StÃ©phane Ducasse

yes >> Hi guys >> >> if you want to help simply. >> Once etoy methods are removed from Morph, Object, PasteUpMorph >> we will not rush and remove Etoy before we need to identify in Etoy >> the >> reference >> made to MorphicExtras classes since some of them are etoyonly. >> So if you have a little script I accept it :). >> > > do , you mean something like following: > > SomeClass allReferencesInMethodsDo: [:method | > self assert: ( method belongsToClassThatBelongsTo: #Etoys ) > ] > > ? > >> Stef >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > -- > Best regards, > Igor Stasenko AKA sig. > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Dec. 2, 2008

Re: [Pharo-project] Bug when loading Seaside in 10178

by StÃ©phane Ducasse

still this is strange to invoke a comparison between MCDefinition and World :) On Dec 1, 2008, at 9:06 AM, Damien Cassou wrote: > On Sun, Nov 30, 2008 at 4:43 PM, Gary Chambers > <gazzaguru2(a)btinternet.com> wrote: >> Finding the modal morph is quite tricky (requests for a dialog not >> specifically being tied to a system window), hence the trick! >> Clearly a few cases I missed... >> Will have a look. > > I think it is a bug with Monticello which does not check the parameter > of the #= method. I fixed that in PharoInbox. > > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Dec. 2, 2008