HI guys
we will send the following version of a deliverable to the ANR.
We plan to use this version (and its follow up) to describe FAMIX30 officially.
Any feedback is welcome. I should thank doru for the diagrams (I put you as a co-author and if you do not want I can remove you).
We will maintain this version
+ add a hal entry and a bib entry for it.
I will send it around.
stef
Alex
two remarks:
- what is the level of reification because we reify a lot and it can be discarded.
- did you check the orion model
because with orion you only represent the delta and this is a big difference.
Stef
On Nov 24, 2011, at 2:05 PM, Alexandre Bergel wrote:
> Having a reification in Moose of 100 versions of Mondrian for example :-)
>
> Just answering the question 'Which classes and methods of Mondrian have changed more than 10 times since the day Mondrian was born?' cannot be easily done without a lot of memory
>
> Alexandre
>
>
> On 24 Nov 2011, at 03:27, Francois Stephany wrote:
>
>> I'm wondering: how big is a dataset > 500MB ? I've no idea how big it is.
>> Alex, what is your use case (in practice!) for more than 500MB?
>>
>> On 23/11/11 18:25, Igor Stasenko wrote:
>>> It is problematic, and requires different memory management than we
>>> currently have.
>>> I think if you need really big data sets, then use gemstone, which is
>>> developed to deal with that specifically.
>>
>
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
>
>
>
Hi,
I have some problem to import a moose model that i have previously exported.
The error that appear is the following:
'Element ''Famix'' not found.'
The MSE exported from the MooseModel is attached.
The elements of the model contain a method "annotation" that look like this:
annotation
<MSEClass: #Column super: #FAMIXRelationalEntity>
<package: #FAMIX>
Once i have the moose model i export it with "exportToMSE" than i try to import the model again with "importFromMSE".
Any idea why i have that problem? Do you need more info to understand the problem?
Cheers,
Fabrizio
FAMIXBehaviouralEntity is an abstract superclass for any kind of behavior.
For example, functions and methods. It has a name because it is a named
entity but it also has a signature in the format: methodName(paramType1,
paramType2). The signature property is necessary for a behavioral entity.
An external parser should provide a few metrics that cannot be derived from
the model such as cyclomatic complexity, numberOfStatements and
numberOfConditionals. Other metrics can be computed from the model if
enough information is provided such as numberOfLinesOfCode (from source
anchor) and numberOfComments (from FAMIXComment).
It provides properties to manage:
(i) parameters
(ii) local variables
(iii) accesses to variables, and
(iv) invocations to and from other behavioural entities.
Optionally, it can also specify a declaredType (e.g. return types for
functions). This is useful for modeling behaviours from statically typed
languages.
Strange, the Fuel tests are green on my image and I have the last version of all packages.
Alexandre
On 23 Nov 2011, at 18:27, admin(a)moosetechnology.org wrote:
> See <http://hudson.moosetechnology.org/job/moose-latest-dev/710/>
>
>
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi!
I am building a small browser in Glamour to monitor events. I have a list such as:
constructor list
title: 'events';
display: [ :event | event allEvents ]
Is there a way to refresh the list once the Glamour GUI has showed up?
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi!
We produced a test that shows a bug related to the classScope.
In Moose-Tests-SmalltalkImporter-LAN-AlexandreBergel.10 we added testClassVariable. This test fails. We need to make the appropriate change to make it pass. This bug prevents us from using MooseChef
In our local image we check the belongsTo in the method classScope. This makes mooseChef happy.
Anyone can have a look at it please?
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
FamixInheritance>>name seems superflous because it overrides a superclass
method with the same behavior.
We tried to remove the entity but then a (seemingly unrelated) test is
failing in FamixModelExtractionTest>>testReferenceModel.
We didn't commit this change in the repository fearing that something might
fail.