View Single Post
Old 02-14-2021, 06:21 PM   #8
pazos
cosiņeiro
pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.
 
Posts: 1,406
Karma: 2451781
Join Date: Apr 2014
Device: BQ Cervantes 4
Ah! You want to scan CC library? In that case a big NOPE. CC doesn't use metadata.calibre or deviceinfo.calibre. There's no way for KOReader (or any other program) to know that these books belong to a calibre library.

To be clear: that's the status on android for this plugin

Works from external sdcard
  1. Scan calibre libraries created with calibre (with folder driver, MTP or device drivers)

Works from internal sdcard and/or phone partition
  1. Scan calibre libraries created with calibre (with folder driver, MTP or device drivers)
  2. Send books and manage the library wirelessly from calibre.

Will never work
  1. Repurpose metadata from formats other than calibre's default json scheme

Quote:
Originally Posted by Incanus View Post
The thing is, with Calibre Companion I'm storing my /Calibre library on the SD Card without any problems.
Yes, apps can write documents on the sdcard using the Storage Access Framework. Sadly granting permissions to write on a specific directory won't give you access to the filesystem. And KOReader relies a lot on filesystem access. In fact it uses the same code in all the platforms it supports.

Writting glue code that emulates filesystem access on top of crappy google stuff is, IMHO, out of the scope of the program.

Of course if somebody comes with a sane patch we can merge it but I have the feeling that it is easier to write a new program from scratch for android using the same libraries that KOReader uses than proxy'ing the crappy storage framework to behave like a proper filesystem.
pazos is offline   Reply With Quote