[ < ] [ > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

3.3 Platform-specific per-user configuration

CrystalSpace' configuration system provides the storage of user-specific settings, utilizing a platform's common protocol for this, while being completely transparent to the application. While knowledge of the details is not necessary, there should be an understanding of some basic issues so the the user-specific settings can "play nicely" across all platforms.

The unique identifier

To distinguish between different configurations for the same user a unique identifier is used. The Application ID (see section 3.2 Configuration File) is directly used as such an unique identifier. How in detail it is used to distinguish between configurations is up to the individual platform-dependent implementation. However, to make the unique identifier 'as unique as possible', it is strongly recommended that an application ID always has the shape `<Producer>.<ProductName>'. If the application is a tool that is only meaningful if used together with CrystalSpace, or if you think your name is not worthy enough to be used in such an exposed place as the per-user configuration, you can also use something generic like `CrystalSpaceApp' or just `CrystalSpace' (latter one is also at least used by CrystalSpace itself, so be wary of possible conflicts).

3.3.1 Storage of per-user configuration on Windows  
3.3.2 Storage of per-user configuration on Unix and Linux  


[ < ] [ > ]   [ << ] [ Up ] [ >> ]         [Top] [Contents] [Index] [ ? ]

This document was generated using texi2html