- Moose-dev - INF Mailman

by Fabrizio Perin

Hi, i got a strange error from the debugger: when the debug window appear (in my case because a test fail) i click on the method that i want to visualize and and another debug window appear saying "MessageNotUnderstood: TextMorphEditor>>blinkParen". Attached the log. Than i figure out that in the last build of Moose you cannot even open a workspace because you get the same error. Seems something starting from shout but i'm not sure. Cheers, Fabrizio

14 years, 7 months

7
14
0 0

PetitParser - The Great Flatten Mystery

by Sean P. DeNigris

I am baffled... I want to turn 'I am not yet watching' into 'IAmNotYetWatching'. I got really close with: | word additionalWord parser | word := #word asParser plus flatten ==> [ :s | s capitalized ]. additionalWord := #space asParser, word ==> [ :n | n second ]. parser := (word, additionalWord star). parser parse: 'I am not yet watching'. Result: #('I' #('Am' 'Not' 'Yet' 'Watching')) So I thought, "cool, just flatten that puppy and"... not even close! I got the exact input string back! What?! ... same as above with flatten added \/ parser := (word, additionalWord star) flatten. parser parse: 'I am not yet watching'. Result: 'I am not yet watching' Where did my capitals go and how did the spaces get back in there? Thanks. Sean -- View this message in context: http://forum.world.st/PetitParser-The-Great-Flatten-Mystery-tp3072095p30720… Sent from the Moose mailing list archive at Nabble.com.

14 years, 7 months

2
2
0 0

bunchCohesion

by Tudor Girba

Hi, The following test is failing: http://hudson.moosetechnology.org/job/moose-latest-dev-on-pharo-1.2/48/test… The reason it is failing is that the method bunchCohesion is not defined. I guess the appropriate code was not published. Andre, Nicolas, could you take a look? Cheers, Doru -- www.tudorgirba.com "When people care, great things can happen."

14 years, 7 months

2
1
0 0

ConfigurationOfPetitParser should stay in its own repo

by Tudor Girba

Hi Alex, I see that you are working on the Moose release. That is great! Just a note: The ConfigurationOfPetitParser should remain in the repository of Lukas, and not in the repository of Moose. Could you take care of that? Cheers, Doru -- www.tudorgirba.com "It's not what we do that matters most, it's how we do it."

14 years, 7 months

3
2
0 0

Re: CollectionExtension>> testFlatCollectArray needs Nile?

by Tudor Girba

Why not depend on it? I think that if we are not using Nile, all the nice work goes away. Are there any problems related to it? Cheers, Doru On 3 Dec 2010, at 16:03, Alexandre Bergel wrote: > Hi! > > testFlatCollectArray uses flatCollect:, which itself uses nsWriteStream. > Is this really necessary to have Nile for this flatCollect:? Mondrian loads CollectionExtension. Is there a particular reason for this? I would rather prefer not to depend on CollectionExtension in that case... > > testFlatCollectArray > "self debug: #testFlatCollectArray" > > self assert: ((#((1 2) (3 4) (5 3)) flatCollect: [ :each | each ] as: Array ) = #(1 2 3 4 5 3)). > ... > > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > -- www.tudorgirba.com "In a world where everything is moving ever faster, one might have better chances to win by moving slower."

14 years, 7 months

2
1
0 0

Re: Question for student report

by Tudor Girba

Hi Simon, I would suggest registering to the mailing list and asking more specific questions: http://www.moosetechnology.org/about/contact I would suggest scheming through the online Moose Book. In particular I would suggest to start from the last chapter: http://www.themoosebook.org/book/philosophy Regarding the use of Smalltalk, here is a short explanation: http://www.themoosebook.org/book/introduction/smalltalk Cheers, Tudor On 1 Dec 2010, at 17:06, (s) Simon Pakijavan wrote: > Hi Tudor > > Thanks for the reply. > > I'm really interested in finding out what makes Moose such a usefull tool for data management and also why it is Smalltalk based. I suppose these topics would be the goal of the report. If you have any more information that may help me find the answers to these questions would be very usefull. > > Thank you > > Simon Pakijavan > ________________________________________ > From: Tudor Girba [tudor.girba(a)gmail.com] > Sent: 01 December 2010 02:18 > To: (s) Simon Pakijavan > Cc: Moose-related development > Subject: Re: [Moose-dev] Question for student report > > Hi Simon, > > I think you did not get this mail. > > Cheers, > Doru > > > On 30 Nov 2010, at 14:11, Tudor Girba wrote: > >> Hi Simon, >> >> Nice to hear from you. >> >> I am currently working with two companies that are using Moose: >> - MCS Parametrix AG, Switzerland (http://www.parametrix.ch) - is using the latest Moose for analyzing systems written in Java and in a custom domain specific language. >> - MMA France (http://www.mma.fr) - is using the Moose 3.2 in VW to analyze Smalltalk systems. >> >> Could you tell us more about the goal of the report? >> >> Cheers, >> Tudor >> >> >> On 30 Nov 2010, at 12:56, (s) Simon Pakijavan wrote: >> >>> Hello >>> >>> My name is Simon Pakijavan and I am a 3rd year computer science student in the UK writing a report into the applications of Moose. >>> >>> For my report, it would be useful to research into some of the organisations that use Moose. If you could provide me with the names of some of these organisations, I would be immensely grateful. >>> >>> Yours >>> >>> Simon Pakijavan >>> >>> _______________________________________________ >>> Moose-dev mailing list >>> Moose-dev(a)iam.unibe.ch >>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> >> -- >> www.tudorgirba.com >> >> "It's not what we do that matters most, it's how we do it." >> > > -- > www.tudorgirba.com > > "Next time you see your life passing by, say 'hi' and get to know her." > > > -- www.tudorgirba.com "Relationships are of two kinds: those we choose and those that happen. They both matter."

14 years, 7 months

1
0
0 0

Question for student report

by (s) Simon Pakijavan

Hello My name is Simon Pakijavan and I am a 3rd year computer science student in the UK writing a report into the applications of Moose. For my report, it would be useful to research into some of the organisations that use Moose. If you could provide me with the names of some of these organisations, I would be immensely grateful. Yours Simon Pakijavan

14 years, 7 months

3
3
0 0

debug command in Mondrian

by Alexandre Bergel

Hi! Just to let you know that I've been working on a debug command for Mondrian. It opens a visualization that shows you how your view is structured. Consider the visualization: Here is the debugging visualization. Red square are not that are cached with a bitmap. Inner nodes are the presence of a metric cache. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

14 years, 7 months

4
5
0 0

Where is OPAX

by Fabrizio Perin

Hi, i cannot find anymore OPAX under XML-Parser. After the long discussion about the future of OPAX i guess that at the end OPAX has been move, but where? I cannot see any package related to OPAX into the XML-Support repo. Where i can find the last version of the OPAX packages that have been moved from XML-Parser? Cheers, Fabrizio

14 years, 7 months

3
6
0 0

PPCompositeTest

by Tudor Girba

Hi Lukas, I noticed that you override two times the changes I pushed in the PPCompositeTest, and as expected, these changes break most of the external tests :). In particular, there are two things that I found useful: - the result instance variable holding the side effect of executing #parse:rule:. This is useful for reusing the grammar tests in the parser tests. - the fail:rule: method for negative tests. In the last comment, you mentioned that this was due to incompatibilities with Helvetia. Should we create a new class with these utilities? Cheers, Doru -- www.tudorgirba.com "When people care, great things can happen."

14 years, 7 months

2
2
0 0

PetitParser instance variables

by Sean P. DeNigris

I wanted my PPCompositeParser subclass to save some values as it parses. But when I added an instance variable, class>>parse: failed with "Error: Unable to initialize #[instVar name]" How do I save these intermediate results? Is it not possible to have inst vars for my own purposes? Sean -- View this message in context: http://forum.world.st/PetitParser-instance-variables-tp3062129p3062129.html Sent from the Moose mailing list archive at Nabble.com.

14 years, 7 months

2
2
0 0

actions and selection actions

by Tudor Girba

Hi, In the latest Glamour, we now make a distinction between actions and selection actions: - global actions selectors are: #dynamicActions: #act* - selection action selectors are: #dynamicActionsOnSelection: #selectionAct* This is interesting because now we can get actions that can work on the overall presentation regardless of the selection. For example, in the MoosePanel we now have a toolbar for each pane (like shown in the attachment) that provides all actions relevant for the current entity. I am still not satisfied with the way the actions are rendered. At the moment, they take an entire row below the title. I would more like it like in Eclipse, where the actions are rendered next to the tabs. Hopefully this will change in a while when someone will put some effort into the Morphic rendering :) Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow."

14 years, 7 months

1
0
0 0

Issue 486 in moose-technology: Presentation-wide actions should be displayed in a toolbar

by moose-technology＠googlecode.com

Status: New Owner: tudor.girba Labels: Type-Enhancement Priority-Medium Component-Glamour New issue 486 by tudor.girba: Presentation-wide actions should be displayed in a toolbar http://code.google.com/p/moose-technology/issues/detail?id=486 Right now, a browser-wide action is mapped on the toolbar, but for each individual list we only have contextual actions that are relevant for selections. We need to distinguish between the selection and the global actions and render for each presentation a toolbar.

14 years, 7 months

1
1
0 0

Re: Issue 310 in moose-technology: Make Glamour loadable without Mondrian and Magritte

by moose-technology＠googlecode.com

Updates: Status: Fixed Labels: Milestone-4.2 Comment #1 on issue 310 by tudor.girba: Make Glamour loadable without Mondrian and Magritte http://code.google.com/p/moose-technology/issues/detail?id=310 The ConfigurationOfGlamour has a Core group that does not load any mondrian or magritte related packages

14 years, 7 months

1
0
0 0

PetitParser trim bug?

by Sean P. DeNigris

According to http://www.lukas-renggli.ch/blog/petitparser-1, "p trim Trims whitespaces before and after p". However, the following snippet seems not to trim the whitespace at the end of the second parser: stringToParse := 'class=" aClass "'. parser := ('class="' asParser, $" asParser negate plus trim flatten, '"' asParser) ==> [ :nodes | nodes second ]. result := parser parse: stringToParse. self assert: result = 'aClass'. "actually returns ' aClass '" Should it be stripping the trailing space? Thanks. Sean -- View this message in context: http://forum.world.st/PetitParser-trim-bug-tp3059805p3059805.html Sent from the Moose mailing list archive at Nabble.com.

14 years, 7 months

2
1
0 0

Re: Hudson build is still unstable: moose-latest-dev #466

by Tudor Girba

Hi, That's great. I fixed the sorted issue (the problem was that internally we were calling sort: instead of sorted: and this does not copy the collection). Cheers, Doru On 25 Nov 2010, at 21:18, Alexandre Bergel wrote: > Hi! > > I fixed a number of test cases: > The tests in MooseFinderTest were yellow because of some icons problems. I fixed this. > > For Mondrian: > All the 310 tests are green in a 12554 (using the 'default' Metacello version). > They are also green in a 1.1.1 using the Metacello Version '2.1.2' > > This left 3 tests. > > I looked at: > testSort > > | sorted group collection | > group := MooseGroup withAll: #(1 3 2). > collection := group entities. > sorted := group sorted: [:a :b | a < b]. > self assert: sorted entities ~= collection > > It is yellow, I do not understand why. I would expect: sorted entities = collection > > I updated testCategoryImporter in: Moose-Tests-SmalltalkImporter-Core-AlexandreBergel.10 > "Update in testCategoryImporter. There was a bug due to the remodularlization." > > Cheers, > Alexandre > > On 24 Nov 2010, at 20:21, admin(a)moosetechnology.org wrote: > >> See <http://hudson.moosetechnology.org/job/moose-latest-dev/466/> >> >> > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > -- www.tudorgirba.com "What is more important: To be happy, or to make happy?"

14 years, 7 months

1
0
0 0

Shout load in Pharo 1.2

by Laval Jannik

Hi, I cannot load Moose in Pharo1.2 because of Shout. It is difficult to debug it, as I cannot open a debugger... But the problem comes from TextMorphForShoutEditor>>findText which does not exist. Any idea ? --- Jannik Laval

14 years, 7 months

3
11
0 0

Re: [Pharo-project] Much better issues feed from Google

by Tudor Girba

Indeed, it looks quite nice. It would be great to have the issues inside the image. To make it great, we would just need the tiny feature of affecting the issues (replying, creating) :) Cheers, Doru On 23 Nov 2010, at 23:46, Stephan Eggermont wrote: > Would be to have it in a browser in the image. > > An early experiment with the current Moose daily build > shows it can be done: > > http://www.squeaksource.com/GoogleIssuesFeed > > Stephan > -- www.tudorgirba.com "What is more important: To be happy, or to make happy?"

14 years, 7 months

1
0
0 0

Re: Issue 477 in moose-technology: Export exception in VerveineJ

by moose-technology＠googlecode.com

Updates: Status: Fixed Comment #1 on issue 477 by anquetil.nicolas: Export exception in VerveineJ http://code.google.com/p/moose-technology/issues/detail?id=477 (No comment was entered for this change.)

14 years, 7 months

1
0
0 0

Fwd: Build failed in Hudson: moose-latest-dev #454

by Alexandre Bergel

I do not know where the problem comes from. I just tried with a Pharo-dev 1.1.1 and it just works. Cheers, Alexandre Begin forwarded message: > From: admin(a)moosetechnology.org > Date: 19 November 2010 20:15:53 GMT-03:00 > To: tudor(a)tudorgirba.com, simon.denier(a)gmail.com, cy.delaunay(a)gmail.com, alexandre(a)bergel.eu, stephane.ducasse(a)inria.fr, jannik.laval(a)inria.fr > Subject: Build failed in Hudson: moose-latest-dev #454 > > See <http://hudson.moosetechnology.org/job/moose-latest-dev/454/> > > ------------------------------------------ > [...truncated 518 lines...] > errorDefinitions: an OrderedCollection() > provisions: a Set(#BitmapBugz #ORCmdInstVarRefsEnvironment #ORVariableBrowser #...etc... > methodAdditions: an OrderedCollection(a MethodAddition a MethodAddition a Metho...etc... > > > [] in MCPackageLoader>>useChangeSetNamed:during: > Receiver: a MCPackageLoader > Arguments and temporary variables: > aBlock: [self basicLoad] > Receiver's instance variables: > requirements: #() > unloadableDefinitions: a SortedCollection() > obsoletions: a Dictionary() > additions: an OrderedCollection(a MCOrganizationDefinition(#(#'XML-Parser' #'XM...etc... > removals: an OrderedCollection() > errorDefinitions: an OrderedCollection() > provisions: a Set(#BitmapBugz #ORCmdInstVarRefsEnvironment #ORVariableBrowser #...etc... > methodAdditions: an OrderedCollection(a MethodAddition a MethodAddition a Metho...etc... > > > BlockClosure>>ensure: > Receiver: [aBlock value] > Arguments and temporary variables: > aBlock: [changeHolder newChanges: oldChanges] > complete: nil > returnValue: nil > Receiver's instance variables: > outerContext: MCPackageLoader>>useChangeSetNamed:during: > startpc: 93 > numArgs: 0 > > > MCPackageLoader>>useChangeSetNamed:during: > Receiver: a MCPackageLoader > Arguments and temporary variables: > baseName: 'XML-Parser-JAAyer.105' > aBlock: [self basicLoad] > changeHolder: ChangeSet > oldChanges: a ChangeSet named Unnamed > newChanges: a ChangeSet named XML-Parser-JAAyer.105 > Receiver's instance variables: > requirements: #() > unloadableDefinitions: a SortedCollection() > obsoletions: a Dictionary() > additions: an OrderedCollection(a MCOrganizationDefinition(#(#'XML-Parser' #'XM...etc... > removals: an OrderedCollection() > errorDefinitions: an OrderedCollection() > provisions: a Set(#BitmapBugz #ORCmdInstVarRefsEnvironment #ORVariableBrowser #...etc... > methodAdditions: an OrderedCollection(a MethodAddition a MethodAddition a Metho...etc... > > > MCPackageLoader>>useNewChangeSetNamedLike:during: > Receiver: a MCPackageLoader > Arguments and temporary variables: > baseName: 'XML-Parser-JAAyer.105' > aBlock: [self basicLoad] > Receiver's instance variables: > requirements: #() > unloadableDefinitions: a SortedCollection() > obsoletions: a Dictionary() > additions: an OrderedCollection(a MCOrganizationDefinition(#(#'XML-Parser' #'XM...etc... > removals: an OrderedCollection() > errorDefinitions: an OrderedCollection() > provisions: a Set(#BitmapBugz #ORCmdInstVarRefsEnvironment #ORVariableBrowser #...etc... > methodAdditions: an OrderedCollection(a MethodAddition a MethodAddition a Metho...etc... > > > MCPackageLoader>>loadWithNameLike: > Receiver: a MCPackageLoader > Arguments and temporary variables: > baseName: 'XML-Parser-JAAyer.105' > Receiver's instance variables: > requirements: #() > unloadableDefinitions: a SortedCollection() > obsoletions: a Dictionary() > additions: an OrderedCollection(a MCOrganizationDefinition(#(#'XML-Parser' #'XM...etc... > removals: an OrderedCollection() > errorDefinitions: an OrderedCollection() > provisions: a Set(#BitmapBugz #ORCmdInstVarRefsEnvironment #ORVariableBrowser #...etc... > methodAdditions: an OrderedCollection(a MethodAddition a MethodAddition a Metho...etc... > > > MCVersionLoader>>loadWithNameLike: > Receiver: a MCVersionLoader > Arguments and temporary variables: > aString: 'XML-Parser-JAAyer.105' > loader: a MCPackageLoader > Receiver's instance variables: > versions: an OrderedCollection(a MCVersion(XML-Parser-JAAyer.105)) > > > MCVersionLoader>>load > Receiver: a MCVersionLoader > Arguments and temporary variables: > > Receiver's instance variables: > versions: an OrderedCollection(a MCVersion(XML-Parser-JAAyer.105)) > > > MetacelloGoferLoad(GoferLoad)>>execute > Receiver: a MetacelloGoferLoad > Arguments and temporary variables: > > Receiver's instance variables: > gofer: a Gofer > model: a MCVersionLoader > > > > --- The full stack --- > UndefinedObject(Object)>>doesNotUnderstand: #newFrom: > class>>initialize > MCMethodDefinition>>postloadOver: > [] in [] in [] in MCPackageLoader>>basicLoad > [] in [] in OrderedCollection(Collection)>>do:displayingProgress:every: > OrderedCollection>>do: > [] in OrderedCollection(Collection)>>do:displayingProgress:every: > [] in [] in ProgressInitiationException>>defaultMorphicAction > BlockClosure>>on:do: > [] in ProgressInitiationException>>defaultMorphicAction > BlockClosure>>ensure: > ProgressInitiationException>>defaultMorphicAction > ProgressInitiationException>>defaultAction > UndefinedObject>>handleSignal: > MethodContext(ContextPart)>>handleSignal: > MethodContext(ContextPart)>>handleSignal: > MethodContext(ContextPart)>>handleSignal: > MethodContext(ContextPart)>>handleSignal: > MethodContext(ContextPart)>>handleSignal: > ProgressInitiationException(Exception)>>signal > ProgressInitiationException>>display:at:from:to:during: > ProgressInitiationException class>>display:at:from:to:during: > ByteString(String)>>displayProgressAt:from:to:during: > OrderedCollection(Collection)>>do:displayingProgress:every: > OrderedCollection(Collection)>>do:displayingProgress: > [] in [] in MCPackageLoader>>basicLoad > BlockClosure>>on:do: > [] in MCPackageLoader>>basicLoad > BlockClosure>>ensure: > MCPackageLoader>>basicLoad > [] in MCPackageLoader>>loadWithNameLike: > [] in MCPackageLoader>>useChangeSetNamed:during: > BlockClosure>>ensure: > MCPackageLoader>>useChangeSetNamed:during: > MCPackageLoader>>useNewChangeSetNamedLike:during: > MCPackageLoader>>loadWithNameLike: > MCVersionLoader>>loadWithNameLike: > MCVersionLoader>>load > MetacelloGoferLoad(GoferLoad)>>execute > - - - - - - - - - - - - - - - > - - - - - - - - - - - - - - - - - - > [] in [] in MetacelloLoadingMCSpecLoader(MetacelloCommonMCSpecLoader)>>loadPackageDirective:gofer: > [] in MetacelloLoadingMCSpecLoader(MetacelloCommonMCSpecLoader)>>loadPackageDirective:gofer: > [] in MetacelloPharoPlatform>>do:displaying: > [] in [] in ProgressInitiationException>>defaultMorphicAction > BlockClosure>>on:do: > [] in ProgressInitiationException>>defaultMorphicAction > BlockClosure>>ensure: > ProgressInitiationException>>defaultMorphicAction > ProgressInitiationException>>defaultAction > UndefinedObject>>handleSignal: > MethodContext(ContextPart)>>handleSignal: > MethodContext(ContextPart)>>handleSignal: > MethodContext(ContextPart)>>handleSignal: > ProgressInitiationException(Exception)>>signal > ProgressInitiationException>>display:at:from:to:during: > ProgressInitiationException class>>display:at:from:to:during: > ByteString(String)>>displayProgressAt:from:to:during: > MetacelloPharoPlatform>>do:displaying: > MetacelloLoadingMCSpecLoader(MetacelloCommonMCSpecLoader)>>loadPackageDirective:gofer: > MetacelloLinearLoadDirective(MetacelloVersionLoadDirective)>>loadPackageDirective:gofer: > MetacelloPackageLoadDirective>>loadUsing:gofer: > [] in MetacelloAtomicLoadDirective(MetacelloVersionLoadDirective)>>loadLinearLoadDirective:gofer: > OrderedCollection>>do: > MetacelloAtomicLoadDirective(MetacelloVersionLoadDirective)>>loadLinearLoadDirective:gofer: > MetacelloAtomicLoadDirective>>loadLinearLoadDirective:gofer: > MetacelloLinearLoadDirective>>loadUsing:gofer: > [] in MetacelloLinearLoadDirective(MetacelloVersionLoadDirective)>>loadAtomicLoadDirective:gofer: > OrderedCollection>>do: > MetacelloLinearLoadDirective(MetacelloVersionLoadDirective)>>loadAtomicLoadDirective:gofer: > MetacelloAtomicLoadDirective>>loadUsing:gofer: > [] in MetacelloLinearLoadDirective(MetacelloVersionLoadDirective)>>loadLinearLoadDirective:gofer: > OrderedCollection>>do: > MetacelloLinearLoadDirective(MetacelloVersionLoadDirective)>>loadLinearLoadDirective:gofer: > MetacelloLinearLoadDirective>>loadUsing:gofer: > MetacelloLinearLoadDirective(MetacelloVersionLoadDirective)>>loadWithPolicy: > MetacelloLoaderPolicy>>load > MetacelloFetchingMCSpecLoader>>doLoad > [] in [] in MetacelloMCVersion>>doLoadRequiredFromArray: > [] in MetacelloPharoPlatform>>do:displaying: > [] in [] in ProgressInitiationException>>defaultMorphicAction > BlockClosure>>on:do: > [] in ProgressInitiationException>>defaultMorphicAction > BlockClosure>>ensure: > ProgressInitiationException>>defaultMorphicAction > ProgressInitiationException>>defaultAction > UndefinedObject>>handleSignal: > MethodContext(ContextPart)>>handleSignal: > MethodContext(ContextPart)>>handleSignal: > ProgressInitiationException(Exception)>>signal > ProgressInitiationException>>display:at:from:to:during: > ProgressInitiationException class>>display:at:from:to:during: > ByteString(String)>>displayProgressAt:from:to:during: > MetacelloPharoPlatform>>do:displaying: > [] in MetacelloMCVersion>>doLoadRequiredFromArray: > BlockClosure>>ensure: > MetacelloMCVersion>>doLoadRequiredFromArray: > MetacelloMCVersion>>load > ConfigurationOfMoose class>>loadRelease42 > UndefinedObject>>DoIt > Compiler>>evaluate:in:to:notifying:ifFail:logged: > Compiler class>>evaluate:for:notifying:logged: > Compiler class>>evaluate:for:logged: > Compiler class>>evaluate:logged: > [] in [] in RWBinaryOrTextStream(PositionableStream)>>fileInAnnouncing: > BlockClosure>>on:do: > [] in RWBinaryOrTextStream(PositionableStream)>>fileInAnnouncing: > [] in [] in ProgressInitiationException>>defaultMorphicAction > BlockClosure>>on:do: > [] in ProgressInitiationException>>defaultMorphicAction > BlockClosure>>ensure: > ProgressInitiationException>>defaultMorphicAction > ProgressInitiationException>>defaultAction > UndefinedObject>>handleSignal: > ProgressInitiationException(Exception)>>signal > ProgressInitiationException>>display:at:from:to:during: > ProgressInitiationException class>>display:at:from:to:during: > ByteString(String)>>displayProgressAt:from:to:during: > RWBinaryOrTextStream(PositionableStream)>>fileInAnnouncing: > RWBinaryOrTextStream(PositionableStream)>>fileIn > CodeLoader>>installSourceFile: > [] in CodeLoader>>installSourceFiles > Array(SequenceableCollection)>>do: > CodeLoader>>installSourceFiles > ProjectLauncher>>startUpAfterLogin > ProjectLauncher>>startUp > [] in [] in AutoStart class>>startUp: > WorldState>>runStepMethodsIn: > PasteUpMorph>>runStepMethods > WorldState>>doOneCycleNowFor: > WorldState>>doOneCycleFor: > PasteUpMorph>>doOneCycle > [] in Project class>>spawnNewProcess > [] in BlockClosure>>newProcess > ------------------------------------------------------------ > > /srv/hudson.moosetechnology.org/builder/build.sh: line 142: 3297 Killed exec "$PHARO_VM" $PHARO_PARAM "$OUTPUT_IMAGE" "$OUTPUT_SCRIPT" > Archiving artifacts > Recording test results > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

14 years, 7 months

3
8
0 0

Re: FAMIXPackageGroup>>exportAsGML

by Simon Denier

On 20 nov. 2010, at 11:47, Tudor Girba wrote: > Hi, > > While browsing the FAMIXPackageGroup class, I stumbled over: > FAMIXPackageGroup>>exportAsGML > > Does anyone know what it is for? It obviously exports to the GML format, but I do not know what tool to use to look at it and I also do not know what exactly it visualizes. http://en.wikipedia.org/wiki/Graph_Modelling_Language In particular, it was used to export package/class dependency graphs, visualize in Yed, and compare with package blueprints. -- Simon

14 years, 7 months

1
0
0 0

FAMIXPackageGroup>>exportAsGML

by Tudor Girba

Hi, While browsing the FAMIXPackageGroup class, I stumbled over: FAMIXPackageGroup>>exportAsGML Does anyone know what it is for? It obviously exports to the GML format, but I do not know what tool to use to look at it and I also do not know what exactly it visualizes. Cheers, Doru -- www.tudorgirba.com "If you interrupt the barber while he is cutting your hair, you will end up with a messy haircut."

14 years, 7 months

1
0
0 0

problem loading XMLSupport

by Tudor Girba

Hi, It looks like loading the latest XMLSupport raises some problems: http://hudson.moosetechnology.org/job/moose-latest-dev/448/console Could anyone take a look at that? Cheers, Doru -- www.tudorgirba.com "Presenting is storytelling."

