[Moose-dev] Re: About passing an exporting context to an exporter

On Jul 15, 2011, at 8:02 PM, Tudor Girba wrote: I do not think it does. And we should pass the information at least up to the FMrepository because else we cannot sort it out. It looks a bit too meta for me. so we will have to filter meta model before filtering model :( Now this is clear that linked MooseContext to fame is ugly. It would be good that FAME take this idea of context a bit better. Because right now there is no dependencies checks done so we could filter out inconsistent model. Still the question was also about passing another param vs. storing the context in a moose object. Finally the FMmodel serialization has a problem because it does not have any idea of the model. so we cannot simply save a model with for example a version number that is passed by the model. so the API of basing everything on elements and not on a holder of elements which can have extra properties is not really good because we lose the opportunity to hook more information in it. So I was thinking to add addModel: to FMRepository and to be able to query this model to get extra information. I think that tracability is important.