Moose-dev July 2013

moose-dev@list.inf.unibe.ch

28 participants
130 discussions

by Tudor Girba

Hi, In the meantime, I added a utility method in GLMRubricTextMorphicTest: simulateOnlyOneClickOn: aMorph (Delay forMilliseconds: HandMorph doubleClickTime + 1) wait. aMorph simulateClick We should integrate this utility in Pharo 3.0. All tests are green locally. Let's see how it goes on the server. Cheers, Doru On Jul 15, 2013, at 8:57 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > This sounds good. I would call the block method as ignoreMultipleClicksWhile:. > > Doru > > > On Mon, Jul 15, 2013 at 8:43 AM, Alain Plantec <alain.plantec(a)univ-brest.fr> wrote: > maybe another solution would be to unplug the hand mouseclickstate before sending the event and to replug it after. > something like: > > -------- > simulateClick > self activeHand forbidMultipleClickWhile: [ > self simulateClickWith: MouseEvent redButton] > -------- > it would be much more efficient. > I will make a try. > Alain > > > Le 14 juil. 2013 à 21:26, Alain Plantec <alain.plantec(a)univ-brest.fr> a écrit : > > > yep, caught. > > and finally it is funny :) > > > > It has something to do with #simulateClick. > > In Rubric, MouseClickState is used to have a real doubleClick (whereas in TextMorph, the editor handle click/doubleClick by itself and not with MouseClickState). > > Mouse clickState mesures the time between two MouseDown and decide for a simple click if the time is > than HandMorph doubleClickTime. > > When several tests with simulateClick are runned, then depending on the state of the hand MouseClickState, a simple click or a double click are triggered. > > So it explains why when you run several tests some of then are failing. > > But when you run a single test with a single simultateClick, then it doesn't fail. > > > > the lesson is that mouseClickState should not be shared (instance var of the HandMorph). > > or it should test the target morph and not only the time. > > > > > > the workarround is to wait before any simulateClick, I've tried and it works. > > change the simulateClick method as follow and all your Rubric related tests should be green again. > > -------- > > simulateClick > > (Delay forMilliseconds: HandMorph doubleClickTime + 1) wait. > > self simulateClickWith: MouseEvent redButton. > > -------- > > > > Cheers > > Alain > > > > > > Le 13 juil. 2013 à 17:26, Tudor Girba <tudor(a)tudorgirba.com> a écrit : > > > >> Wow, thank you very much for looking into this. > >> > >> Doru > >> > >> > >> On Jul 13, 2013, at 3:14 PM, Alain Plantec <alain.plantec(a)univ-brest.fr> wrote: > >> > >>> ok, I 've a track > >>> With rubric, if a textArea do not have the focus but has a selection, then the first click on it give it the focus but don't deselect. > >>> In that case, one have to click to times to have the old TextMorph behavior. > >>> So, depending on the goal of the test, one have to send simulateClick one time or two times and not alway only one time. > >>> I will dig more to really understand. > >>> > >>> > >>> Le 13 juil. 2013 à 10:11, Alain Plantec <alain.plantec(a)univ-brest.fr> a écrit : > >>> > >>>> and if one add a #inspect send in a testMethod, the results are the same with the TestRunner but differ > >>>> if one run them from Nautilus. > >>>> As an example, with: > >>>> ----- > >>>> testEnteringTextInPort > >>>> | composite textMorph | > >>>> composite := GLMCompositePresentation new with: [ :a | a rubricText display: '' ]. > >>>> window := composite openOn: 4. > >>>> textMorph := self find: RubScrolledTextMorph in: window. > >>>> textMorph simulateClick. > >>>> self assert: textMorph activeHand keyboardFocus = textMorph textArea. > >>>> self simulateKeyStrokes: 'hello'. > >>>> (composite pane port: #text) value asString inspect. <-------------------------------- ** inspect added here ** > >>>> self assert: (composite pane port: #text) value asString = 'hello' > >>>> ---- > >>>> by running tests from Nautilus, the inspect runs ok and the result string is 'hello'. > >>>> but now #testAcceptKeyCanBeOverriden turns yellow > >>>> > >>>> by running test from the TestRunner, #testEnteringTextInPort and #testPastingUpdatesTextPort stay yellow (as without the inspect) > >>>> and #testAcceptKeyCanBeOverriden is green > >>>> > >>>> Alain > >>>> > >>>> > >>>> Le 2 juil. 2013 à 12:49, Tudor Girba <tudor(a)tudorgirba.com> a écrit : > >>>> > >>>>> Thanks. I got the same problem and I do not know where to start from. It's really strange. > >>>>> > >>>>> For those interested, the tests are in the GLMRubricTextMorphicTest class. If you run all of them repeatedly, you get some errors. If you run them individually, you do not. > >>>>> > >>>>> Alain: do you happen to have an insight? > >>>>> > >>>>> Doru > >>>>> > >>>>> > >>>>> On Tue, Jul 2, 2013 at 11:53 AM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > >>>>> Hi guys. > >>>>> > >>>>> I hope that we can release 4.8 and move to Pharo 3.0 soon. I wanted to fix failing tests and the only one is Rubric test. I was working with it for some time, and I have no idea what's up. When you run tests separately they work fine, but when being run in a suite some test fail and failures are inflicted by test order > >>>>> > >>>>> Maybe someone have ideas where to look at? UI maybe? > >>>>> > >>>>> Uko > >>>>> _______________________________________________ > >>>>> Moose-dev mailing list > >>>>> Moose-dev(a)iam.unibe.ch > >>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > >>>>> > >>>>> > >>>>> > >>>>> -- > >>>>> www.tudorgirba.com > >>>>> > >>>>> "Every thing has its own flow" > >>>> > >>>> > >>> > >> > >> -- > >> www.tudorgirba.com > >> > >> "If you interrupt the barber while he is cutting your hair, > >> you will end up with a messy haircut." > >> > >> > > > > > > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" -- www.tudorgirba.com "Next time you see your life passing by, say 'hi' and get to know her."

10 years, 9 months

focus with GLM-Roassal

by Usman Bhatti

The focus is not correct: It is centered on the lower right part of the diagram. So zooming-in hides the upper-left part of the diagram. Is this a known bug or a feature? To reproduce: Moose Finder -> a-Moose-Model -> all packages -> visualize -> Dependencies (cycles) -> zoom-in.

10 years, 9 months

Rubric test failures

by Yuriy Tymchuk

Hi guys. I hope that we can release 4.8 and move to Pharo 3.0 soon. I wanted to fix failing tests and the only one is Rubric test. I was working with it for some time, and I have no idea what's up. When you run tests separately they work fine, but when being run in a suite some test fail and failures are inflicted by test order Maybe someone have ideas where to look at? UI maybe? Uko

10 years, 9 months

Build failed in Jenkins: moose-latest-dev-4.8 #698

by admin＠moosetechnology.org

See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/698/> ------------------------------------------ [URLTrigger] A change within the response URL invocation (log) Building remotely on moose-ubuntu1204-dualproc-i386 in workspace <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/ws/> Deleting project workspace... done [moose-latest-dev-4.8] $ /bin/sh -xe /tmp/hudson4893996138813142628.sh + wget --quiet -O - http://get.pharo.org/20+vm + bash Downloading the latest 20 Image: http://files.pharo.org/image/20/latest.zip Pharo.image Downloading the latest pharoVM: http://files.pharo.org/vm/pharo/linux/stable.zip pharo-vm/pharo Downloading PharoV10.sources: http://files.pharo.org/sources//PharoV10.sources.zip Downloading PharoV20.sources: http://files.pharo.org/sources//PharoV20.sources.zip Creating starter scripts pharo and pharo-ui Please install the 32bit libraries sudo aptitude install ia32-libs + ./pharo Pharo.image save moose-latest-dev-4.8 + REPO=http://www.smalltalkhub.com/mc/Moose/Moose/main + ./pharo moose-latest-dev-4.8.image config http://www.smalltalkhub.com/mc/Moose/Moose/main ConfigurationOfMoose --install=development [31m[33m =============================================================================== Notice: Installing ConfigurationOfMoose development =============================================================================== [0m[0m[31m==== Startup Error: Error: Could not resolve: Collections-Support [Collections-Support] in <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/ws/package-cache> http://smalltalkhub.com/mc/Pharo/XMLWriter/main ERROR: 'GoferRepositoryError: Could not access http://ss3.gemstone.com/ss/Pharo20: ZnHttpUnsuccessful: 500 Internal Server Error' [0mMetacelloFetchingMCSpecLoader(Object)>>error: MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>retryingResolvePackageSpecReferences:gofer: MetacelloFetchingMCSpecLoader>>linearLoadPackageSpec:gofer: in Block: [| references nearestReference cachedReference ext...etc... MetacelloPharoPlatform>>do:displaying: in Block: [:bar | ... BlockClosure>>cull: Job>>run in Block: [result := block cull: self] BlockClosure>>on:do: Job>>run in Block: [self prepareForRunning.... BlockClosure>>ensure: Job>>run NonInteractiveUIManager(UIManager)>>displayProgress:from:to:during: ByteString(String)>>displayProgressFrom:to:during: MetacelloPharoPlatform>>do:displaying: MetacelloFetchingMCSpecLoader>>linearLoadPackageSpec:gofer: MetacelloPackageSpec>>loadUsing:gofer: MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>linearLoadPackageSpecs:repositories: in Block: [:pkg | pkg loadUsing: self gofer: gofer] OrderedCollection>>do: MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>linearLoadPackageSpecs:repositories: MetacelloFetchingMCSpecLoader>>linearLoadPackageSpecs:repositories: in Block: [super linearLoadPackageSpecs: packageSpecs reposi...etc... BlockClosure>>ensure: MetacelloLoaderPolicy>>pushLoadDirective:during: MetacelloLoaderPolicy>>pushLinearLoadDirectivesDuring:for: MetacelloFetchingMCSpecLoader>>linearLoadPackageSpecs:repositories: MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>load MetacelloMCVersionSpecLoader>>load MetacelloMCVersion>>executeLoadFromArray: MetacelloMCVersion>>fetchRequiredFromArray: in Block: [:dict | ^ self executeLoadFromArray: anArray] MetacelloPharoPlatform(MetacelloPlatform)>>useStackCacheDuring:defaultDictionary: in Block: [^ aBlock value: dict] BlockClosure>>on:do: MetacelloPharoPlatform(MetacelloPlatform)>>useStackCacheDuring:defaultDictionary: [0m[31mGot startup errors: [0m[31m Error: Could not resolve: Collections-Support [Collections-Support] in <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/ws/package-cache> http://smalltalkhub.com/mc/Pharo/XMLWriter/main ERROR: 'GoferRepositoryError: Could not access http://ss3.gemstone.com/ss/Pharo20: ZnHttpUnsuccessful: 500 Internal Server Error' [0mBuild step 'Execute shell' marked build as failure Archiving artifacts Recording test results

10 years, 9 months

Issue 953 in moose-technology: parentScope in FAMIXFunction should be container

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 953 by step...(a)stack.nl: parentScope in FAMIXFunction should be container http://code.google.com/p/moose-technology/issues/detail?id=953 Modeling Delphi code in FAMIX - functions can be nested - methods can contain (nested) functions parentScope should just be deprecated and point to container temporarily and then you have to modify ScopingEntity, too, and move the functions inst var to famixcontainer -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings

10 years, 9 months

Issue 954 in moose-technology: List presentation should support changing the color and font of the text

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 954 by chisvasi...(a)gmail.com: List presentation should support changing the color and font of the text http://code.google.com/p/moose-technology/issues/detail?id=954 Tree, list and column presentations should support changing the color and style of the text. For example, the following code should change just the color of the text: | browser | browser := GLMTabulator new. browser column: #one. browser transmit to: #one; andShow: [ :a | a list display: [ :x | x ]; textColor: [ :aNumber | (aNumber isDivisibleBy: 2) ifTrue: [ Color green ] ifFalse: [ Color red ] ] ]. browser openOn: (1 to: 6). -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings

10 years, 9 months

Issue 951 in moose-technology: Export then Import a MSE Model throws FMSyntaxError

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 951 by v.blonde...(a)gmail.com: Export then Import a MSE Model throws FMSyntaxError http://code.google.com/p/moose-technology/issues/detail?id=951 Hi, I wanted to export and import a MSE file of a Moose Model. The export works perfectly but the import which throws an FMSyntaxError. You can reproduce from the Moose Panel by creating a Model from Smalltalk, export it (Import/export / Export to MSE), and import it. The pragma in FAMIXMethod>>clientClasses : <MSEProperty: 'Client classes' type: #FAMIXType> <multivalued> seems to be the problem. Indeed 'Client Classes' contains a space character which is not recognize by the MSE parser. I resolved by deleting the space. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings

10 years, 9 months

Issue 955 in moose-technology: GTInspector should install methods in the selected class

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-GlamorousToolkit New issue 955 by tu...(a)tudorgirba.com: GTInspector should install methods in the selected class http://code.google.com/p/moose-technology/issues/detail?id=955 Right now, the inspector installs methods in the class of the current object. Instead, it should install the methods in the selected class (from the drop down). -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings

10 years, 9 months

Re: UI stuff in parsing

by Vincent Blondeau

Hi, > Le 11/07/2013 17:53, Stephan Eggermont a écrit : >> Hi Vincent, >> >> FMMSEParser basicRun should do the trick Indeed, but I send the message MooseModel importFromMSEStream, which call many methods before FMMSEParser basicRun included FMMSEParser run containing the UIstuff. I don't want to rewrite them just for remove that. >> What's your end goal for this? Because most of what you can do with >> moose >> is going to perform pretty bad over high latency slow bandwidth >> connections. >> >> http://sealedabstract.com/rants/why-mobile-web-apps-are-slow/ The goal of the Moose on web project is sharing project analyses. We want to deploy a moose platform on a server and accesses it from computers. So the developers would be able to consult the models and see the improvements they have to make on the code. We don't want to use mobile platforms to see the models. The technology is too slow for this. However, what we do is synthesize the information. The moose is accessible by blocks and, this, shorten the delay. Have you seen the website in demo : http://37.139.2.203/client/ and the API : http://37.139.2.203/API ? > > >> Stephan >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> > Vincent

10 years, 9 months

Re: [Pharo-users] New win32 VM available (was: More than 500MB for windows)

by Stéphane Ducasse

Thanks igor. On Jul 11, 2013, at 4:07 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > So, after spending unproportionally huge time (2days) dealing with > jenkins config idiosyncrasies, > it finally managed to build it. > > http://files.pharo.org/vm/pharo/win/latest.zip > > This VM should react properly on > AddressSpaceLimit=<number of MBytes> > setting in .ini file. > The ini file is located in same directory as VM executable. > If it doesn't exists, you can run VM once and it will create it automatically. > > Thanks for patience. > > -- > Best regards, > Igor Stasenko. >

10 years, 9 months

← Newer
1
...
6
7
8
9
10
11
12
13
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev July 2013