November 2013 - Pharo-dev - lists.pharo.org

TextModel

by Alexandre Bergel

Hi Ben, We have doubt about the getSelection of TextModel. Execute the following in a Workspace: model := TextModel new. model openWithSpec. In the window, insert some text, and select something. Evaluate the following: model getSelection It always returns (1 to: 0) for us. Do you confirm? https://pharo.fogbugz.com/f/cases/12144/TextModel-getSelection Cheers, Johan Fabry & Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Nov. 11, 2013

about Announcer unsubscribe:

by StÃ©phane Ducasse

HI guys with ronie we were looking at how we can remove update: methods ( fun story) and we found update: aSymbol "Update the image if changed." super update: aSymbol. aSymbol = self getImageSelector ifTrue: [ self updateImage] and here we see that a static self announcer when: #jkhjkh send: #updateImage to: self does not work so we thought that we can change getImageSelector: anObject getImageSelector := anObject into getImageSelector: anObject getImageSelector := anObject. self announcer when: anObject send: #updateImage to: self but this is not nice because we should clean before. Now the problem (and I would like to get your point of viee) is that announcer only define unregister: anObject and the granularity is too large because we do not want to lose all the other resgitrations we did. Tx for your anwsers Stef

Nov. 11, 2013

Re: [Pharo-dev] About MenuItemModel

by Benjamin

Indeed :) Ben On 11 Nov 2013, at 19:17, Camillo Bruni <camillobruni(a)gmail.com> wrote: > #action is most probably a ValueHolder, no? > > On 2013-11-11, at 19:12, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > >> Hi ben >> >> do I get it correctly that we pass a block to a block for action >> >> action: aBlock >> >> action value: aBlock >> >> are you sure that you want a block as argument of a block. >> >> I would prefer that action is simply a block. >> >> Stef >> >

Nov. 11, 2013

Re: [Pharo-dev] Unexpected block variable change of value

by ClÃ©ment Bera

There is a bug left in double nested blocks in the debugger (some variables then shows incorrect value). Retry with the old compiler (world menu>settings>compiler>Compiler) and see if this is fixed. 2013/11/11 Max Leske <maxleske(a)gmail.com> > Not sure if itâs related to your issue but Iâve been seeing swapped > temporary variables in the debugger. The value used for execution is > correct but in the view two variables will have the value of the other. > Are you sure that the value *effectively* changes or could it be a > visualization problem? > > Max > > On 11.11.2013, at 17:29, btc(a)openinworld.com wrote: > > > I'm not sure if I'm missing something, but there seems some strange > behavior that I don't understand. The value of a block variable changes > when stepping over a method that acts on that variable. I encountered this > in Spec, but that seems co-incidental to the behaviour. > > SETUP > > 1. The attached "My-Spec-Tutorial-BenComan.1.mcz" (i.e. Bahman's > tutorial) was loaded into build #30564. > > > > 2. A breakpoint was inserted after the first "e generateArguments" in... > > SpecRowLayout>>privateAsArray > > | result shouldCheckSplitters | > > result := OrderedCollection new. > > shouldCheckSplitters := false. (self commands reject: [:e | e > isSplitter ]) do: [:e | > > ...lots..hidden.for..conciseness.... > > e generateArguments. > > self haltOnce. "<------------------" > > e asSpecElements do: [:el | > > result add: el ]]. > > > > 3. The following was evaluated... > > Halt enableHaltOnce. > > MyFirstWindow new openWithSpec: #defaultSpec. > > > > > > OBSERVATION > > 1. When the debugger opened at the breakpoint > > e = a SpecLayoutAdd > > > > 2. But after stepping over #asSpecElements > > e = an OrderedCollection() > > > > So how did the value of 'e' change? > > > > Where... > > SpecLayoutAdd(SpecLayoutSend)>>asSpecElements > > ^ {self selector.}, self arguments > > > > SpecLayoutAdd(SpecLayoutSend)>>selector > > ^ selector > > > > SpecLayoutAdd(SpecLayoutSend)>>arguments > > ^ arguments > > > > > > This was on Windows 7. Since files.pharo.org is offline, I wasn't able > to try a newer VM. My current was... > > > > NBCoInterpreter NativeBoost-CogPlugin-EstebanLorenzano.18 uuid: > a53445f9-c0c0-4015-97a3-be7db8d9ed6b Mar 13 2013 > > NBCogit NativeBoost-CogPlugin-EstebanLorenzano.18 uuid: > a53445f9-c0c0-4015-97a3-be7db8d9ed6b Mar 13 2013 > > git://gitorious.org/cogvm/blessed.git Commit: > 412abef33cbed05cf1d75329e451d71c0c6aa5a7 Date: 2013-03-13 17:48:50 +0100 > By: Esteban Lorenzano <estebanlm(a)gmail.com> Jenkins build #14535 > > > > Win32 built on Mar 13 2013 18:49:42 Compiler: 4.6.2 > > VMMaker versionString git://gitorious.org/cogvm/blessed.git Commit: > 412abef33cbed05cf1d75329e451d71c0c6aa5a7 Date: 2013-03-13 17:48:50 +0100 > By: Esteban Lorenzano <estebanlm(a)gmail.com> Jenkins build #14535 > > NBCoInterpreter NativeBoost-CogPlugin-EstebanLorenzano.18 uuid: > a53445f9-c0c0-4015-97a3-be7db8d9ed6b Mar 13 2013 > > NBCogit NativeBoost-CogPlugin-EstebanLorenzano.18 uuid: > a53445f9-c0c0-4015-97a3-be7db8d9ed6b Mar 13 2013 > > > > cheers -ben > > > > <My-Spec-Tutorial-BenComan.1.mcz> > > >

