Hi Santiago,
I noticed that you committed a change to Famix-Core.
The comment says that the intention of the commit was to add WMC to
package. This is Ok.
The problem is that in the process, you also:
- deleted FAMIXClass>>isInterface and FAMIXClass>>isInterface:
- introduced null checks in core methods (classScope, packageScope and
namespaceScope)
I am sure that the first one was a mistake. But, for the second one
you should have raise it for discussion because it has to do with
changing the semantics of those methods.
In general, changes to Core classes should be treated with more care
(this is valid for me as well) :)
Cheers,
Doru
--
www.tudorgirba.com
"Every thing has its own flow"
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 754 by alexandr...(a)gmail.com: MoosePanel and evaluation tab
http://code.google.com/p/moose-technology/issues/detail?id=754
The evaluation tab works with Cmd-o, but it operates only if the text is
selected. Which is awkward
Hi!
Apparently there is something wrong I do in the evaluation script pane in a MoosePanel.
How can I have the result of the script in the right most pane?
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi!
We are currently implementing some statistics functionalities in Hismo.
The idea is to be able to identify correlation between two metrics, computing the standard deviation.
We will commit in a couple of hours.
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
FAMIXAssociation is an abstract superclass for relationships between Famix
named entities. It defines a polymorphic API refined by subclasses:
essentially from, to, next and previous.
>From and To properties are abstract at this level, but specific
implementations can have multiple ends and properties.
For example, FAMIXInheritance has:
(i) From mapped to the subclass;
(ii) To mapped to the superclass.
Next and Previous properties provide an order of the appearence of these
associations in code. The order is calculated within a particular
relationship for example, method invocation order within a calling method
(from).
For example in java, the following code
method a() { b(); c(); }
will produce two invocation associations first from method a to method b,
and second from method a to method c. These associations are bound together
and can be navigated with previous and next.
Hi!
Metrics for smalltalk code are lazy computed. It is only when you send #numberOfLinesOfCode to a class or a method that the value is actually computed from the code present in the image.
The current schema is not really optimal when loading multiple versions.
The problem we are facing is that we need to manually call the metric methods after each version is loaded.
Is there a way to force the metrics to be computed while importing code?
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
What is the different between objects represented
by FamixUnknownSourceLanguage and FamixCustomSourceLanguage?
Do we have an example to show the difference?
thanx
Usman and Nicolas
Status: New
Owner: ----
CC: tu...(a)tudorgirba.com
Labels: Type-Defect Priority-Critical
New issue 752 by alexandr...(a)gmail.com: New Mondrian Easel
http://code.google.com/p/moose-technology/issues/detail?id=752
- When the UI thread crashes, a new easel has to be opened. For example,
execute the script:
-=-=-=-=-=-=-=-=-=
self foo
view nodes: (1 to: 20)
-=-=-=-=-=-=-=-=-=
It will raise a debugger. Remove the "self foo", and press the check or
Cmd-s, then I have the same error, even though "self foo" is not in the
script.
The easel is barely usable without this :-(