Quote:
Originally Posted by BetterRed
My take is that the data, i.e the library, belongs to me, calibre is a tool I use to organise, manipulate and access that data… but not exclusively.
So, why would I copy the file path to that EPUB in my earlier post and not copy the calibre view-book link to the EPUB?
If I put the calibre view-book link into another application, then when I click on that link the calibre Viewer will open the EPUB, and the calibre library manager will start or switch to the Default library.
If I put the file path link into another application, then when I click on that link the calibre Viewer will open the EPUB… end of story. The calibre library manager would not be started, and if it was running it would NOT switch to the Default library.
BR
|
The content is yours. How it's organised is decided by the programmer.
Logically the files don't exist for the use on a path, it's only an implementation detail that they do exist that way.
I'd only use the viewer via Calibre. I don't have any ebooks not imported (but the originals are still in the original locations) and thus I only use the ebook viewer via calibre. Calibre is the easiest way to find an ebook on the computer. Just like the native Kobo or Kindle or Sony PRS is library, (not KOReader and filebrowsing) is easiest on an eink Ereader.
I do have kinds of things I don't add to Calibre, and then indeed I have hierarchical human readible schemes and use a filebrowser.
There is thus IMO, no need to know the path of an ebook added to Calibre. Defeats the reason for having a library interface.
A bunch of files isn't a library. A library is content only accessed by metadata, not filepath.