Nov. 11, 2013

Re: [Pharo-dev] How to get menu popping up

by Benjamin

What is classesListModel ? Ben On 11 Nov 2013, at 20:17, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > We are trying to fix the ChangeSorter because the menu are broken. > So we did > > ChangeSorterApplication>>changeSetMenu1: aMenu shifted: isShifted > "Set up aMenu to hold commands for the change-set-list pane. This could be for a single or double changeSorter" > > aMenu title: 'Change Set'. > self changeSetMenu1NewGeneration: aMenu. > > ChangeSorterApplication>>changeSetMenu1NewGeneration: aMenuModel > > | group1 menuItem | > menuItem := MenuItemModel new > name: [ TimeStamp now asString ]; > enabled: [ TimeStamp now seconds even ]; > yourself. > > group1 := MenuGroupModel new. > group1 autoRefresh: true. > > aMenuModel > addMenuGroup: group1. > self classesListModel menu: aMenuModel. > > > but the menu does not pop up. > > We tried to understand NewListModel but we could not understand how the new menu supposed to work > The example > > exampleWithMenu > "self exampleWithMenu" > â¦. > model := NewListModel new. > model menu: menu. > model openWithSpec > > but this is not how it works with a list. > So how do we use the new menu? > > > Stef

Nov. 11, 2013

Re: [Pharo-dev] About MenuModel

by Benjamin

It used to be a block. Now you can actually use both of them, with a subtile difference which is that the result of the block will not act one the model unlike a MenuModel which will add its shortcuts to the model by its own. I will write a presentation mail this evening to explain this a bit better :) Ben On 11 Nov 2013, at 20:13, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi Ben > > We do not understand MenuModel > in the example we have > > > menu := MenuModel new. > â¦ > group1 := MenuGroupModel new. > item11 := MenuItemModel new > name: [ TimeStamp now asString ]; > enabled: [ TimeStamp now seconds even ]; > yourself. > > ... > model := NewListModel new. > model menu: menu > > > then on the NewListModel > > NewListModel >> menu: aBlock > <api: #block getter: #menu registration: #whenMenuChanged:> > "Set the block used to defined the menu" > > menuHolder value: aBlock > > so it is a block? or a MenuModel? > > I'm totally confused. > > Stef

Nov. 11, 2013

Re: [Pharo-dev] to integrate :-)

by Camillo Bruni

nice :) BTW, if anybody is interested, you can run the CI validation locally ;) http://smalltalkhub.com/#!/~Pharo/ci On 2013-11-11, at 20:04, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > hi! > > Here are some resutls of the Pharo sprint: > > https://pharo.fogbugz.com/f/cases/12139/Navigating-in-menus > https://pharo.fogbugz.com/f/cases/12137/Temporary-variables-are-not-added-p… > > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Nov. 11, 2013

Re: [Pharo-dev] to integrate :-)

by Alexandre Bergel

One more: https://pharo.fogbugz.com/f/cases/12143/Right-clicking-in-the-debugger-text… Alexandre On Nov 11, 2013, at 4:04 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > hi! > > Here are some resutls of the Pharo sprint: > > https://pharo.fogbugz.com/f/cases/12139/Navigating-in-menus > https://pharo.fogbugz.com/f/cases/12137/Temporary-variables-are-not-added-p… > > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Nov. 11, 2013

Re: [Pharo-dev] How to test UI staff?

by Juraj Kubelka

Thanks for the explanation! Cheers, Jura El 11-11-2013, a las 16:04, Camillo Bruni <camillobruni(a)gmail.com> escribiÃ³: > On 2013-11-11, at 18:41, Juraj Kubelka <juraj.kubelka(a)gmail.com> wrote: >> Hi! >> >> I am trying to fix bug 12138 (https://pharo.fogbugz.com/f/cases/12138/Finding-a-class-is-kind-of-broken) >> >> And I would like to write test like that: >> >> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- >> testSearchSelectAndOK >> |classes | >> waitSemaphore := Semaphore new. >> classes := { Object . BlockClosure. Class }. >> listDialogWindow := SearchFacade classSearchIn: classes. >> "listDialogWindow open." >> listDialogWindow addDependent: self. >> listDialogWindow searchUpdate: 'BlockClosure'. >> waitSemaphore wait. >> listDialogWindow listIndex: 1. >> waitSemaphore wait. >> listDialogWindow ok. >> self assert: listDialogWindow answer notNil. >> self assert: (listDialogWindow answer = BlockClosure). >> >> handleUpdate: aMorphChanged >> waitSemaphore signal. >> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- >> >> If I run the test from debugger â context menu on test method and select debug tests â and then I do proceed, it works. If I press the green button in Nautilus which run the test, it is frozen and I have to kill it by Cmd+. The same happens if the test it run from Test Runner. >> >> It waits for testSemaphoreForMethod semaphore in method PackageTreeNautilusUI(NautilusUI)>>runTestForAMethod:notifying:priority: > > Hi, > > Note that the Debugger uses a separate UI Thread to avoid side-effects. > However if you run the test directly from nautilus this is not the case. > Instead the tests are directly run in the UIThread. > > If you do `waitSemaphore wait` you will instantaneously block the UI thread, > which in return means that #handleUpdate: will never be called (since the > UI thread execution halted). > > I just propose an outline for a solution (not well thought through.. :P): > Somehow you have to run the test in a separate thread ([...] fork) to make > sure `waitSemaphore wait` does not block the UI Thread. At the same time > you do not want to wait forever, so #valueWithin:onTimeout: is your friend :)

Nov. 11, 2013

Re: [Pharo-dev] about addMenuGroup:

by Benjamin

In fact, I remember why I put it there :) There is a method for creating groups with block, and I think it should be prefered Ben On 11 Nov 2013, at 19:30, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi ben > > addMenuGroup: is categorized in private but the examples uses it so I imagine that the category should be changed. > Can you confirm it? > > Stef

Nov. 11, 2013