Hi,
I went over some of the loading scripts and I noticed that there were a number of duplicated scripts which led to inconsistencies. So, I now changed them as follows.
Every loader has a load method that should load all the prerequisites. For example, we have: - MooseLoader>>load - GlamourLoader>>load - MondrianLoader>>load
When loading a prerequisite project that is within the realm of Moose (e.g., Glamour, Mondrian), instead of hardcoding the script we delegate to the appropriate loader. For example: MooseLoader>>loadMondrian Installer ss project: 'Mondrian'; install: 'MondrianLoader'. (Smalltalk at: #MondrianLoader) load.
Like this all loading scripts are in exactly one place.
The next step would be to go towards something like the Seasiders have with their Package map in which we declaratively build a Moose landscape with all dependent packages. That would be nice both for loading and for creating a dependency visualization.
Cheers, Doru
-- www.tudorgirba.com
"Yesterday is a fact. Tomorrow is a possibility. Today is a challenge."
On 17 mai 09, at 14:59, Tudor Girba wrote:
Hi,
The next step would be to go towards something like the Seasiders have with their Package map in which we declaratively build a Moose landscape with all dependent packages. That would be nice both for loading and for creating a dependency visualization.
It sounds like something circumventing the dependency mechanism of monticello (not necessarily a bad thing). Can you give more details on the rationale and specs of Package map?
-- Simon
Thanks doru This is good that you did that. For my side I only maintained MooseLoader load.
Stef
On May 17, 2009, at 2:59 PM, Tudor Girba wrote:
Hi,
I went over some of the loading scripts and I noticed that there were a number of duplicated scripts which led to inconsistencies. So, I now changed them as follows.
Every loader has a load method that should load all the prerequisites. For example, we have:
- MooseLoader>>load
- GlamourLoader>>load
- MondrianLoader>>load
When loading a prerequisite project that is within the realm of Moose (e.g., Glamour, Mondrian), instead of hardcoding the script we delegate to the appropriate loader. For example: MooseLoader>>loadMondrian Installer ss project: 'Mondrian'; install: 'MondrianLoader'. (Smalltalk at: #MondrianLoader) load.
Like this all loading scripts are in exactly one place.
The next step would be to go towards something like the Seasiders have with their Package map in which we declaratively build a Moose landscape with all dependent packages. That would be nice both for loading and for creating a dependency visualization.
Cheers, Doru
-- www.tudorgirba.com
"Yesterday is a fact. Tomorrow is a possibility. Today is a challenge."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-
Simon Denier -
Stéphane Ducasse -
Tudor Girba