Moving KPrefs from libkdepim to kdelibs

Benjamin Meyer ben at meyerhome.net
Mon Jul 21 13:56:22 BST 2003


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Monday 21 July 2003 8:14 am, Cornelius Schumacher wrote:
> A couple of people have asked, if we can move KPrefs from libkdepim to
> kdelibs. It's a class which provides easy access to configuration
> information stored via KConfig in a type-safe way with as few redundant
> code as possible, in particular without specifying config file keys and
> default values at more than one location in the code.
>
> KPrefs doesn't address any GUI issues, it's just an abstracted layer on
> configuration data and should be orthogonal to the different GUI approaches
> for configuration we currently have.
>
> The class is used by KOrganizer, Kontact, KAddressBook, KBugBuster and
> Kandy since a long time and should be pretty stable. See e.g.
> kdepim/korganizer/koprefs.{h,cpp} for an example how to use it.
>
> Any objections to moving kdepim/libkdepim/kprefs.{h,cpp} to
> kdelibs/kdecore?

I have no objections sense the point of kdelibs is to provide a place to store 
code that is used by multiple applications.  I simply want to point out that 
KAutoConfig exists in kdecore and provides a very similar feature set.

- -Benjamin Meyer

- -- 
Public Key: http://www.csh.rit.edu/~benjamin/public_key.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE/G+L71rZ3LTw38vIRAtffAJ9dCGaIMb8Bnj0I0tcOnAC4cRvAxQCdH/px
Qdu4WM16nqLHUeM0gRBM47o=
=eZOL
-----END PGP SIGNATURE-----





More information about the kde-core-devel mailing list