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

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

by Igor Stasenko

code sucks ifTrue: ['Move to trash']. :) 2009/3/19 Alexandre Bergel <alexandre(a)bergel.eu>: > :-) > > > 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 > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > 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.

March 19, 2009

Re: [Pharo-project] Composing UI layout question

by Igor Stasenko

2009/3/19 <astares(a)gmx.de>: >>parent width & height (or any other parent coordinate) depends on >>its submorph's fixed width/height. > > Ahh, should have read your mail more carefully. You are not only > interested in a flexible alignment within the parent - but also > to depend on own child bounds/parameters. > There are limitless number of variants, how concrete coordinate can be evaluated and what parameters can take part in it. The parent/child relations is most obvious, but not necessary. > The new JavaFX provides something like this by using the > "bind" keyword. > yes, exactly like this. > See http://weblogs.java.net/blog/aim/archive/2009/01/layout_primer_f.html > in section "Using Binding to Layout Nodes" > > Bye > T. > -- > Psssst! Schon vom neuen GMX MultiMessenger gehÃ¶rt? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger01 > > _______________________________________________ > 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.

March 19, 2009

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

by Henrik Sperre Johansen

Wouldn't it be possible to use the version history to make an algorithm which figures out who's *mostly* responsible though? ;) Cheers, Henry ----- Opprinnelig melding ----- Fra: Michael Rueger <m.rueger(a)acm.org> Sendt: 19. mars 2009 17:19 Til: Pharo-project(a)lists.gforge.inria.fr Emne: Re: [Pharo-project] just for fun... extensibility of Morphic StÃ©phane Ducasse wrote: > lol > I'm not that we want to know. > Some of us could cry to see their idols falling from their statute :) Well, it would also be unfair for those having done maintenance as their initials would be on the method. 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

[Pharo-project] System-Settings

by Alain Plantec

Hi all, here is a new version: - taken into account Adrian remarks - made all part of the Setting-Settings package. - added filtering: by token or by package - added style: a style is represented by a subclass of SettingStyle with a method #load - one can manage user defined style (no need for demo mode, only have to create a style named 'my beautiful demo mode') creating a style consists in creating a subclass of SettingStyle with a class method #styleName and with an instance method #load. Style export and import relies on simple fileout/filein. - the pragma keyword is now a parameter: the default is <setting> as in: desktopColor <setting> ^ DesktopColor ifNil: [DesktopColor := (SettingManager newSetting: 'Desktop color') parent: #desktopColorSettingNode; default: (MessageSend receiver: Color selector: #green)] all standard settings are browsed by 'SettingTree new open' An application or a particular part of the system can use its own keyword. as an example <menu> as in: aSettingAboutMenu <menu> ^ ..... all menu settings would be browsed by 'SettingTree forKeywords: #(#menu) open' I've attached the package System-Settings, SettingSandBox1, SettingSandBox2 for testing and a UserDefinedSettings with a style example. Cheers Alain

March 19, 2009

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

by Michael Rueger

StÃ©phane Ducasse wrote: > lol > I'm not that we want to know. > Some of us could cry to see their idols falling from their statute :) Well, it would also be unfair for those having done maintenance as their initials would be on the method. Michael

March 19, 2009

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

by StÃ©phane Ducasse

lol I'm not that we want to know. Some of us could cry to see their idols falling from their statute :) Stef On Mar 19, 2009, at 5:09 PM, astares(a)gmx.de wrote: > Hey lets build a tool that uses the authors initials in such methods > to find other interesting/horrible places in the image ;) > > Bye > T. > -- > Psssst! Schon vom neuen GMX MultiMessenger gehÃ¶rt? Der kann`s mit > allen: http://www.gmx.net/de/go/multimessenger01 > > _______________________________________________ > 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] How to rename a package ?

by Lukas Renggli

>> Long answer: By renaming all the categories and protocols (this can be >> automated using the OB-Refactoring and OB-Regex tools), creating a new > > Would those support finding orphaned package extensions? Especially with > removing stuff and reorganizing we will have that need occasionally. No, but the following remnant from the Seaside 2.9 packaging effort does: | packages | packages := MCWorkingCopy allManagers collect: [ :each | each packageInfo ]. Smalltalk organization categories do: [ :cat | (packages anySatisfy: [ :pak | pak includesSystemCategory: cat ]) ifFalse: [ Transcript show: 'Category: '; show: cat; cr ] ]. Smalltalk allClassesAndTraitsDo: [ :class | [ :cls | cls organization categories do: [ :cat | (packages anySatisfy: [ :pak | pak includesMethodCategory: cat ofClass: cls ]) ifFalse: [ Transcript show: 'Class: '; show: cls; show: ' Protocol: '; show: cat; cr ] ] ] value: class; value: class class ] Lukas -- Lukas Renggli http://www.lukas-renggli.ch

March 19, 2009

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

by astares＠gmx.de

Hey lets build a tool that uses the authors initials in such methods to find other interesting/horrible places in the image ;) Bye T. -- Psssst! Schon vom neuen GMX MultiMessenger gehÃ¶rt? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger01

March 19, 2009

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

by Michael Rueger

Lukas Renggli wrote: > 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 Would those support finding orphaned package extensions? Especially with removing stuff and reorganizing we will have that need occasionally. Michael

March 19, 2009

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

by Alexandre Bergel

This question raised several times. In a general way, you can't. Cheers, Alexandre On 19 Mar 2009, at 16:41, Alain Plantec 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 > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

March 19, 2009