If there are not dependencies back to Moose, having the filter in Fame is genau the right place.

--AA

On Dec 3, 2009, at 11:49 , Cyrille Delaunay wrote:

Ok. But the class 'ParseClientFilter' is not FAMIX-specific and I thougth it would maybe be usefull for fame. If it's not, I can move it into a moose package :)

2009/12/3 stephane ducasse stephane.ducasse@gmail.com but cyrille

FAMIX stuff should not polute Fame so you should extend (subclass) in moose pckage and hope that FAME will take your extension into account.

Stef On Dec 3, 2009, at 11:34 AM, Cyrille Delaunay wrote:

...

Hi,

I just save some changes on the Fame squeaksource repository:

• Implement a 'ParseClientFilter' that enable to parse and import

mse filtering some elements. This is use in Moose to specify the FAMIX elements (FAMIX.Class, FAMIX.Method, ...) you want to import in a MooseModel from a MSE File (This is already available by selecting 'import from MSE' in the MoosePanel).

...

• Two Lint rules in Fame-Util about the Moose issue 143 -> checking if a FM3 class respect the fame name convention

between FM3 and Smalltalk

...

 -> checking if the superclass defined in a FM3MetaDescription  

t exist and is well defined.

...