Configuration API

[Waldo Bastian]

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

On Thu April 29 2004 22:05, Claes Holmerson wrote:
> > At the storage level, KConfig considers all values utf-8 strings. When the
> > application asks for the value it specifies the desired type and only then
> > will the value be converted to that type. With KConfigXT we generate code
> > for the access methods so that we get type-safety from the compiler based
> > on the type specified in the meta-data. In both cases the backend has no
> > actual knowledge about the type.
>
> It might be a good idea to borrow some of the primitive data types that
> are defined in the XML Schema Spec (Part 2), and use them in the backend
> storage.

KDE has plenty of primitive data types already, it's just that the backend 
doesn't care about them.

In case someone is collecting requirements, we use:
String, StringList, Font, Rect, Size, Color, Point, Int, UInt, Bool,
Double, DateTime, Int64, UInt64, IntList, Enum, Path, Password

Cheers,
Waldo
- -- 
bastian at kde.org  |   SUSE Linux 9.1 Order Now!   |  bastian at suse.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQFAkWiqN4pvrENfboIRArq6AJ43scuGCrReW8QYYqsdnqxKRPk4bgCfRbC1
0qxgfOr1c2Zzo6M+P1U86zQ=
=YZ5w
-----END PGP SIGNATURE-----