[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    QDom as an alternative to KConfig?
From:       Frerich Raabe <frerichraabe () gmx ! de>
Date:       2001-03-31 21:27:13
[Download RAW message or body]

Hello,

I'm about to add support for filters to KNewsTicker but I noticed an annoying 
thing. KConfig's files look more and more cluttered as the various options 
are added (and therefore saved/read). This is especially true for the filter 
or news source lists, and I currently have to have a single group for each 
news source/filter (for a similiar case, have a look at KMail's config file). 
I also found all these "dead" entries annoying but using KSimpleConfig (which 
doesn't "suffer" from those) is no option.

Therefore, Malte brought up the idea to use some kind of QDom-based 
configuration mechanism. As KNewsTicker's configuration interface is 100% 
encapsulated (in kdenetwork/knewsticker/configfrontend.[h|cpp]), I thought 
about doing exactly that: XML seems fairly well suited for all kinds of 
structured data and I'd take advantage of that for the list of news sources 
and filters.

One disadvantage would be that I wouldn't get merging of global / local 
configuration but KNewsTicker doesn't need it anyway AFAICS as it solely 
relies on the local config.

So, has anybody ever experimented with this or comments/suggestions which 
might help me decide what to do next? I'd like to hear other's opinions about 
this.

- Frerich

[prev in list] [next in list] [prev in thread] [next in thread]