Thread: Loading Plugin in development
View Single Post
Old 06-16-2014, 10:56 PM   #3
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
I use a command file to package the plugin and start calibre.

Code:
del "KoboUtilities.zip"
"c:\Program Files\7-Zip\7z.exe" a "KoboUtilities.zip" __init__.py about.txt action.py book.py common_utils.py container.py dialogs.py jobs.py config.py "KoboUtilities_Help.html" plugin-import-name-KoboUtilities.txt run.cmd images/* translations/*.po translations/*.mo
mode 165,999
calibre-debug -s
calibre-customize -a "KoboUtilities.zip"
SET CALIBRE_DEVELOP_FROM=D:\Development\GitHub\calibre\src
calibre-debug  -g
That:
  • Removes and rebuilds the zip file
  • Stops the current calibre session
  • Sets the command window size to maximum for my screen
  • Adds the plugin to calibre
  • Sets an environment variable to point to the calibre source
  • Starts calibre in debug mode

Setting the environment variable is only needed if you want to run calibre from source. For a plugin, you don't usually need to.
davidfor is offline   Reply With Quote