14 years, 7 months

4
7
0 0

Re: Issue 289 in moose-technology: Cleaning #forNodes:whenEnteringUpdateShapes:whenLeavingUpdateShapes:withLayoutUpdate:

by moose-technology＠googlecode.com

Updates: Status: Fixed Comment #2 on issue 289 by alexandre.bergel: Cleaning #forNodes:whenEnteringUpdateShapes:whenLeavingUpdateShapes:withLayoutUpdate: http://code.google.com/p/moose-technology/issues/detail?id=289 (No comment was entered for this change.)

14 years, 7 months

1
0
0 0

VerveineJ out of memory error

by Fabrizio Perin

Hi, i just try to use VerveineJ to import Java code in moose and i'm not able to make it work: first i tried by command line to use VerveineJ to create the mse of LANModel and it worked. Than i tried to use it with one of my case study and i got: java.lang.OutOfMemoryError: Java heap space. I tried to modify the script verveinej.sh adding the -Xmx2048m option ( JOPT="-Xmx2048m" ) and it still doesn't work. Than i tried to use the Moose Wizard and again for the LANModel no problem, but when i tried to import one of my case study i get an error: a message box appear saying that the output.mse file doesn't exist and it ask me to point to an existing file. Apparently verveinej just does not create the file because not able to parse the project and the importer try to go ahead but it does not have any output file from verveinej. Someone has a similar problem? Am i doing something wrong? Cheers, Fabrizio

14 years, 7 months

2
5
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev