Moose and its configurations

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Moose and its configurations

abergel
Hi!

Getting a proper configuration of moose is not easy and probably will not be produced tomorrow. I spent some time with our Metacello Sansei, and we did not fix it.

Many cycles from the configuration can be removed by simply removing the dependency on ConfigurationOfMoose. For example, ConfigurationOfDSM, ConfigurationOfKumpel and ConfigurationOfSmallDude explicitly load Moose. Is there a reason for this?

Saying that DSM, Kumpel and SmallDude can only be loaded in a Pharo with Moose will simplify the situation in my opinion.

Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.





_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Reply | Threaded
Open this post in threaded view
|

Re: Moose and its configurations

Tudor Girba-2
Hi,

Indeed. But, the issue is deeper: it is because we do not have an explicit architecture that people bundle together code at multiple levels. So, we need to fix our definition of the architecture first (see the mail entitled "major repackaging planned").

Now, let's take SmallDude. It actually has two components:
a) the duplication computation mechanism
b) the integration in FAMIX

a) is an algorithm engine that should be reusable without FAMIX. b) is a meta-model extension. If they would be packaged separately, only b) should need dependencies to the core of Moose.

Furthermore, if we split the overall Moose into multiple components along the idea of engines, we will actually have b) only depend on the ConfigurationOfFamix. and ConfigurationOfMoose will simply put all these together.

The only problem is that if we do that, we can get in an even bigger mess due to the amount of Configurations. So, that is why I want to see what can be done about this part.

In any case, at the very least we will split the current configuration into ConfigurationOfMooseCore (on which others like SmallDude can depend) and ConfigurationOfMoose.

Cheers,
Doru


On 20 Oct 2011, at 00:19, Alexandre Bergel wrote:

> Hi!
>
> Getting a proper configuration of moose is not easy and probably will not be produced tomorrow. I spent some time with our Metacello Sansei, and we did not fix it.
>
> Many cycles from the configuration can be removed by simply removing the dependency on ConfigurationOfMoose. For example, ConfigurationOfDSM, ConfigurationOfKumpel and ConfigurationOfSmallDude explicitly load Moose. Is there a reason for this?
>
> Saying that DSM, Kumpel and SmallDude can only be loaded in a Pharo with Moose will simplify the situation in my opinion.
>
> Cheers,
> Alexandre
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel  http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
>
>
> _______________________________________________
> Moose-dev mailing list
> [hidden email]
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev

--
www.tudorgirba.com

"Quality cannot be an afterthought."


_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev