Quote:
Originally Posted by mblrdr
I only called it trash because this is an unnescessary concept imho. Sorry about the wording.
I wouldn't be so pushy if I hadn't nearly all my software in portable form. None of these uses such a concept (different between portable vs non-portable) but I guess I'll find a solution. There are lot of sites which do portable versions of "install only" programs.
Remembering the last library does not need \AppData at all if done the right way (for example an *.ini file).
Still I'd like to know the developers standpoint.
Don't get me wrong I really like calibre. It's awsome.
|
Installed Calibre has .INI files galore (except they are primarily .json files), they are a
carbon copy of what's in Calibre Portable\Calibre Settings folder. The reason they are in AppData is to allow different users to have different settings. Example: Mary Nerk likes to have Segoe UI [9pt] as the Interface font, Fred Nerk prefers Papyrus [12pt]. Calibre accommodates that by having the settings in AppData. This can be dispensed with via the CALIBRE_CONFIG_DIRECTORY Environment Variable.
The only 'settings' that calibre puts in the registry are those that
Windows needs to know about, such as the registration of the calibre:// protocol handler.
BR