Ok so I was wrong.
do you want me to have a look?
Do you have a list of todo for moose (I should check the bug tracking
system)?
Here we will do a big pass on what hani has been doing and we would
like to propose a clean
version for integration.
I do not remember if moose imports class extension but I will need
that so we may have a look (may be not in the importer itself for now
because we just need that for squeak so we can first look for all the
* and attached them to the right package. )
time time time..... grgrgrgrgrgrgrgrgrgrgrgrg
stef
On 28 avr. 07, at 08:58, Tudor Girba wrote:
Hi Stef,
Don't be sad, ImportingContext is still in use :).
The FullImportPreferences and FastImportPreferences are not used,
at least not in the SmalltalkImporter. But you are right in that
those classes should be just implemented as methods in
ImportingContext.
Cheers,
Doru
On Apr 28, 2007, at 8:29 AM, Stéphane Ducasse wrote:
Hi
why the new importer does not use the importingContext but Full
preferences
The importing context was providing a semantics consistency for the
imported models
and we could decide what do load dynamically not been forced to
define a new class for a new configuration of entities to be loaded.
Sometimes I feel sad to see all the efforts I spent in moose not even
used.
Stef
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
Tudor Girba
www.iam.unibe.ch/~girba
www.iam.unibe.ch/~girba/blog/
"No matter how many recipes we'll know, we'll still value a chef."