nice :)
We should apply your dependency matrix on Squeak this summer.
For now continue to apply it on moose and report the problems
I will fix them.
Stef
Hi,
It's fine. MooseCore depends on nothing now.
Romain
-----Message d'origine-----
De : Stéphane Ducasse [mailto:stephane.ducasse@univ-savoie.fr]
Envoyé : dimanche 22 juin 2008 22:18
À : peirsro(a)ensieta.fr; Related to the development of Moose and other
related tools
Objet : Re: [Moose-dev] MooseCore depends on other packages
Hi romain
can you check because I fixed the problems you kindly reported :)
Stef
On Jun 19, 2008, at 11:57 AM, Romain PEIRS wrote:
Hi,
I would know why the package MooseCore depends on other packages :
MooseUI
and MooseFAMIXModel?
Indeed, the methods defaultViewer in the classes Object and
MooseElement
make an access on the class MooseBrowserEntityUI which is defined in
the
package MooseUI.
Moreover, the methods importClasses, importMethods and
importNamespaces in
the class MooseImporter make an access on the classes FAMIXClass,
FAMIXMethod and FAMIXNamespace, respectively.
Should we move these methods on an other place?
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev