[Pharo-dev] [pharo-project/pharo-core] 0cac45: 30745

[GitHub]

  Branch: refs/heads/3.0
  Home:   https://github.com/pharo-project/pharo-core
  Commit: 0cac45ba5324163103cea3ff7220e9d8d37599ac
  
https://github.com/pharo-project/pharo-core/commit/0cac45ba5324163103cea3ff7220e9d8d37599ac
  Author: Jenkins Build Server 
  Date:   2014-02-05 (Wed, 05 Feb 2014)

  Changed paths:
M Gofer-Core.package/GoferBrowseLocalChanges.class/README.md
M Gofer-Core.package/GoferBrowseRemoteChanges.class/README.md
M Gofer-Core.package/GoferChanges.class/README.md
M Gofer-Core.package/GoferCleanup.class/README.md
M Gofer-Core.package/GoferCommit.class/README.md
M Gofer-Core.package/GoferFetch.class/README.md
M Gofer-Core.package/GoferLoad.class/README.md
M Gofer-Core.package/GoferLocalChanges.class/README.md
M Gofer-Core.package/GoferMerge.class/README.md
M Gofer-Core.package/GoferOperation.class/README.md
M Gofer-Core.package/GoferPush.class/README.md
M Gofer-Core.package/GoferRecompile.class/README.md
M Gofer-Core.package/GoferRemoteChanges.class/README.md
M Gofer-Core.package/GoferRevert.class/README.md
M Gofer-Core.package/GoferSynchronize.class/README.md
M Gofer-Core.package/GoferUnload.class/README.md
M Gofer-Core.package/GoferUpdate.class/README.md
M Gofer-Core.package/GoferWorking.class/README.md
M Gofer-Tests.package/GoferApiTest.class/README.md
M Gofer-Tests.package/GoferOperationTest.class/README.md
M Gofer-Tests.package/GoferReferenceTest.class/README.md
M Gofer-Tests.package/GoferResource.class/README.md
M Gofer-Tests.package/GoferTest.class/README.md
M KernelTests.package/AdditionalMethodStateTest.class/README.md
M KernelTests.package/BehaviorTest.class/README.md
M KernelTests.package/BlockClosureTest.class/README.md
M KernelTests.package/ClassHierarchyTest.class/README.md
R KernelTests.package/ClassHierarchyTest.class/instance/as yet 
unclassified/testSubclassInstVar.st
R KernelTests.package/ClassHierarchyTest.class/instance/as yet 
unclassified/testSubclasses.st
A 
KernelTests.package/ClassHierarchyTest.class/instance/tests/testSubclassInstVar.st
A 
KernelTests.package/ClassHierarchyTest.class/instance/tests/testSubclasses.st
M KernelTests.package/ClassTest.class/README.md
M KernelTests.package/CodeSimulationTests.class/README.md
R KernelTests.package/CollectionCombinator.class/instance/as yet 
unclassified/combineFromIdx_.st
R KernelTests.package/CollectionCombinator.class/instance/as yet 
unclassified/forArrays_processWith_.st
A 
KernelTests.package/CollectionCombinator.class/instance/operating/combineFromIdx_.st
A 
KernelTests.package/CollectionCombinator.class/instance/operating/forArrays_processWith_.st
M KernelTests.package/CompiledMethodTrailerTest.class/README.md
M KernelTests.package/DateAndTimeDosEpochTest.class/README.md
M KernelTests.package/DateAndTimeTest.class/README.md
M KernelTests.package/DateAndTimeUnixEpochTest.class/README.md
R KernelTests.package/DatePrintFormatTester.class/instance/as yet 
unclassified/printFormat.st
A 
KernelTests.package/DatePrintFormatTester.class/instance/printing/printFormat.st
M KernelTests.package/ExampleForTest1.class/README.md
M KernelTests.package/ExampleForTest11.class/README.md
M KernelTests.package/ExampleForTest111.class/README.md
M KernelTests.package/ExampleForTest112.class/README.md
M KernelTests.package/ExampleForTest12.class/README.md
M KernelTests.package/ExceptionTester.class/README.md
M KernelTests.package/ExceptionTests.class/README.md
M KernelTests.package/FalseTest.class/README.md
R KernelTests.package/FloatTest.class/instance/IEEE 
754/test32bitGradualUnderflow.st
R KernelTests.package/FloatTest.class/instance/IEEE 
754/test32bitRoundingMode.st
R KernelTests.package/FloatTest.class/instance/IEEE 754/testNaN5.st
R KernelTests.package/FloatTest.class/instance/NaN behavior/testNaN1.st
R KernelTests.package/FloatTest.class/instance/NaN behavior/testNaN2.st
R KernelTests.package/FloatTest.class/instance/NaN behavior/testNaN3.st
R KernelTests.package/FloatTest.class/instance/NaN behavior/testNaN4.st
R KernelTests.package/FloatTest.class/instance/NaN 
behavior/testNaNCompare.st
R KernelTests.package/FloatTest.class/instance/NaN 
behavior/testNaNisLiteral.st
R KernelTests.package/FloatTest.class/instance/NaN 
behavior/testReciprocal.st
R KernelTests.package/FloatTest.class/instance/as yet 
unclassified/testFractionAsFloatWithUnderflow.st
R 
KernelTests.package/FloatTest.class/instance/characterization/testCharacterization.st
R KernelTests.package/FloatTest.class/instance/infinity 
behavior/testHugeIntegerCloseTo.st
R KernelTests.package/FloatTest.class/instance/infinity 
behavior/testInfinity1.st
R KernelTests.package/FloatTest.class/instance/infinity 
behavior/testInfinity2.st
R KernelTests.package/FloatTest.class/instance/infinity 
behavior/testI

[Pharo-dev] [pharo-project/pharo-core]

[GitHub]

  Branch: refs/tags/30745
  Home:   https://github.com/pharo-project/pharo-core

Re: [Pharo-dev] Hello

[Ron Teitelbaum]

Nice to meet you Lorenzo!

All the best,

Ron Teitelbaum

> -Original Message-
> From: Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] On Behalf Of
> Lorenzo Baracchi
> Sent: Wednesday, February 05, 2014 10:43 AM
> To: pharo-dev@lists.pharo.org
> Subject: [Pharo-dev] Hello
> 
> Hello,
> I write this message only to introduce myself. I am Lorenzo Baracchi and
> currently I am working on my MSc thesis at the University of Lugano in the
> REVEAL research group.
> I am new to Pharo and Smalttalk, thus I will probably asks some question
here!
> 
> Cheers
>  Lorenzo
> 

Re: [Pharo-dev] Hello

[Alexandre Bergel]

Welcome!!!

Alexandre


On Feb 5, 2014, at 12:43 PM, Lorenzo Baracchi  
wrote:

> Hello,
> I write this message only to introduce myself. I am Lorenzo Baracchi and 
> currently I am working on my MSc thesis at the University of Lugano in the 
> REVEAL research group.
> I am new to Pharo and Smalttalk, thus I will probably asks some question here!
> 
> Cheers
>Lorenzo
> 

-- 
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Re: [Pharo-dev] Shortcuts

[Pharo4Stef]

Agreed!
Now it requires work to migrate the old tools with hadrocded shortcuts.

Stef


On 05 Feb 2014, at 16:33, Sean P. DeNigris  wrote:

> sebast...@flowingconcept.com wrote
>> For your UX rejoice
>> #not
> 
> Yes, I find the new shortcuts especially confusing because they are not
> universal. This is a disaster for muscle memory. e.g. in Nautilus method
> pane, cmd+b,v browses versions of the method, but if the source pane has
> focus, it selects the current line (thinking it's a cmd+b, even though cmd
> is still pressed), then (unless you happen to be on a line with only a Class
> name) it replaces the selected line with the contents of the clipboard.
> 
> I think Diego's suggestion is brilliant - after a partial shortcut has been
> typed, give visual feedback on possible completions.
> 
> 
> 
> -
> Cheers,
> Sean
> --
> View this message in context: 
> http://forum.world.st/Shortcuts-tp4741703p4741740.html
> Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
> 

Re: [Pharo-dev] Hello

[Pharo4Stef]

Welcome and feel with to ask any question you want. 
BTW on what topic are you working?

Stef
On 05 Feb 2014, at 16:43, Lorenzo Baracchi  wrote:

> Hello,
> I write this message only to introduce myself. I am Lorenzo Baracchi and 
> currently I am working on my MSc thesis at the University of Lugano in the 
> REVEAL research group.
> I am new to Pharo and Smalttalk, thus I will probably asks some question here!
> 
> Cheers
>Lorenzo
> 

Re: [Pharo-dev] OpalCompiler and Semantic analyzer

[Clément Bera]

Arf you are too fast to fix bugs we don't have time to review :-)

I guess Marcus or I will have a look friday afternoon, if possible before.

Regards.


2014-02-05 Nicolai Hess :

> 2014-02-03 Nicolai Hess :
>
> Can someone with some background knowledget on the opal compiler,
>> look at my fix for issue 12442.
>>
>> It seems to work, but I don't like it.
>>
>> There were 2 problems with OCUnusedVariableWarning, removing unused temps:
>> 1. Removes the RBTemporaryNode and updates the source text but does
>> not correct the sourcetext offset of the remaining nodes.
>> 2. Removed temporaries are left in the methodnode/blocknode scope
>>
>> One additional issue, if you have removed all temporaries, the two bars
>> from the empty variable declaration still there
>>
>>
>> nicolai
>>
>
>
> Now we have 3 Opal Compiler related bugs waiting for a review:
>
> 12442 Nautilus brakes code when removing more than one unused local
> variables
> 12512 SemanticAnalyzer ignores answer from UnknownSelectorWarning
> 12514 OCSemanticWarnings ignore "cancel" from a confirmation dialog
>
> please report back if you find any issues in the bug fixes.
>
>
> regards
> Nicolai
>
>

Re: [Pharo-dev] OpalCompiler and Semantic analyzer

[Nicolai Hess]

2014-02-03 Nicolai Hess :

> Can someone with some background knowledget on the opal compiler,
> look at my fix for issue 12442.
>
> It seems to work, but I don't like it.
>
> There were 2 problems with OCUnusedVariableWarning, removing unused temps:
> 1. Removes the RBTemporaryNode and updates the source text but does
> not correct the sourcetext offset of the remaining nodes.
> 2. Removed temporaries are left in the methodnode/blocknode scope
>
> One additional issue, if you have removed all temporaries, the two bars
> from the empty variable declaration still there
>
>
> nicolai
>


Now we have 3 Opal Compiler related bugs waiting for a review:

12442 Nautilus brakes code when removing more than one unused local
variables
12512 SemanticAnalyzer ignores answer from UnknownSelectorWarning
12514 OCSemanticWarnings ignore "cancel" from a confirmation dialog

please report back if you find any issues in the bug fixes.


regards
Nicolai

[Pharo-dev] R: Hello

[Lorenzo Schiavina]

Benissimo!

Lorenzo

-Messaggio originale-
Da: Pharo-dev [mailto:pharo-dev-boun...@lists.pharo.org] Per conto di
Lorenzo Baracchi
Inviato: mercoledì 5 febbraio 2014 16:43
A: pharo-dev@lists.pharo.org
Oggetto: [Pharo-dev] Hello

Hello,
I write this message only to introduce myself. I am Lorenzo Baracchi and
currently I am working on my MSc thesis at the University of Lugano in the
REVEAL research group.
I am new to Pharo and Smalttalk, thus I will probably asks some question
here!

Cheers
 Lorenzo

Re: [Pharo-dev] Shortcuts

[Sebastian Sastre]

On Feb 5, 2014, at 1:33 PM, Sean P. DeNigris  wrote:

> sebast...@flowingconcept.com wrote
>> For your UX rejoice
>> #not
> 
> Yes, I find the new shortcuts especially confusing because they are not
> universal. This is a disaster for muscle memory.

I’m adding to my dictionary the expression: 
Muscle memory disaster

Quite appropriate

Please correct me if I’m wrong… the problem I think is originated by the lack 
of key combination detection so what we have now is a clever workaround for the 
real deal.

I really hope we could get it right as really productive apps do

Re: [Pharo-dev] Hello

[Marcus Denker]

On 05 Feb 2014, at 16:43, Lorenzo Baracchi  wrote:

> Hello,
> I write this message only to introduce myself. I am Lorenzo Baracchi and 
> currently I am working on my MSc thesis at the University of Lugano in the 
> REVEAL research group.
> I am new to Pharo and Smalttalk, thus I will probably asks some question here!
> 

Welcome!

Marcus

[Pharo-dev] Hello

[Lorenzo Baracchi]

Hello,
I write this message only to introduce myself. I am Lorenzo Baracchi and 
currently I am working on my MSc thesis at the University of Lugano in 
the REVEAL research group.
I am new to Pharo and Smalttalk, thus I will probably asks some question 
here!


Cheers
Lorenzo

Re: [Pharo-dev] Shortcuts

[Sean P. DeNigris]

sebast...@flowingconcept.com wrote
> For your UX rejoice
> #not

Yes, I find the new shortcuts especially confusing because they are not
universal. This is a disaster for muscle memory. e.g. in Nautilus method
pane, cmd+b,v browses versions of the method, but if the source pane has
focus, it selects the current line (thinking it's a cmd+b, even though cmd
is still pressed), then (unless you happen to be on a line with only a Class
name) it replaces the selected line with the contents of the clipboard.

I think Diego's suggestion is brilliant - after a partial shortcut has been
typed, give visual feedback on possible completions.



-
Cheers,
Sean
--
View this message in context: 
http://forum.world.st/Shortcuts-tp4741703p4741740.html
Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

[Pharo-dev] Smalltalk job

[Clément Bera]

Hiring now! Searching for a Smalltalk Developer - 6 month (renewable)
contract with a major direct client in Omaha Nebraska! Call or email
Natalie Wharton: # 630.465.7833 nwhar...@cssus.net

Major qualifications,
* 3+ years of Smalltalk, preferably VisualWorks
* 3+ years of relational database, either MS SQL or Oracle
* Good problem solving skill - a fast learner
* Good communication skills - able to conduct production support
interacting with customers


From:

Natalie 
WhartonSenior
Technical Recruiter

Re: [Pharo-dev] Shortcuts

[J.F. Rick]

I actually just reported this bug to FogBugz today. Try doing it twice in a
row and see if that gets you what you want. If so, that matches my
experience on Ubuntu. Investigating a bit further, it seems that ctrl and
command are different for different platforms. Try doing alt-f and see if
that works. It could be that we are using the wrong modifier. It is strange
that both modifiers work for do it or print it but not for find.

Cheers,

Jeff


On Wed, Feb 5, 2014 at 2:26 PM, Diego Lont  wrote:

> Hi all,
>
> I am probably a stupid user, but I cannot use the new short-cuts that are
> default everywhere. Because currently when I press crtl-x or crtl-f,
> nothing happens, so I assume they are broken.
>
> I have learned that when I type a short-cut, this should give visual
> feedback. So when I press crtl-x (or cmd-x on my mac), I would expect a
> visual aid that tells me what I can delete. class xxx, method yyy, etc.
> This way I hope I can find my shortcuts again.
>
> Diego
>



-- 
Jochen "Jeff" Rick, Ph.D.
http://www.je77.com/
Skype ID: jochenrick

[Pharo-dev] [pharo-project/pharo-core] c9f9e0: 30744

[GitHub]

  Branch: refs/heads/3.0
  Home:   https://github.com/pharo-project/pharo-core
  Commit: c9f9e0d3abde52a50398efff74083cc9c316ac00
  
https://github.com/pharo-project/pharo-core/commit/c9f9e0d3abde52a50398efff74083cc9c316ac00
  Author: Jenkins Build Server 
  Date:   2014-02-05 (Wed, 05 Feb 2014)

  Changed paths:
A Deprecated30.package/FTPConnectionException.class/README.md
A Deprecated30.package/FTPConnectionException.class/definition.st
A Deprecated30.package/FTPConnectionException.class/instance/as yet 
unclassified/defaultAction.st
A Deprecated30.package/FTPConnectionException.class/instance/as yet 
unclassified/isResumable.st
R Network-Protocols.package/FTPConnectionException.class/README.md
R Network-Protocols.package/FTPConnectionException.class/definition.st
R Network-Protocols.package/FTPConnectionException.class/instance/as yet 
unclassified/defaultAction.st
R Network-Protocols.package/FTPConnectionException.class/instance/as yet 
unclassified/isResumable.st
M Polymorph-Widgets.package/AnimationSettings.class/README.md
M Polymorph-Widgets.package/BlueUIThemeIcons.class/README.md
M Polymorph-Widgets.package/NullSound.class/README.md
M Polymorph-Widgets.package/NullSoundTheme.class/README.md
M Polymorph-Widgets.package/PharoUIThemeIcons.class/README.md
M Polymorph-Widgets.package/ShadowLabelMorph.class/README.md
M Polymorph-Widgets.package/UIThemeRegistry.class/README.md
M Polymorph-Widgets.package/UIThemeWatery.class/README.md
A ScriptLoader30.package/ScriptLoader.class/instance/pharo - 
scripts/script397.st
A ScriptLoader30.package/ScriptLoader.class/instance/pharo - 
updates/update30744.st
M 
ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st
M Spec-Debugger.package/EyeDebuggerContextInspector.class/definition.st

  Log Message:
  ---
  30744
12808 #testObsoleteClasses: AnObsoleteEyeContextInspector
https://pharo.fogbugz.com/f/cases/12808

12817 Class comments missing for Polymorph-Widgets package
https://pharo.fogbugz.com/f/cases/12817

12814 FTPConnectionException is not in use and should be moved to Deprecated30 
package or renamed
https://pharo.fogbugz.com/f/cases/12814

http://files.pharo.org/image/30/30744.zip

Re: [Pharo-dev] Shortcuts

[Sebastian Sastre]

If nothing happens check what you’re focusing because they are contextual

Also, I’ve found out that some of them had timing requirements which is 
surprisingly creative

For example:

In Nautilus, the menu that shows:

Senders of…   b,n

for some reason it’s supposed to mean: 

1. press cmd
2. keep it down 
3. press and release b
4. press and release n
5. you can release cmd now

For your UX rejoice

#not





On Feb 5, 2014, at 11:26 AM, Diego Lont  wrote:

> Hi all,
> 
> I am probably a stupid user, but I cannot use the new short-cuts that are 
> default everywhere. Because currently when I press crtl-x or crtl-f, nothing 
> happens, so I assume they are broken.
> 
> I have learned that when I type a short-cut, this should give visual 
> feedback. So when I press crtl-x (or cmd-x on my mac), I would expect a 
> visual aid that tells me what I can delete. class xxx, method yyy, etc. This 
> way I hope I can find my shortcuts again. 
> 
> Diego

[Pharo-dev] [pharo-project/pharo-core]

[GitHub]

  Branch: refs/tags/30744
  Home:   https://github.com/pharo-project/pharo-core

Re: [Pharo-dev] Shortcuts

[Stephan Eggermont]

After typing cmd-x, we get a kind of modal behavior: cmd-m does something else 
than before we typed cmd-x. This should be visible in the UI. In a class 
browser we could highlight which method, class, package would be removed when 
the relevant keys were to be pressed, or the title/status bar of the window 
with selection should show the mode, or a popup could be shown with the 
possible actions.

Stephan

Re: [Pharo-dev] missing variable names in context inspector (from issue 12800?)

[Marcus Denker]

On 05 Feb 2014, at 15:08, Sven Van Caekenberghe  wrote:

> And there is an obsolete instance …
> 
yes, the reason has to be that when  class gets renamed that the packages are 
renamed that something is not correctly done
with the subclass… or maybe it happens on load of the package that something is 
not done correctly?
Will look into that later… I will fix the obsolete later today .

Marcus

Re: [Pharo-dev] missing variable names in context inspector (from issue 12800?)

[Sven Van Caekenberghe]

And there is an obsolete instance ...

On 05 Feb 2014, at 15:03, Nicolai Hess  wrote:

