- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Pharo Refactoring Tool

by Alexandre Bergel

> Some really useful refactorings are: > > - extract setUp method (this one is missing in all IDE's). Write a test with no setup, and then you want to take the initialisation of a variable at the top of a method and move it to a test setup method (possibly extracting an instance variable as well). > > - extract sub-component (or delegate or policy) - eg. extract out a method into another class and call it via an instance variable (eg. delegate behavior) > > - extract to local variable, and inline local variable are also very common eclipsy things that we seem to miss at a local method level in smalltalk as well Oh yes! There is a whole range of useful refactorings for unit tests that I would love to have. - Cutting a unit test in two. For example, moving a method category into a new unit test - Structure unit tests along the hierarchy of the tested classes - extract the setUp, tearDown, and resources In general, there is research field about unit tests that is here to explore: - reducing the duplication between unit tests - reducing the redundancy in tests (do I test twice the same thing?) - if I want to test a method, where should I start? By writing a new unit test or extending an existing one? - Having a button 'generate test' in the pre-debugger, to be sure that an error will never happen - ... Here, at the UChile, we are particularly interested in these issues. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Jan. 20, 2011

Re: [Pharo-project] Pharo Refactoring Tool

by TimM

ashubair(a)scs.ryerson.ca wrote: > should consider. My starting point is to bring Pharo up to the level of > Eclipse > (seehttp://help.eclipse.org/helios/index.jsp?topic=/org.eclipse.jdt.doc.user… > ) but I would love to hear from experienced Smalltalkers about > refactorings that are important to them. A reasonable equivalence with eclipse would be awesome (Ideally, if you can find some time to observe java developers using Intelli-J - you really say how they play the IDE like a piano). We are often too mouse-y in Smalltalk, but we don't have to be (its been great seeing some of the keyboard shortcuts introduced in Pharo). Some really useful refactorings are: - extract setUp method (this one is missing in all IDE's). Write a test with no setup, and then you want to take the initialisation of a variable at the top of a method and move it to a test setup method (possibly extracting an instance variable as well). - extract sub-component (or delegate or policy) - eg. extract out a method into another class and call it via an instance variable (eg. delegate behavior) - extract to local variable, and inline local variable are also very common eclipsy things that we seem to miss at a local method level in smalltalk as well Tim

Jan. 19, 2011

Re: [Pharo-project] ConfigurationOf Question

by Dale Henrichs

On 01/19/2011 01:24 PM, StÃ©phane Ducasse wrote: > hi guys > > what should be the load or loadDefault definition if I want to load the latest version as defined by a method of this style? > > version02: spec > > <version: '0.2'> > spec for: #common do: [ spec repository: 'http://www.squeaksource.com/Soup'. > spec > package: 'Soup-Core' with: 'Soup-Core-StephaneDucasse.8'; > package: 'Soup-Tests-Core' with: 'Soup-Tests-Core-StephaneDucasse.2'; > package: 'Soup-Help' with: 'Soup-Help-StephaneDucasse.2' ]. > > > AM I correct to believe that > > load > "self load" > > ^self project latestVersion load > > execute version02: if this is the last method version? > > Stef Stef, Yes that is correct. #latestVersion filters out versions with #baseline, #broken, or #development blessings... Dale

Jan. 19, 2011

Re: [Pharo-project] Issue 3557 in pharo: [Feature]: Setting for "easy select" i.e. selecting in the world by dragging

by pharo＠googlecode.com

Comment #1 on issue 3557 by sean.p.d...(a)gmail.com: [Feature]: Setting for "easy select" i.e. selecting in the world by dragging http://code.google.com/p/pharo/issues/detail?id=3557 Fix in inbox: SLICE-Issue-3557-Feature-Setting-for-easy-select-ie-selecting-in-the-world-by-dragging-SeanDeNigris.1 * added world easy selection setting (allows multiple selection like Mac/Windows desktop) * renamed PolymorphSystemSettings class>>morphicAppearanceSettingsOn: to morphicSettingsOn:, because not all of its settings are appearance related so the name was misleading

Jan. 19, 2011

[Pharo-project] Issue 3557 in pharo: [Feature]: Setting for "easy select" i.e. selecting in the world by dragging

by pharo＠googlecode.com

Status: New Owner: ---- New issue 3557 by sean.p.d...(a)gmail.com: [Feature]: Setting for "easy select" i.e. selecting in the world by dragging http://code.google.com/p/pharo/issues/detail?id=3557 WorldState>>easySelectingWorld: allows you to toggle drag-to-select, just like a Mac/Windows desktop; but it's not obvious that it's available

Jan. 19, 2011

Re: [Pharo-project] PluggableTextMorph(Object)>>doesNotUnderstand: #stylerStyled:

by Tudor Girba

I guess this was just for testing different scenarios :) Cheers, Doru On 19 Jan 2011, at 22:55, Alexandre Bergel wrote: > I got bitten by the Shout problem. > But ConfigurationOfMoose automatically loads Petit. Why loading it manually? > > Alexandre > > > On 19 Jan 2011, at 18:49, StÃ©phane Ducasse wrote: > >> alain >> mentioned that in another thread >> >> >> I've the same problem when I load Moose and/or Petit with the following scripts: >> >> Gofer new >> squeaksource: 'Moose'; >> package: 'ConfigurationOfMoose'; >> load. >> (Smalltalk at: #ConfigurationOfMoose) perform: #loadDefault. >> >> Gofer new >> renggli: 'petit'; >> package: 'ConfigurationOfPetitParser'; >> load. >> (Smalltalk at: #ConfigurationOfPetitParser) perform: #loadDefault. >> >> >> >> >> >> On Jan 19, 2011, at 10:43 PM, Alexandre Bergel wrote: >> >>> I do not understand. What can I do to help? >>> >>> Alexandre >>> >>> >>> On 19 Jan 2011, at 18:40, StÃ©phane Ducasse wrote: >>> >>>> Can somebody try by defining these methods >>>> >>>> !PluggableTextMorph methodsFor: 'zork' stamp: 'BenjaminVanRyseghem 11/25/2010 15:35'! >>>> stylerStyled: styledCopyOfText >>>> >>>> textMorph contents runs: styledCopyOfText runs . >>>> "textMorph paragraph recomposeFrom: 1 to: textMorph contents size delta: 0." "caused chars to appear in wrong order esp. in demo mode. remove this line when sure it is fixed" >>>> textMorph updateFromParagraph. >>>> selectionInterval >>>> ifNotNil:[ >>>> textMorph editor >>>> selectInvisiblyFrom: selectionInterval first to: selectionInterval last; >>>> storeSelectionInParagraph; >>>> setEmphasisHere]. >>>> textMorph editor blinkParen. >>>> self scrollSelectionIntoView >>>> ! ! >>>> >>>> !PluggableTextMorph methodsFor: 'zork' stamp: 'BenjaminVanRyseghem 11/25/2010 15:35'! >>>> stylerStyledInBackground: styledCopyOfText >>>> "It is possible that the text string has changed since the styling began. Disregard the styles if styledCopyOfText's string differs with the current textMorph contents string" >>>> >>>> textMorph contents string = styledCopyOfText string >>>> ifTrue: [self stylerStyled: styledCopyOfText]! ! >>>> >>>> >>>> >>>> I think that we found a bug in MC since the category where named: 'shout' (not with * so that the changes do not belong to the package of shout but really the one of PluggableTextMorph. >>>> >>>> >>>> On Jan 19, 2011, at 10:34 PM, StÃ©phane Ducasse wrote: >>>> >>>>>>> PluggableTextMorph(Object)>>doesNotUnderstand: #stylerStyled: >>>>> >>>>> >>>>> this is probably with a MC problem because in >>>>> Issue 3486: PluggableTextMorph should be able to support text styling >>>>> >>>>> we payed attention to have it. >>>>> http://code.google.com/p/pharo/issues/detail?id=3486 >>>>> >>>>> Benjamin can you have a look? >>>>> >>>>> Stef >>>>> >>>> >>>> >>> >>> -- >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> Alexandre Bergel http://www.bergel.eu >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >>> >>> >>> >>> >> >> > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > -- www.tudorgirba.com "What is more important: To be happy, or to make happy?"

Jan. 19, 2011

Re: [Pharo-project] PluggableTextMorph(Object)>>doesNotUnderstand: #stylerStyled:

by Alexandre Bergel

I got bitten by the Shout problem. But ConfigurationOfMoose automatically loads Petit. Why loading it manually? Alexandre On 19 Jan 2011, at 18:49, StÃ©phane Ducasse wrote: > alain > mentioned that in another thread > > > I've the same problem when I load Moose and/or Petit with the following scripts: > > Gofer new > squeaksource: 'Moose'; > package: 'ConfigurationOfMoose'; > load. > (Smalltalk at: #ConfigurationOfMoose) perform: #loadDefault. > > Gofer new > renggli: 'petit'; > package: 'ConfigurationOfPetitParser'; > load. > (Smalltalk at: #ConfigurationOfPetitParser) perform: #loadDefault. > > > > > > On Jan 19, 2011, at 10:43 PM, Alexandre Bergel wrote: > >> I do not understand. What can I do to help? >> >> Alexandre >> >> >> On 19 Jan 2011, at 18:40, StÃ©phane Ducasse wrote: >> >>> Can somebody try by defining these methods >>> >>> !PluggableTextMorph methodsFor: 'zork' stamp: 'BenjaminVanRyseghem 11/25/2010 15:35'! >>> stylerStyled: styledCopyOfText >>> >>> textMorph contents runs: styledCopyOfText runs . >>> "textMorph paragraph recomposeFrom: 1 to: textMorph contents size delta: 0." "caused chars to appear in wrong order esp. in demo mode. remove this line when sure it is fixed" >>> textMorph updateFromParagraph. >>> selectionInterval >>> ifNotNil:[ >>> textMorph editor >>> selectInvisiblyFrom: selectionInterval first to: selectionInterval last; >>> storeSelectionInParagraph; >>> setEmphasisHere]. >>> textMorph editor blinkParen. >>> self scrollSelectionIntoView >>> ! ! >>> >>> !PluggableTextMorph methodsFor: 'zork' stamp: 'BenjaminVanRyseghem 11/25/2010 15:35'! >>> stylerStyledInBackground: styledCopyOfText >>> "It is possible that the text string has changed since the styling began. Disregard the styles if styledCopyOfText's string differs with the current textMorph contents string" >>> >>> textMorph contents string = styledCopyOfText string >>> ifTrue: [self stylerStyled: styledCopyOfText]! ! >>> >>> >>> >>> I think that we found a bug in MC since the category where named: 'shout' (not with * so that the changes do not belong to the package of shout but really the one of PluggableTextMorph. >>> >>> >>> On Jan 19, 2011, at 10:34 PM, StÃ©phane Ducasse wrote: >>> >>>>>> PluggableTextMorph(Object)>>doesNotUnderstand: #stylerStyled: >>>> >>>> >>>> this is probably with a MC problem because in >>>> Issue 3486: PluggableTextMorph should be able to support text styling >>>> >>>> we payed attention to have it. >>>> http://code.google.com/p/pharo/issues/detail?id=3486 >>>> >>>> Benjamin can you have a look? >>>> >>>> Stef >>>> >>> >>> >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> >> > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Jan. 19, 2011

Re: [Pharo-project] PluggableTextMorph(Object)>>doesNotUnderstand: #stylerStyled:

by StÃ©phane Ducasse

alain mentioned that in another thread I've the same problem when I load Moose and/or Petit with the following scripts: Gofer new squeaksource: 'Moose'; package: 'ConfigurationOfMoose'; load. (Smalltalk at: #ConfigurationOfMoose) perform: #loadDefault. Gofer new renggli: 'petit'; package: 'ConfigurationOfPetitParser'; load. (Smalltalk at: #ConfigurationOfPetitParser) perform: #loadDefault. On Jan 19, 2011, at 10:43 PM, Alexandre Bergel wrote: > I do not understand. What can I do to help? > > Alexandre > > > On 19 Jan 2011, at 18:40, StÃ©phane Ducasse wrote: > >> Can somebody try by defining these methods >> >> !PluggableTextMorph methodsFor: 'zork' stamp: 'BenjaminVanRyseghem 11/25/2010 15:35'! >> stylerStyled: styledCopyOfText >> >> textMorph contents runs: styledCopyOfText runs . >> "textMorph paragraph recomposeFrom: 1 to: textMorph contents size delta: 0." "caused chars to appear in wrong order esp. in demo mode. remove this line when sure it is fixed" >> textMorph updateFromParagraph. >> selectionInterval >> ifNotNil:[ >> textMorph editor >> selectInvisiblyFrom: selectionInterval first to: selectionInterval last; >> storeSelectionInParagraph; >> setEmphasisHere]. >> textMorph editor blinkParen. >> self scrollSelectionIntoView >> ! ! >> >> !PluggableTextMorph methodsFor: 'zork' stamp: 'BenjaminVanRyseghem 11/25/2010 15:35'! >> stylerStyledInBackground: styledCopyOfText >> "It is possible that the text string has changed since the styling began. Disregard the styles if styledCopyOfText's string differs with the current textMorph contents string" >> >> textMorph contents string = styledCopyOfText string >> ifTrue: [self stylerStyled: styledCopyOfText]! ! >> >> >> >> I think that we found a bug in MC since the category where named: 'shout' (not with * so that the changes do not belong to the package of shout but really the one of PluggableTextMorph. >> >> >> On Jan 19, 2011, at 10:34 PM, StÃ©phane Ducasse wrote: >> >>>>> PluggableTextMorph(Object)>>doesNotUnderstand: #stylerStyled: >>> >>> >>> this is probably with a MC problem because in >>> Issue 3486: PluggableTextMorph should be able to support text styling >>> >>> we payed attention to have it. >>> http://code.google.com/p/pharo/issues/detail?id=3486 >>> >>> Benjamin can you have a look? >>> >>> Stef >>> >> >> > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > >

Jan. 19, 2011

Re: [Pharo-project] PluggableTextMorph(Object)>>doesNotUnderstand: #stylerStyled:

by Alexandre Bergel

I do not understand. What can I do to help? Alexandre On 19 Jan 2011, at 18:40, StÃ©phane Ducasse wrote: > Can somebody try by defining these methods > > !PluggableTextMorph methodsFor: 'zork' stamp: 'BenjaminVanRyseghem 11/25/2010 15:35'! > stylerStyled: styledCopyOfText > > textMorph contents runs: styledCopyOfText runs . > "textMorph paragraph recomposeFrom: 1 to: textMorph contents size delta: 0." "caused chars to appear in wrong order esp. in demo mode. remove this line when sure it is fixed" > textMorph updateFromParagraph. > selectionInterval > ifNotNil:[ > textMorph editor > selectInvisiblyFrom: selectionInterval first to: selectionInterval last; > storeSelectionInParagraph; > setEmphasisHere]. > textMorph editor blinkParen. > self scrollSelectionIntoView > ! ! > > !PluggableTextMorph methodsFor: 'zork' stamp: 'BenjaminVanRyseghem 11/25/2010 15:35'! > stylerStyledInBackground: styledCopyOfText > "It is possible that the text string has changed since the styling began. Disregard the styles if styledCopyOfText's string differs with the current textMorph contents string" > > textMorph contents string = styledCopyOfText string > ifTrue: [self stylerStyled: styledCopyOfText]! ! > > > > I think that we found a bug in MC since the category where named: 'shout' (not with * so that the changes do not belong to the package of shout but really the one of PluggableTextMorph. > > > On Jan 19, 2011, at 10:34 PM, StÃ©phane Ducasse wrote: > >>>> PluggableTextMorph(Object)>>doesNotUnderstand: #stylerStyled: >> >> >> this is probably with a MC problem because in >> Issue 3486: PluggableTextMorph should be able to support text styling >> >> we payed attention to have it. >> http://code.google.com/p/pharo/issues/detail?id=3486 >> >> Benjamin can you have a look? >> >> Stef >> > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Jan. 19, 2011

[Pharo-project] Issue 3556 in pharo: PluggableTextMorph(Object)>>doesNotUnderstand: #stylerStyled:

by pharo＠googlecode.com

Status: Accepted Owner: stephane...(a)gmail.com CC: Benjamin...(a)gmail.com, aplan...(a)gmail.com Labels: Milestone-1.2 New issue 3556 by stephane...(a)gmail.com: PluggableTextMorph(Object)>>doesNotUnderstand: #stylerStyled: http://code.google.com/p/pharo/issues/detail?id=3556 Can somebody try by defining these methods !PluggableTextMorph methodsFor: 'zork' stamp: 'BenjaminVanRyseghem 11/25/2010 15:35'! stylerStyled: styledCopyOfText textMorph contents runs: styledCopyOfText runs . "textMorph paragraph recomposeFrom: 1 to: textMorph contents size delta: 0." "caused chars to appear in wrong order esp. in demo mode. remove this line when sure it is fixed" textMorph updateFromParagraph. selectionInterval ifNotNil:[ textMorph editor selectInvisiblyFrom: selectionInterval first to: selectionInterval last; storeSelectionInParagraph; setEmphasisHere]. textMorph editor blinkParen. self scrollSelectionIntoView ! ! !PluggableTextMorph methodsFor: 'zork' stamp: 'BenjaminVanRyseghem 11/25/2010 15:35'! stylerStyledInBackground: styledCopyOfText "It is possible that the text string has changed since the styling began. Disregard the styles if styledCopyOfText's string differs with the current textMorph contents string" textMorph contents string = styledCopyOfText string ifTrue: [self stylerStyled: styledCopyOfText]! ! I think that we found a bug in MC since the category where named: 'shout' (not with * so that the changes do not belong to the package of shout but really the one of PluggableTextMorph. On Jan 19, 2011, at 10:34 PM, StÃ©phane Ducasse wrote: PluggableTextMorph(Object)>>doesNotUnderstand: #stylerStyled: this is probably with a MC problem because in Issue 3486: PluggableTextMorph should be able to support text styling we payed attention to have it. http://code.google.com/p/pharo/issues/detail?id=3486 Benjamin can you have a look?

Jan. 19, 2011