- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] TextModel
by Alexandre Bergel Nov. 11, 2013

Nov. 11, 2013

Oh... I have noticed if we do this: PluggableTextMorph>>selectionInterval: sel Transcript show: 'selectionInterval: ', sel printString;cr. selectionInterval := sel Is it not enough to send an announcement? Alexandre On Nov 11, 2013, at 5:41 PM, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: > It is actually an issue. > > The problem comes from the fact the morph does not notify its model when its selection changed. > > > Ben > > On 11 Nov 2013, at 21:18, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > >> 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 >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

1 0

TextModel
by Alexandre Bergel Nov. 11, 2013

Nov. 11, 2013

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 ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

1 0

about Announcer unsubscribe:
by StÃ©phane Ducasse Nov. 11, 2013

Nov. 11, 2013

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

1 0

How to get menu popping up
by StÃ©phane Ducasse Nov. 11, 2013

Nov. 11, 2013

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

2 1

to integrate :-)
by Alexandre Bergel Nov. 11, 2013

Nov. 11, 2013

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 ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

2 2

How to test UI staff?
by Juraj Kubelka Nov. 11, 2013

Nov. 11, 2013

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: Apparently there are problems with process priorities. But I do not know what to change. Thank you for any help, Jura

2 2

about addMenuGroup:
by StÃ©phane Ducasse Nov. 11, 2013

Nov. 11, 2013

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

2 2

Who is Penelope, Ulysse's wife?
by Alexandre Bergel Nov. 11, 2013

Nov. 11, 2013

Looks like to be a robot, but apparently she is able to fill bug entries? Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

3 2

Bugs and files sites down?
by Pablo EstefÃ³ Nov. 11, 2013

Nov. 11, 2013

Hi guys, We are trying to start the Pharo Sprint here at DCC UChile but the sites files.pharo.org / bugs.pharo.org seems to be down. Cheers, Pablo

2 2

Fwd: [ci-announces] CI shutdown on the 11th of November
by Max Leske Nov. 11, 2013

Nov. 11, 2013

files.pharo.org and get.pharo.org will remain DOWN for the rest of the day. Begin forwarded message: > From: Emmanuel Jeanvoine <emmanuel.jeanvoine(a)inria.fr> > Subject: Re: [ci-announces] CI shutdown on the 11th of November > Date: 9. November 2013 09:00:31 MEZ > To: ci-announces(a)inria.fr > Reply-To: Emmanuel Jeanvoine <emmanuel.jeanvoine(a)inria.fr> > > On Thu, 07 Nov 2013, Emmanuel Jeanvoine wrote: > >> Dear users, >> >> The 11th of November, the IT department will stop the national IT >> services. As a consequence, the CI service will be stopped. >> >> In order to prevent any trouble, we strongly advice users to perform >> the following steps before the 11th of November (Sunday evening at the >> very latest): >> - stop the Jenkins instance of your project (see >> https://ci.inria.fr/project/PROJECTNAME/show#ci) >> - stop all the slaves related to your project (directly with a clean >> shutdown in the slave or from >> https://ci.inria.fr/project/PROJECTNAME/show#slaves) >> >> By the way, if you notice unused slaves in your project, you are >> strongly encouraged to removed them ("delete" button on >> https://ci.inria.fr/project/PROJECTNAME/show#slaves, or "destroy" >> button directly on the CloudStack interface). Stopping the unused >> slaves is not enough to free the related resources. >> >> Monday in the morning, the remaining running slaves will be stopped. >> After the maintenance, the Jenkins instances and the slaves will be >> restarted. >> >> Thus we hope that the service will be fully available on Tuesday in >> the morning. Anyway, since it is an heavy operation (major changes on >> the network of the datacenter) issues might occur, so we will >> communicate if communication means are available ;). >> >> Thank you for your understanding, >> Emmanuel > > > This is a reminder, you still have the opportunity to shutdown your > slaves and jenkins instances before tomorrow evening. This might be > useful to prevent slaves and jenkins corruption. > > Regards, > Emmanuel

1 0