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?
doru? could you have a glance at that? I can fix that but I would like your POV on that
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.
seems to me a missed class extension
-
Moreover, the methods importClasses, importMethods and importNamespaces in the class MooseImporter make an access on the classes FAMIXClass, FAMIXMethod and FAMIXNamespace, respectively.
This is strange that the core of moose is depending on FAMIX. may be should be moved with the tests that used these methods?
Should we move these methods on an other place?
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Hi,
I missed this mail.
Indeed, these methods would better belong to the other packages.
Cheers, Doru
On Jun 22, 2008, at 5:27 PM, Stéphane Ducasse wrote:
doru? could you have a glance at that? I can fix that but I would like your POV on that
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.
seems to me a missed class extension
Moreover, the methods importClasses, importMethods and importNamespaces in the class MooseImporter make an access on the classes FAMIXClass, FAMIXMethod and FAMIXNamespace, respectively.
This is strange that the core of moose is depending on FAMIX. may be should be moved with the tests that used these methods?
Should we move these methods on an other place?
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com www.tudorgirba.com/blog
"Sometimes the best solution is not the best solution."
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@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-
Romain PEIRS -
Stéphane Ducasse -
Tudor Girba