> Since the update 30742 , the context inspector (in a Debugger window)
> shows only a list of numbers instead of that contexts variable names.
> 
> 
> Nicolai

[Pharo-dev] missing variable names in context inspector (from issue 12800?)

[Nicolai Hess]

Since the update 30742 , the context inspector (in a Debugger window)
shows only a list of numbers instead of that contexts variable names.


Nicolai

Re: [Pharo-dev] Shortcuts

[Sven Van Caekenberghe]

Hi Diego,

What platform are you on ?
In what tool do the shortcuts fail ?
Everything seems to work as expected for me on Mac OS X, #30742.

Sven

On 05 Feb 2014, at 14:26, Diego Lont  wrote:

> Hi all,
> 
> I am probably a stupid user, but I cannot use the new short-cuts that are 
> default everywhere. Because currently when I press crtl-x or crtl-f, nothing 
> happens, so I assume they are broken.
> 
> I have learned that when I type a short-cut, this should give visual 
> feedback. So when I press crtl-x (or cmd-x on my mac), I would expect a 
> visual aid that tells me what I can delete. class xxx, method yyy, etc. This 
> way I hope I can find my shortcuts again. 
> 
> Diego

[Pharo-dev] Shortcuts

[Diego Lont]

Hi all,

I am probably a stupid user, but I cannot use the new short-cuts that are 
default everywhere. Because currently when I press crtl-x or crtl-f, nothing 
happens, so I assume they are broken.

I have learned that when I type a short-cut, this should give visual feedback. 
So when I press crtl-x (or cmd-x on my mac), I would expect a visual aid that 
tells me what I can delete. class xxx, method yyy, etc. This way I hope I can 
find my shortcuts again. 

Diego

Re: [Pharo-dev] test failures in downloaded image 30733

[Goubier Thierry]

Le 05/02/2014 12:05, Usman Bhatti a écrit :

I see and I've been achieving it in another way.

aClass >> export
fileRef := UITheme builder
fileSave: 'Choose a file'
extensions: #('txt')
path: nil.
fileRef isNil ifFalse: [
self exportOn: fileRef writeStream
]

Instead of testing the method export, I test exportOn: with a stream as
a parameter.
What I am thinking is that, with this approach, we are not testing all
the execution paths in the method export. But then, with a Shim, we will
not be testing that path either.


No, it would be different with a Shim: you could test two times this 
code, one with a nil answer, and another one with a fileReference answer.


You would do something like:

{nil. 'aPath'} do: [:d |
[ aShim setAsUITheme.
aShim preload: #fileSave:extension:path: withAnswer: d.
aClass export ]
ensure: [ aShim reset ]
]

And hop, your paths are covered.

Thierry
--
Thierry Goubier
CEA list
Laboratoire des Fondations des Systèmes Temps Réel Embarqués
91191 Gif sur Yvette Cedex
France
Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95

Re: [Pharo-dev] test failures in downloaded image 30733

[Usman Bhatti]

On Tue, Feb 4, 2014 at 10:01 AM, Goubier Thierry wrote:

>
>
> Le 04/02/2014 09:48, Usman Bhatti a écrit :
>
>>
>>
>>
>> On Tue, Feb 4, 2014 at 9:29 AM, Goubier Thierry > > wrote:
>>
>>
>>
>> Le 04/02/2014 09:23, Usman Bhatti a écrit :
>>
>>
>>
>>
>> Yes, I use that already with Glamour and Roassal, and other morph
>> widgets that I have.
>> The harder part for me so far is responding to dialog boxes e.g.
>> answer
>> the user questions automatically and once I have that, I'd be
>> able to
>> completely test my current set of UIs automatically.
>>
>>
>> What about writing a Shim over the dialog creator with a catalog of
>> predefined answers that could be picked by each dialog creation?
>> When calling a dialog, we're usually going through a factory
>> interface usually.
>>
>>
>> I do not know what is a Shim.
>>
>
> From Wikipedia:
>
> In computer programming, a shim (from shim) or shiv is a small library
> that transparently intercepts an API and changes the parameters passed,
> handles the operation itself, or redirects the operation elsewhere.


