Moose-dev

moose-dev@list.inf.unibe.ch

6621 discussions

by Alexandre Bergel

Dear list, I am still struggling in populating my meta model with Java code. It is not clear to me how I can express dependencies. For example, I have a class Point, and a second class PointFactory. I guess there should be a famix entity intended to express this situation that contains the following information: - the method PointFactory>>createNewPoint has a reference to Point Which of the FAMIXes classes should I use? FAMIXAccess, FAMIXInvocation, FAMIXGlobalVariable? Then, what should I do with this famix entity. The FAMIXMethod (PointFactory>>createNewPoint) should know about it. Where should I do an add: ? In FAMIXMethod>>accesses, incomingInvocations, outgoingInvocations, ... ? Side question, what is a group (e.g., incomingInvocationsGroup)? Side questions 2: does it make sense that I add come comments in the moose code and then publish it in Store? I will do this... This is important I believe. But how can I do it? Sorry about my ignorance about Store. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

17 years

groups and versioning [was: Expressing dependencies in FAMIX]

by Tudor Girba

Hi Alex, And here are the answers for the other two questions. On Apr 16, 2008, at 1:21 AM, Alexandre Bergel wrote: > Side question, what is a group (e.g., incomingInvocationsGroup)? The methods that end with Group offer the collection of entities in a Group, and Group can be typed (e.g., ClassGroup) and such a typed Group has methods with meta-descriptions that then are shown better in the ui. > Side questions 2: does it make sense that I add come comments in the > moose code and then publish it in Store? Of course, you can add comments :) > I will do this... This is important I believe. But how can I do it? > Sorry about my ignorance > about Store. I guess you are asking about the publishing policy. You can find details here: http://moose.unibe.ch/docs/dev/versioning Cheers, Doru -- www.tudorgirba.com www.tudorgirba.com/blog "There are no old things, there are only old ways of looking at them."

17 years

Re: Does the message sorted: in the method MooseModel>>packagesDSM do anything?

by Romain PEIRS

Hi Ricky, What an idiot I am! :-) Indeed, it is returning a sorted copy! Now, it's working! Thanks a lot! Romain -----Message d'origine----- De : Richard Wettel [mailto:richard.wettel@lu.unisi.ch] Envoyé : mercredi 16 avril 2008 12:57 À : peirsro(a)ensieta.fr; Related to the development of Moose and other related tools Objet : Re: [Moose-dev] Re: Does the message sorted: in the method MooseModel>>packagesDSM do anything? Hi Romain, I got your question wrong. That's why the #sorted: in SequenceableCollection is returning a sorted copy of your collection, and does not modify the original collection. Ricky On Apr 16, 2008, at 12:43 PM, Romain PEIRS wrote: > Hi Ricky, > > Thanks for your answer. But my problem is that my collection is not > sorted > after this kind of message: > aCollection sorted: [:e1 :e2 | e1 staticNeededPackages size < e2 > staticNeededPackages size] > I don't really understand why! > > Cheers > > Romain > > > -----Message d'origine----- > De : Richard Wettel [mailto:richard.wettel@lu.unisi.ch] > Envoyé : mercredi 16 avril 2008 12:15 > À : peirsro(a)ensieta.fr; Related to the development of Moose and other > related tools > Objet : Re: [Moose-dev] Does the message sorted: in the method > MooseModel>>packagesDSM do anything? > > Hi Romain, > > #sorted: expects a block with 2 arguments, such as: > aCollection sorted: [:e1 :e2 | e1 staticNeededPackages size < e2 > staticNeededPackages size] > which will sort the elements ascending. > For more examples, just search for the senders of the selector > #sorted: > > Cheers, > Ricky > > On Apr 16, 2008, at 11:55 AM, Romain PEIRS wrote: > >> Hi everybody ! >> >> Im working on the method MooseModel >> packagesDSM and I noticed >> that the >> message sorted: sent to an OrderedCollection doesnt sort anything! >> I also tried with a simple condition of sort: p1staticNeededPackages >> size >>> p2staticNeededPackages size >> I dont understand why the OrderedCollection is not sorted. >> Have I forgot anything? >> >> Thanks >> >> Romain >> >> >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev

