-6

This idea serves to adjust application user interfaces based on user needs and experience in a simple way.

In any complex application, every easily accessible configuration item and every tool available gets a metainformation class 'Feature' attached to them. The 'Feature' class contains the following properties:
*Feature name
*Short Description
*Pointer to documentation
*a 'pro-ness' value measuring how advanced the feature is (0: basic feature, 100: very advanced feature)
*visibility

Via visibility, the availability of a feature is controlled. Invisible features are always set to default, not to a previously user-applied value. All features are collected in a application-wide registry.

Now two configuration facilities are possible:
1) A list of yes/no choices to (de-)activate features individually (not unlike firefox's about:config, but simpler, since only boolean values)
2) The 'feature bar': A linear graph showing the 'pro-ness' of all available features, and a slider to adjust the desired pro-ness. Either coarse adjustment (basic, intermediate, pro) or fine adjustment of the 'pro-ness' value are possible. Individual choices from 1) override this one.

Obviously, complex applications (e. g. koffice) have to gain most from this.

I'm working on some think called libgreattao(I'm worst world developer, but any free time I tries to develop ).

See at sourceforge the description. I have first prealpha version on my computer, but I must made more polish to get it working.