RFC KAutoConfig

[Cornelius Schumacher]

On Thursday 13 February 2003 17:03, Benjamin Meyer wrote:
>  *
>  * The name of the widget determines the name of the setting.  The initial
>  * value of the widget also is the default when asked to reset.
>  *
>  * This class was created to further follow the DRY principle.
>  * DRY - Don't Repeat Yourself

One main problem with config settings is that you have to repeatedly write the 
name of the setting (which is used as key in KConfig) as string, e.g. at the 
place in the application where the setting is read and at another place where 
it is written (in case of KAutoConfig this would be in the ui file, right?).

This is a problem because the compiler isn't able to do any checks on them, so  
typos can be very hard to find.

Does you class address this problem in any way?

>  * The only major downside to this class is that it is almost guaranteed
> (?) * to be slower then the normal implimentaions.  Thus the design of the
> class * is geared towards improving the speed of its operation.

How much slower is KAutoConfig than the traditional way?

-- 
Cornelius Schumacher <schumacher at kde.org>