17 years

Re: Does the message sorted: in the method MooseModel>>packagesDSM do anything?

by Romain PEIRS

Hi Ricky, Thanks for your answer. But my problem is that my collection is not sorted after this kind of message: aCollection sorted: [:e1 :e2 | e1 staticNeededPackages size < e2 staticNeededPackages size] I don't really understand why! Cheers Romain -----Message d'origine----- De : Richard Wettel [mailto:richard.wettel@lu.unisi.ch] Envoyé : mercredi 16 avril 2008 12:15 À : peirsro(a)ensieta.fr; Related to the development of Moose and other related tools Objet : Re: [Moose-dev] Does the message sorted: in the method MooseModel>>packagesDSM do anything? Hi Romain, #sorted: expects a block with 2 arguments, such as: aCollection sorted: [:e1 :e2 | e1 staticNeededPackages size < e2 staticNeededPackages size] which will sort the elements ascending. For more examples, just search for the senders of the selector #sorted: Cheers, Ricky On Apr 16, 2008, at 11:55 AM, Romain PEIRS wrote: > Hi everybody ! > > Im working on the method MooseModel >> packagesDSM and I noticed > that the > message sorted: sent to an OrderedCollection doesnt sort anything! > I also tried with a simple condition of sort: p1staticNeededPackages > size >> p2staticNeededPackages size > I dont understand why the OrderedCollection is not sorted. > Have I forgot anything? > > Thanks > > Romain > > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev

17 years

Does the message sorted: in the method MooseModel>>packagesDSM do anything?

by Romain PEIRS

Hi everybody ! Im working on the method MooseModel >> packagesDSM and I noticed that the message sorted: sent to an OrderedCollection doesnt sort anything! I also tried with a simple condition of sort: p1staticNeededPackages size > p2staticNeededPackages size I dont understand why the OrderedCollection is not sorted. Have I forgot anything? Thanks Romain

17 years

Why are the classes and methods not displayed

by Orla Greevy

Hi, related to my previous question, I have a model loaded in moose which I generated usinig the namespaceImporter. When I inspect the model all the classes and methods are there but they are not displayed n the browser. Any ideas? Orla

17 years

embedding EyeSee diagrams as subcanvas?

by Johan Brichau

Hi everybody, I have some trouble embedding an Eyesee diagram in an application window. Right now, I basically put a VisualisationUI as a subcanvas. The code snippets that illustrate the essential parts of that process are below. However, this does not seem to be an ideal solution. The diagram is not scaled to the subcanvas (there are scrollbars) and I don't see how to accomplish that. Maybe I'm doing something wrong and I should not use the VisualisationUI as the subcanvas? Or maybe I can easily scale the diagram to the size of the subcanvas? I only found a way to change the zoom level. Any help would be appreciated. Thanks! ---- code snippets ---- .... theCanvas := Graphics.VisualizationUI new .... diagramrenderer diagram gcWrapper: EyeSee.DiagramGraphicsContextWrapper new. diagramrenderer diagram setup. ... postBuildWith: aBuilder theCanvas visualization model: diagramrenderer. ---------------------------- Johan Brichau johan.brichau(a)uclouvain.be

17 years

setBelongsTo: vs packageIn:

by Alexandre Bergel

Hi! I wish to specify that a class belongs to a package. Which of these invocations should I use? famixClass setBelongsTo: package. famixClass packageIn: package Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

17 years

NamespaceImporter

by Orla Greevy

Hi, THe following code used to export a moose model of moose but now is not working. Any ideas? Thanks Orla |model | model := MooseModel new. model name: aName. NameSpaceImporter new add: SCG.Moose; model: model; run. MooseModel root addEntity: model.

17 years

Error in the last version of Moose ...

by Alexandre Bergel

In the last version of Moose, there is the following piece of code: EntityState>>cache: selector initializer: aBlock ^self at: selector ifAbsentPut: [ aBlock cullValue: self entity ] cullValue: does not exist. callValue: neither... This raises some rollbacks in the moose GUI... Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

17 years

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev