Quote:
Originally Posted by theducks
# 1) Calibre would need UAC admin elevation every metadata or book update if it did  put data in Program files (That is so Windows 3.1 type thinking  )
Calibre does it the current method to avoid the huge performance hit using a BLOB. |
ProgramData is different than Program Files. It's effectively the AppData directory for "All Users", so if calibre went that route it'd be better to use AppData instead of ProgramData (AppData is per user and lives in the user's profile).
However, default to Documents makes some amount of sense, as Documents is generally backed up (well, when a user does backups, anyway, which is unfortunately not as often as we should). Calibre content could be considered "documents", in the same way that Amazon puts books in Documents\My Kindle Content, Nook puts books in Documents\My Barnes & Noble eBooks, Adobe Digital Editions puts books in Documents\My Digital Editions, etc. Just as those other apps don't expect you to manipulate files, neither does calibre.
For the OP, I don't understand why you would need to link data into a calibre book directory. What's the end goal? Keep in mind that calibre is not a document editor, so if you're trying to build/write a document with embedded content via calibre you're "doing it wrong"
