[Morphic] Some feedback about the package organization

stéphane ducasse ducasse at iam.unibe.ch
Sat Feb 11 09:57:01 CET 2006


On 11 févr. 06, at 00:27, Juan Vuletich wrote:

> Hi Stef,
>
> I wasn't thinking about it, but sounds good. What do you mean by "a  
> layered architecture"?

instead of two big packages Morphic and Morphic Extras

I would like to have
	Morphic-Core
	Morphic-Widgets
	Morphic-Examples
	Morphic-ExtraWidgets
	Morphic-ExtraWidgets-Led
	Morphic-Oldies

(If we want we can have then another Packages named Morphic that only  
contains (no code)
but just the other packages as required packages. I think that this  
is the best way to manage configLine of entities
changing together. This way refactoring or cleaning Morphic would imply:
	loading the map and saving it and its package at once but still make  
sure that we can remove part. but for now we do not
really need to worry about that.)

As an example...
The idea would be that we can remove as much as possible
and only load what we want:
	for example some packages such as LedMorph are excellent and well- 
self contained and coherent
	while other are just a bag of stuff and other have lot of reference  
to other packages

> BTW, if I remember well, CDScreenShotMorph was touched about a  
> month ago, and I tested it as the contributor of the code said (was  
> it Jerome?), and everything looked fine... Let me take a look.
For this one, I would put it into the
	MorphicSimpleExamples




More information about the Morphic mailing list