March 2009 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] How to rename a package ?

by Lukas Renggli

Short answer: It is not supported by Monticello. Long answer: By renaming all the categories and protocols (this can be automated using the OB-Refactoring and OB-Regex tools), creating a new package and committing that one. You'll loose the version history and thus the ability to merge. Lukas On Thu, Mar 19, 2009 at 4:41 PM, Alain Plantec <alain.plantec(a)free.fr> wrote: > Thanks > Alain > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Lukas Renggli http://www.lukas-renggli.ch

March 19, 2009

Re: [Pharo-project] just for fun... extensibility of Morphic

by Alexandre Bergel

:-) On 19 Mar 2009, at 15:19, Schwab,Wilhelm K wrote: > Stef, > > I was having a fairly nice day, until I saw this ;) > > Bill > > > > > -----Original Message----- > From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr > ] On Behalf Of StÃ©phane Ducasse > Sent: Thursday, March 19, 2009 8:50 AM > To: Pharo Development > Subject: [Pharo-project] just for fun... extensibility of Morphic > > awesome if you want to add a new handle .... guess what you have to > edit this method :) > > Morph>>balloonHelpTextForHandle: aHandle > "Answer a string providing balloon help for the > given halo handle" > | itsSelector | > itsSelector := aHandle eventHandler firstMouseSelector. > itsSelector == #doRecolor:with: ifTrue: [^ 'Change color']. > itsSelector == #mouseDownInDimissHandle:with: > ifTrue: [^ Preferences preserveTrash > ifTrue: ['Move to trash'] > ifFalse: ['Remove from screen']]. > #(#(#addFullHandles 'More halo handles') #(#addSimpleHandles 'Fewer > halo handles') #(#chooseEmphasisOrAlignment 'Emphasis & alignment') > #(#chooseFont 'Change font') #(#chooseNewGraphicFromHalo 'Choose a new > graphic') #(#chooseStyle 'Change style') #(#dismiss 'Remove') > #(#doDebug:with: 'Debug') #(#doDirection:with: 'Choose forward > direction') #(#doDup:with: 'Duplicate') #(#doMenu:with: 'Menu') > #(#doGrab:with: 'Pick up') #(#editDrawing 'Repaint') > #(#makeNewDrawingWithin 'Paint new object') > #(#mouseDownInCollapseHandle:with: 'Collapse') > #(#mouseDownOnHelpHandle: 'Help') > #(#prepareToTrackCenterOfRotation:with: 'Move object or set center of > rotation') #(#presentViewMenu 'Present the Viewing menu') > #(#startDrag:with: 'Move') #(#startGrow:with: 'Change size') > #(#startRot:with: 'Rotate') #(#startScale:with: 'Change > scale')#(#trackCenterOfRotation:with: 'Set center of rotation') ) > do: [:pair | itsSelector == pair first > ifTrue: [^ pair last]]. > ^ 'unknown halo handle'translated > > _______________________________________________ > 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 > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

March 19, 2009

[Pharo-project] How to rename a package ?

by Alain Plantec

Thanks Alain

March 19, 2009

Re: [Pharo-project] Customization of registration mechanisms

by StÃ©phane Ducasse

I agree now we could do it in a second step. I'm really curious to see alain code integrated. On Mar 19, 2009, at 3:38 PM, Michael Rueger wrote: > Hi all, > > in light of recent discussions about preferences/settings and menu > registration I would like a favorite issue I have with all automagic > mechanisms: how to customize them. > > For sake of argument imagine loading a vastly enhanced (bloated ;-) ) > version of my Yaxo XML package, having setting pragmas or menu > registration adding "try to parse as xml", "pretty print to xml" or > other "useful" items to menus and a couple of equally useful > settings to > the settings. > > If I now want to not have these items show up in my menus or in the > settings editor, how do I do this without editing code, thus > creating a > fork of the package? > > In Sophie the content of menus was explicitly configured (not in a > nice > way, but nevertheless) in a preference/external xml file. > > Basically what I am suggesting is that regardless of how the automagic > registration works, there needs to be a way to override it somewhere, > preferably through some setting entries. > > Comments? Ideas? Suggestions? > > Michael > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

March 19, 2009

Re: [Pharo-project] Fwd: [ANN] 10254

by StÃ©phane Ducasse

gary could you check that and remove this overrides in polymorph. Stef On Mar 19, 2009, at 1:46 PM, Henrik Johansen wrote: > I know, which is why I thought it was strange, the .cs contained: > !BorderedMorph removeSelector: #areasRemainingToFill:! > which when I file it in, results in no areasRemainingToFill: method > for > BorderedMorph in the image. > > I really have no idea how the update process makes it revert to an > older > version instead, nor how one would go about fixing it... :/ > > Cheers, > Henrik > > StÃ©phane Ducasse wrote: >> >> >> henrik I just integrated the file you gave me. >> If you have a new version that fixes the problem I will do a new >> version. >> >> Stef >> >> On Mar 19, 2009, at 12:20 PM, Henrik Johansen wrote: >> >>> It seems BorderedMorph's areasRemainingToFill: method got reverted >>> to >>> the version in use prior to the override by PolyMorph (which has now >>> been promoted to Morph), instead of removed completely. >>> (This is the state my image is in after updating a released 248, at >>> least) >>> >>> Cheers, >>> Henry >>> >>> StÃ©phane Ducasse wrote: >>>> Issue 655: Overlapping Graphics on World do not Properly Repaint >>>> Issue 658: Preferences resetHaloSpecifications >>>> Issue 664: unimplemented errorCantGoBack >>>> Closed 665 >>>> >>>> now we will focus on the closures. >>>> >>>> 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 > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

