24 Jun
2008
24 Jun
'08
8:42 p.m.
done :)
On Jun 24, 2008, at 7:10 PM, Tudor Girba wrote:
Agree :)
Doru
On Jun 24, 2008, at 5:15 PM, stéphane ducasse wrote:
Hi Doru
There are several methods in MooseFamixModel that depend on
MooseFamixExtensions.
I suggest to move them there. Do we agree?
- la méthode hasSubclasses dans FAMIXClass
(Root::Smalltalk::SCG::Moose::FAMIXClass.hasSubclasses()-
--
www.tudorgirba.com
www.tudorgirba.com/blog
"Obvious things are difficult to teach."
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
numberOfChildren())
- la méthode
hasSuperclasses dans FAMIXClass
(Root::Smalltalk::SCG::Moose::FAMIXClass.hasSuperclasses()-
numberOfParents()
)
- la méthode hasEmptyBody dans FAMIXAbstractBehaviouralEntity (2
invocations:
Root
::Smalltalk
::SCG::Moose::FAMIXAbstractBehaviouralEntity.hasEmptyBody()-
numberOfAccesses()
et
Root
::Smalltalk
::SCG::Moose::FAMIXAbstractBehaviouralEntity.hasEmptyBody()-
numberOfOutgoingInvocations()
)
Then in MooseUI
mooseKill <menuItem: 'Kill' nameKey: nil menu: #(#menuBar #tools
#mooseUtilities) position: 1> SCG.Moose.MooseModel kill
depends on MooeUIExtensions
So may be we should move it there.
Stef
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev