6ucky / variamos-web-3.1 Goto Github PK

Because of that, I create a global functionality, called getModelInfo() --check last commit--. This way if someone wants to include a new model in the project structure, he/she just need to create the model file (i.e. feature.js) and just to include a meta data in the getModelInfo function and that's it.

Then, I need your help to modify the filetree.js, and the multi-models.vue files, to use that function, and generate the proper project structure without having to manually modify those files to include new models (you agree?).

For example, the next code must be updated. In the previous image, there is only one model ("feature") which appears in the "application" subfolder, and the "adaptation" subfolder. Later if someone wants to include a new model in the "application" subfolder, he/she just need to modify the getModelInfo meta data and that's it. (Sounds better don't you think so?).

Therefore, you should not predefine the number of childrens of each project folder. For example, in the next image you are saying a "domain" folder will have 3 childrens. But this should be automatically generated, based on the quantity of models that will be displayed in the domain folder. Check first image of this email. So, again, use the getModelInfo function to make it generic.

• the sub_cotalogue.vue must be generic

• generic tree structure for each model

• generic models

• generic file management system

• generic tabs

When a feature model is constructed, it can automatically identify the root feature and leaf feature. The leaf feature will be shown in the binding model.

1/2 d

1. Range constraint transformed from xml to HLVL
2. Put * in the range
3. False product line has only one solution
4. void product line has no solution
5. False optional feature
6. Check multiplicity conflicts (change range to and to check solutions)