Facilitate the use of the optimal configuration of a component

[jim-bcom]

PROBLEM
Currently XPCF configuration files tend to systematically define a lot of a component properties.
These component configurations are often cut'n pasted in many configuration files in projects that uses the same component.
This leads to several issues:

• once a satisfying component configuration has been found in a project, other projects don't benefit from it unless these changes are ported to every users of the component
• if a component adds, remove, rename or changes the type one of its property, this changes must done in every xml files
• configuration files for complex applications are big. A user of a component shouldn't have to understand the inner workings of it, some propeties should remain up to the expert/component developer to use.

SUGGESTED SOLUTIONS

1. Simplify configuration files

• Init component class members that are bound to properties with optimal default value (for most cases)
• Remove as much properties from the xml files. Some use-case specific cannot be removed such as file path, ...

2. Share configuration files for a component

• Pipeline/Sample using a component from a module could retrieve this defaut configuration file.

NOTES

• For 1 we must ensure that not defining a property in the configuration file results in setting the value defined in the initialization of the class member in the C++ file.