RFC: KConfig XT (KDE 3.2)
ben at meyerhome.net
Sun Mar 16 12:01:59 GMT 2003
On Saturday 15 March 2003 4:56 pm, Waldo Bastian wrote:
> On Saturday 15 March 2003 17:39, Navindra Umanee wrote:
> > Waldo Bastian <bastian at kde.org> wrote:
> > > Drawbacks:
> > > * We rely on default configuration files being properly installed.
> > What happens when configuration files are not properly installed?
> > Crash?
> Hard to tell. E.g. the application reads the config entry and it expects to
> get a reasonable default if the user hasn't configured anything. If the
> configuration file isn't installed it will get something like 0, Qt::black
> or an empty string. Of course the same already happens if you edit the
> config file in you home-directory and add empty Key= statements.
> An application should never crash on it, but having e.g. black text on a
> black background doesn't make an application very usable.
> It's not the only file that is required though. If your application uses
> XMLGUI and it can't find the XML file describing its menus, you will end up
> with a pretty messed up application as well.
So an application would have to store the default setting within itself just
in case the default file wasn't found which is brings us full circle.
More information about the kde-core-devel