Should Files and Folders be generated? about famix

[anneetien]

I think it is a good idea to move File and Folder from Famix-Generator.

But I don't understand why not using traits to manage it? There will still be a TWithFile trait, no?

Managing homogeneously things will be easier according to me. Starting to manage something through classes and other through traits will be the mess

[jecisc]

The idea of the generators is to be able to define multiple meta-models.

Traits are here to define concepts to reuse between multiple MMs.

I have the impression that things such as Tags, File representation, Duplication, etc are "options". Those options should be able to work with any MM and should not be part of the generator.

If we make them part of the generator, it means that we need to generate one MM for each combination of options the user might need. For example:

• Java Vanilla
• Java with tags
• Java with files
• Java with duplication
• Java with tags and files
• Java with tags and duplication
• Java with files and duplication
• Java with tags, files and duplication
• ...

It's the reason I think those "options" should be things defined only once and working for every MM if possible. In that case, we don't need traits since we do not need to share the behaviour to reuse between multiple MMs.

[anneetien]

A bit like MooseQuery, you propose to define these concepts independently of the MM?
I agree on the principle.
And I think we could add the metrics eventually that way.

Can you, please, explain a bit better what would be your solution of file management and how it is linked to Fame or Famix?

[jecisc]

What we could do for files and folders is to have classes FamixFile and FamixFolder with meta description.

Then, we could add as extensions of FamixTSourcedEntity the opposites that would be stored in the private state.