- Pharo-dev - lists.pharo.org

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

by GitHub

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: c9f9e0d3abde52a50398efff74083cc9c316ac00 https://github.com/pharo-project/pharo-core/commit/c9f9e0d3abde52a50398efff… Author: Jenkins Build Server <board(a)pharo-project.org> 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

Feb. 5, 2014

[pharo-project/pharo-core]

by GitHub

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

Feb. 5, 2014

Re: [Pharo-dev] Shortcuts

by 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

Feb. 5, 2014

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

by Marcus Denker

On 05 Feb 2014, at 15:08, Sven Van Caekenberghe <sven(a)stfx.eu> 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

Feb. 5, 2014

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

by Sven Van Caekenberghe

And there is an obsolete instance ... On 05 Feb 2014, at 15:03, Nicolai Hess <nicolaihess(a)web.de> 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

Feb. 5, 2014

missing variable names in context inspector (from issue 12800?)

by 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

Feb. 5, 2014

Re: [Pharo-dev] Shortcuts

by 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 <diego.lont(a)delware.nl> 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

Feb. 5, 2014

Shortcuts

by 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

Feb. 5, 2014

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

by 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

Feb. 5, 2014

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

by Usman Bhatti

On Tue, Feb 4, 2014 at 10:01 AM, Goubier Thierry <thierry.goubier(a)cea.fr>wrote: > > > Le 04/02/2014 09:48, Usman Bhatti a Ã©crit : > >> >> >> >> On Tue, Feb 4, 2014 at 9:29 AM, Goubier Thierry <thierry.goubier(a)cea.fr >> <mailto:thierry.goubier@cea.fr>> 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 > >

Feb. 5, 2014