March 19, 2009

[Pharo-project] Customization of registration mechanisms

by Michael Rueger

Hi all, in light of recent discussions about preferences/settings and menu registration I would like a favorite issue I have with all automagic mechanisms: how to customize them. For sake of argument imagine loading a vastly enhanced (bloated ;-) ) version of my Yaxo XML package, having setting pragmas or menu registration adding "try to parse as xml", "pretty print to xml" or other "useful" items to menus and a couple of equally useful settings to the settings. If I now want to not have these items show up in my menus or in the settings editor, how do I do this without editing code, thus creating a fork of the package? In Sophie the content of menus was explicitly configured (not in a nice way, but nevertheless) in a preference/external xml file. Basically what I am suggesting is that regardless of how the automagic registration works, there needs to be a way to override it somewhere, preferably through some setting entries. Comments? Ideas? Suggestions? Michael

March 19, 2009

Re: [Pharo-project] just for fun... extensibility of Morphic

by Schwab,Wilhelm K

Stef, I was having a fairly nice day, until I saw this ;) Bill -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of StÃ©phane Ducasse Sent: Thursday, March 19, 2009 8:50 AM To: Pharo Development Subject: [Pharo-project] just for fun... extensibility of Morphic awesome if you want to add a new handle .... guess what you have to edit this method :) Morph>>balloonHelpTextForHandle: aHandle "Answer a string providing balloon help for the given halo handle" | itsSelector | itsSelector := aHandle eventHandler firstMouseSelector. itsSelector == #doRecolor:with: ifTrue: [^ 'Change color']. itsSelector == #mouseDownInDimissHandle:with: ifTrue: [^ Preferences preserveTrash ifTrue: ['Move to trash'] ifFalse: ['Remove from screen']]. #(#(#addFullHandles 'More halo handles') #(#addSimpleHandles 'Fewer halo handles') #(#chooseEmphasisOrAlignment 'Emphasis & alignment') #(#chooseFont 'Change font') #(#chooseNewGraphicFromHalo 'Choose a new graphic') #(#chooseStyle 'Change style') #(#dismiss 'Remove') #(#doDebug:with: 'Debug') #(#doDirection:with: 'Choose forward direction') #(#doDup:with: 'Duplicate') #(#doMenu:with: 'Menu') #(#doGrab:with: 'Pick up') #(#editDrawing 'Repaint') #(#makeNewDrawingWithin 'Paint new object') #(#mouseDownInCollapseHandle:with: 'Collapse') #(#mouseDownOnHelpHandle: 'Help') #(#prepareToTrackCenterOfRotation:with: 'Move object or set center of rotation') #(#presentViewMenu 'Present the Viewing menu') #(#startDrag:with: 'Move') #(#startGrow:with: 'Change size') #(#startRot:with: 'Rotate') #(#startScale:with: 'Change scale')#(#trackCenterOfRotation:with: 'Set center of rotation') ) do: [:pair | itsSelector == pair first ifTrue: [^ pair last]]. ^ 'unknown halo handle'translated _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

March 19, 2009

[Pharo-project] Issue 668: should clean the option-World click menu

by StÃ©phane Ducasse

From: stÃ©phane ducasse <ducasse(a)iam.unibe.ch> Date: March 19, 2009 3:13:40 PM CEST To: Pharo Development <Pharo-project(a)lists.gforge.inria.fr> Subject: Issue 668: should clean the option-World click menu Issue 668: should clean the option-World click menu http://code.google.com/p/pharo/issues/detail?id=668 Apparently option-click on the world brings a new menu (which points to crappy stuff) and to the new pharo menu.

March 19, 2009

[Pharo-project] Registration mechanism need for menuWorld and dockingBar

by StÃ©phane Ducasse

http://code.google.com/p/pharo/issues/list?thanks=669

March 19, 2009

Re: [Pharo-project] UIManager>>request: does not send ProvideAnswerNotification anymore

by Damien Cassou

On Mon, Mar 2, 2009 at 11:35 AM, Damien Cassou <damien.cassou(a)gmail.com> wrote: > it seems that calling #request: does not trigger a > ProvideAnswerNotification. This notification is used by > #valueSuppressingMessages:supplyingAnswers: to automatically fill text > requests. > > Can somebody check that? > > [UIManager default request: 'Please choose a username for\the > application ' withCRs , 'config' printString] > Â Â Â Â Â Â Â Â valueSuppressingMessages: Array new supplyingAnswers: > (Array with: (Array with: '.*username.*' with: 'admin')) It seems #confirm: have the same problem. Could you please fix that too: [UIManager default confirm: 'blah blah'] valueSupplyingAnswers: {{'blah blah' . true}}. Opens a dialog but should just return true directly. Bye -- Damien Cassou http://damiencassou.seasidehosting.st

March 19, 2009