Thread: How to write a Metadata plugin
View Single Post
Old 11-25-2018, 08:38 PM   #5
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
You just need create the zip file and install it. The latter can be done from the Plugins page of the preferences. But, I use small script file to build, install and restart calibre when testing. They look like:


Code:
del "..\Annotations.zip"
"c:\Program Files\7-Zip\7z.exe" a "..\Annotations.zip" *.py developer_notes.txt dialogs\* help\* images\*.png plugin-import-name-annotations.txt readers\*.py -x!readers\_* README.md about.txt run.cmd translations/*.po translations/*.mo
mode 165,999
calibre-customize -a "..\Annotations.zip"
SET CALIBRE_DEVELOP_FROM=E:\Development\GitHub\calibre\src
calibre-debug  -s
calibre-debug  -g
That isn't for a metadata source plugin, but the overall concept is the same. The "SET" statement is for running from calibre source. You probably don't need to do this.

Once calibre is started, just test the metadata download and look at the log produced for errors. I tend to put a lot of logging statements in so that I can see what is happening.

You can test the identify method without the GUI, but, I don't usually do it that way.
davidfor is offline   Reply With Quote