Talk:Bibletime2PlatformConsiderations

Install locations

The main point of the M$ article is that applications need to have isolated storages which are not easily accessed by other applications.

"When an application stores data in a file, the file name and storage location must be carefully chosen to minimize the possibility that the storage location will be known to another application and, therefore, vulnerable to corruption. Without a standard system in place to manage these problems, developing ad hoc techniques that minimize storage conflicts can be complex and the results can be unreliable. With isolated storage, data is always isolated by user and by assembly."

I don't find any other important point in that article. And that aspect is already taken care by QSettings. It uses similar techique than for example java package naming convention: company name and application name.

http://doc.trolltech.com/4.2/qsettings.html#platform-specific-notes tells how settings are stored. I would strongly recommend file-based store instead of default Windows registry. We don't have to care about underlying file format or any other techical detail, Qt takes care of them.

"The paths for the .ini and .conf files can be changed using setPath()." Using files and setPath() allows BibleTime to run directly from USB-disk or CD-rom (under Windows). I can't see any reason to use registry. --Eeli