Quote:
Originally Posted by ShellShock
This is where the IOSRA plugin came unstuck. It worked by copying the Marvin database off the device to your Calibre device, so that the plugin could read the Marvin meta data from a local copy of the database. This meant it could keep Calibre's meta data in sync with Marvin, and it did not require any direct interfacing to Marvin.
The IOS security changes put a stop to this by hiding the location where Marvin stores its database, so the plugin can no longer read it. One solution would be for Marvin to store its meta data database in a location that is publically available. Assuming Marvin 3 uses the same database schema as Marvin 2, then this would only require minimal changes to the plugin. However, the schema may be totally different...I have no idea.
I got the impression that Kris was eventually going to provide a more robust API in M3 for third parties to use to connect to Marvin...but I have not seen anything about this for some time.
|
There are a lot of different ways to get the job done. I've learned over the years not to criticize the choices made unless I know the circumstances behind the choice.