Tx for this info. I was not aware of it and it is surprising for me because
half of my doctoral thesis was about AOP and related concepts, and Shim
seems to be a very similar concept, in its definition, to AOP.

>
>
>  Sometimes, we would like to provide our own answers to the dialogue to
>> see if the tests pass in different configurations (e.g. when we have two
>> or more checkboxes, to see if we get different results selecting
>> different boxes).
>>
>> Or may be we can start with a simpler solution and then evolve towards a
>> completely customizable one.
>>
>
> My simple approach would be :
>
> in normal code, instead of calling UIManager directly as in:
>
> UIManager default chooseFrom: aCollection title: aString withCRs.
>
> use a shim (self class myUIManager ). In the test case, setup so that:
>
> `self class myUIManager` returns a shim over UIManager capturing the
> chooseFrom:title: and containing a dictionary with 'title' -> value to
> choose. You preload the shim with the right answers and the keys for the
> shim to find to which dialog this refers (it could be ordered: answer for
> first dialog, answer for second dialog, etc...). The shim, instead of
> creating the dialog, returns the value it already has (or an error if it
> hasn't, which will help you fill the needed values !).
>
> For stuff not related to dialogs you are using the shim for, you can just
> do a passthrough (i.e. UIManager default perform: ) which can even be
> handled automagically via doesNotUnderstand:.
>
> As you can see, there isn't much to it.


I see and I've been achieving it in another way.

aClass >> export
fileRef := UITheme builder
fileSave: 'Choose a file'
extensions: #('txt')
path: nil.
fileRef isNil ifFalse: [
self exportOn: fileRef writeStream
 ]

Instead of testing the method export, I test exportOn: with a stream as a
parameter.
What I am thinking is that, with this approach, we are not testing all the
execution paths in the method export. But then, with a Shim, we will not be
testing that path either.

Usman


>
>
> Thierry
> --
> Thierry Goubier
> CEA list
> Laboratoire des Fondations des Systèmes Temps Réel Embarqués
> 91191 Gif sur Yvette Cedex
> France
> Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95
>
>

Re: [Pharo-dev] comments :)

[Torsten Bergmann]

Still 1017 to go. Feel free to help:
 
   Smalltalk allClasses select: [:each | each comment includesSubstring: '' 
]
 
External Package owners should also reintegrate too so these do not
get lost when a new version of external packages get integrated.
(for instance https://pharo.fogbugz.com/f/cases/12812 for Spec)

step by step it goes ...
 
Bye
T.
 

Gesendet: Mittwoch, 05. Februar 2014 um 08:36 Uhr
Von: Pharo4Stef 
An: "Pharo Development List" 
Betreff: [Pharo-dev] comments :)

Thanks for all these comments!
 

On 05 Feb 2014, at 00:27, GitHub  wrote: 30742
12794 Class comments missing in UpdateStreamer package
https://pharo.fogbugz.com/f/cases/12794[https://pharo.fogbugz.com/f/cases/12794]

12802 Class comments missing for Kernel package
https://pharo.fogbugz.com/f/cases/12802[https://pharo.fogbugz.com/f/cases/12802]

12804 Class comment missing in AST packages
https://pharo.fogbugz.com/f/cases/12804[https://pharo.fogbugz.com/f/cases/12804]

12797 Class comments missing for tools package
https://pharo.fogbugz.com/f/cases/12797[https://pharo.fogbugz.com/f/cases/12797]

12796 Class comments missing for Traits package
https://pharo.fogbugz.com/f/cases/12796[https://pharo.fogbugz.com/f/cases/12796]

12798 Class comments missing in GroupManager package
https://pharo.fogbugz.com/f/cases/12798[https://pharo.fogbugz.com/f/cases/12798]

12806 Class comment missing in package FreeType + categorizing for 
FreeTypeCacheTest
https://pharo.fogbugz.com/f/cases/12806[https://pharo.fogbugz.com/f/cases/12806]

12800 EyeContextInspector should be renamed to EyeMethodContextInspector
https://pharo.fogbugz.com/f/cases/12800[https://pharo.fogbugz.com/f/cases/12800]