Dear list
With great pleasure I have seen some new activities blossoming around
SqMoose and Famix3 in the last few weeks: porting some projects from
VW (Mondrian, Hismo), using Famix3 (Cook)...
Now it will become increasingly harder to be aware of all changes and
in particular, of current development status for each project.
Since we dont have some kind of continuous integration system right
now, I created a page on the wiki which more or less serves this
purpose:
http://code.google.com/p/moose-technology/wiki/DevLog
I kindly invite any current developer to contribute to this page, so
that we can have a clear picture of where the moose development is
going.
Of course, dont forget the regular issue list for the precise, fully
described issues.
http://code.google.com/p/moose-technology/issues/list
--
Simon
Hi!
I was wondering what is the equivalent of FAMIX2Access>>accessedIn in
Famix 3?
FYI, I am migrating class blueprint in Pharo.
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
I just ported it.
Few comments:
- FAMIX 3 is used instead of FAMIX2 (I used MooseEntity instead of
AbstracEntity@VW. AbstractEntity does not exist in Pharo)
- Used Fame Annotation (look at annotation on the class side of Hismo
classes)
The port is not complete however, some test still are still yellow or
red. Maybe someone can help on that.
I also added HismoTest>>testSimple1 to help me understand how to use
histories. The test is yellow, help will be appreciated :-)
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi Alex,
I guess this mail was aimed at moose-dev :)
Have a look here:
http://moose.unibe.ch/docs/famix/famix3.0/classdiagram
NamedEntity>>parentPackage points to the FAMIXPackage.
NamedEntity>>belongsTo
- points to a ContainerEntity and it describes the language scope
(e.g., FAMIXNamespace)
- however, it is derived (that is why in the diagram it appears with /
in front). In this case this means that it will get overriden in
subclasses to point to something else. This is useful for providing a
polymorphic API for getting to an outer language scope (e.g., from
FAMIXClass to FAMIXNamespace)
Type>>container
- points to the container, and it is not derived.
Type>>belongsTo returns self container
Cheers,
Doru
On 27 Mar 2009, at 23:37, Alexandre Bergel wrote:
> Dear List,
>
> What is the difference between NamedEntity>>parentPackage,
> NamedEntity>>belongsTo and container ?
> I guess one should be for the package, and another one for the
> namespace. But a third?
>
> Cheers,
> Alexandre
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
>
>
>
> _______________________________________________
> Pharo-project mailing list
> Pharo-project(a)lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
--
www.tudorgirba.com
"From an abstract enough point of view, any two things are similar."
Hi All,
Several time I saw the need to add a particular edge between two nodes
that I know. I added a new method addEdgeFrom:to: in ViewRenderer.
Here the appropriate test. Feel free to comment.
-=-=-=-=-=-=-=-=-=-=-=-=
testAddEdge
| view |
view := MOViewRenderer new.
view nodes: (1 to: 2).
view addEdgeFrom: 1 to: 2.
window := view open.
self assert: (view root edges size = 1).
self assert: (view root edges first source =
(view nodeForDomainValue: 1)).
self assert: (view root edges first target =
(view nodeForDomainValue: 2)).
-=-=-=-=-=-=-=-=-=-=-=-=
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi Jannik,
I enhanced Mondrian with what you asked for (preferred size in
presence of subviews (was existing in VW but not in Pharo), extra
method for edge addition).
However, I still cannot open your DSM. The reason is that
FAMIX2Package does not understand color:
FAMIX2Package new color: Color blue
Again, I am not sure this is the best way to do this. Shape should be
aware of colors, not the domain.
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi All,
I added a new package in Moose, that use Mondrian to display some
visualization. Moose is now dependent on Mondrian.
Rio is used for file accesses.
I updated MooseLoader.
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi All,
On the LAN example, some metrics raise an exception:
FAMIXClass>>fanIn, fanOut, numberOfComments, tightClassCohesion
Just try:
MooseModel root first allClasses first tightClassCohesion
or
MooseModel root first allClasses first fanIn
I commented their pragma out in the last version of Famix-Core.
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi All,
There is a problem I have been working on for a while.
Open an easel (MOEasel open), and execute the script
view shape: (MORectangleShape new width: 30; height: 20; text: 'A').
view nodes: (1 to: 20)
outer rectangles of the nodes do not get displayed correctly. I have
no clue why. The entry point I guess is MORectangleShape>>display:
anElement on: aCanvas
A beer for the one who found it :-)
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
