24 May
2011
24 May
'11
9:34 p.m.
Hi,
On 24 May 2011, at 21:19, Stéphane Ducasse wrote:
tx doru but I do not understand why
- the importer cannot do that automatically?
- why do I have to do that manually?
It is because in most cases we want to move the models between computers and images, and
we do not want to hardcode the full path in the model.
If the VerveineJ/inFusion Importer Wizard would work in Moose, it could set this
transparently, but if we depend on an external solution we want to have the least amount
of hardcoded things.
Cheers,
Doru
Stef
On May 24, 2011, at 3:13 PM, Tudor Girba wrote:
--
www.tudorgirba.com
"Problem solving efficiency grows with the abstractness level of problem
understanding."
Hi,
Yes.
First, you should import the sources like this:
PATH_TO_verveine.extractor.java/verveine.sh -Xmx 2000m -- .
Second, you have to point the Moose model to the root folder:
http://www.themoosebook.org/book/externals/import-export/root-folder
Alternatively, you can place the sources in a folder src/MOOSE_MODEL-NAME under the
moose.image. It would be like:
moose.image
src/
/MOOSE_MODEL_NAME (this is the folder that you provided to verveineJ)
Cheers,
Doru
On 24 May 2011, at 15:03, Stéphane Ducasse wrote:
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev Hi guys
I did import FAMIX model from file sources with verveineJ and I would like to see the
code
of the java method when I use a browser. Now I do not see the code.
Should I do something special.
Stef
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
www.tudorgirba.com
"Relationships are of two kinds: those we choose and those that happen. They both
matter."
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev