Uniforming FEM interface methods

[epernod]

Some FEM have similar members and methods but the behaviour slightly changes sometimes.

For example:

• In triangular and tetrahedronFEM, you have to choose the method using an enum: (large, small, etc...). In triangular, Large = 0 and in tetra, Large = 1. Which is stored as string or enum depending on components.
• Same for setter and getter, you have: TriangularFEMForceField::setYoung vs TetrahedronFEMForceField::setYoungModulus. setPoissonRatio vs setPoisson

Could we setup a commun api for those components? Can someone identify one FEM which could be the reference.

[damienmarchal]

+1 about any proposal for unifying the similarities between component toward a more consistent sofa.

[hugtalbot]

Hi guys,

This is a known issue. I think this is related to what @IPeterlik and @hdeling are working on with homogeneous forcefields for linear elasticity and corotated approach. Homogeneous data, methods and behaviors must be respected.

[hugtalbot]

This is already related to #232 #979