Sometimes I have no idea what to do
and I'm stuck
belongsTo
<MSEProperty: #belongsTo type: #FAMIXContainerEntity> <derived>
^self shoudBeImplemented
what does it means?
Why there is no instance variable somehow related to belongsTo in
FamixNamedEntity?
Yes I feel a bit alone some times.....
Stef
Looking at SqMoose, how do I get a Fame description from the Moose
entity?
It looks like if I send a #mooseDescription message to this entity,
the model will be initialized/accessed through MooseModel class>>meta.
However not sure what is the metamodel in this case: is it Famix?
Because there is also a MooseModel class#initializeFAMIXDescriptions
Anyway, the protocol described in the Sosym paper is different, so
it's disturbing!
--
Simon
I updated the iPlasma page on the moose website:
http://moose.unibe.ch/docs/faq/importWithiPlasma
People wanting to conduct an experiment over C or C++ code might find
this interesting.
Cheers,
Alexandre
On 21 Oct 2008, at 09:58, Tudor Girba wrote:
> Hi Alex,
>
> Could you add an entry in the documentation for this one?
>
> Cheers,
> Doru
>
>
> On Oct 21, 2008, at 9:56 AM, Alexandre Bergel wrote:
>
>> Thanks Radu,
>>
>> Cheers,
>> Alexandre
>>
>>
>> On 21 Oct 2008, at 09:47, Radu Marinescu wrote:
>>
>>> Hi Alex,
>>>
>>> there is no HOWTO (at least none that I know of... may be Doru has
>>> one). But here is in brief how you should do it.
>>>
>>> 1. Go on a Windows machine (VM is also ok)
>>> 2. From the iPlasma package go to iPlasma/tools/mcc and start
>>> mcc.exe with the following parameters
>>> mcc <source_folder> <dat_folder>
>>> whereby <source_folder> = the root folder of your source files
>>> (take care to indicate a folder that includes BOTH .c and the
>>> HEADER files .h !!)
>>> <dat_folder> = is a folder that you create somewhere on the
>>> disk. It's the place where mcc will place its results. After
>>> mcc.exe has run, the <dat_folder> should contain a set of *.dat
>>> files.
>>>
>>> 3. From the iPlasma package go to iPlasma/tools/iPlasma folder and
>>> depending on the machine you are using start iPlasma using
>>> build.sh (on UNIX/Mac) resp. insider.bat (on Windows)
>>>
>>> 4. After the GUI of iPlasma (called Insider) started select from
>>> the menu Load | C++ (from Mcc tables) ... as in the first figure.
>>> <pastedGraphic.tiff>
>>>
>>> 5. In the "Model loader" that will open in the "Source path" edit
>>> field specify the <dat_folder> created in Step 2. You don't have
>>> to write anything in the "Cache file name" field.
>>>
>>> 6. After the model has bee created from the *.dat files found in
>>> the <dat_folder>, in the right panel right-click on the root
>>> entity (the System) and from the pop-up menu select "Run Tool...|
>>> Moose MSE Exporter" . In the window that will pop-up you have to
>>> specify the name of the MSE file to be created (with complete
>>> path!)... and wait until the MSE file is created.
>>> For large projects this might take a while, and unfortunately
>>> there is no progress bar, nor any obvious sign that the process is
>>> completed. You can check that the process is completed in 2 ways:
>>> a. check that the MSE file stops to be modified (in Finder)
>>> b. check if the iPlasma frontend is responsive (if it is then the
>>> process is finished)
>>>
>>> <pastedGraphic.tiff>
>>>
>>>
>>> I hope this helps!
>>>
>>> Concerning the other enhancements, although we are late compared
>>> to what we promised, the update will arrive very soon (hopefully
>>> earlier than a week from today).
>>>
>>> cheers,
>>> radu.
>>>
>>>
>>>
>>> -----
>>> Use Eclipse? Try inCode!
>>> www.intooitus.com/inCode.html
>>>
>>>
>>>
>>>
>>> On Oct 17, 2008, at 1:28 PM, Alexandre Bergel wrote:
>>>
>>>> Hi!
>>>>
>>>> I went through http://loose.upt.ro/iplasma/, but I am unsure how
>>>> to generate MSE files from a set of .c files.
>>>> I do not know how to generate tables from MCC, MEMORIA.
>>>>
>>>> Is there a short howto on this?
>>>>
>>>> Cheers,
>>>> Alexandre
>>>>
>>>> --
>>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>>>> Alexandre Bergel http://www.bergel.eu
>>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>
>> --
>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>> Alexandre Bergel http://www.bergel.eu
>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>>
>>
>>
>>
>>
>
> --
> www.tudorgirba.com
> www.tudorgirba.com/blog
>
> "In a world where everything is moving ever faster,
> one might have better chances to win by moving slower."
>
>
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hello,
I search a visualization that help me easily to see the evolution of
entities. Something like what you can see in the attached file.
I do not remember what is the name of a such style of visualization
but I just remember that Doru showed me a visualization very similar
on Mondrian but I do not remember what was the name of the methode...
can some one help me to know if a such visualization is implemented
somewhere?
thanks,
Hani
Hello,
Really after one hour of thinking that somewhere there is a bug I
found the selectors
InheritanceDefinition>>superClass
and
InheritanceDefinition>>subClass
which are not accessors and they are different of:
InheritanceDefinition>>superclass
and
InheritanceDefinition>>subclass.
Could you please illustrate why we need the selectors #superClass and
#subClass when we have the accessors #superclass and #subclass?
Specially, could you explain why both return a group that will always
contain one, and only one, element?
thanks,
hani
Hi adrian
I was wondering which meta models you have expressed in FAME?
we have FAMIX30. Now did you give a try to model EMOF?
Now do you think that it would be possible to redo the import
of EMOF sara and pierrick did but using FAME?
Of course we would have the same limits with multiple inheritance.
Stef
