|
Sengian - thanks for that, I will take a look when I get a chance.
As for the source control, just to kill this subject off again as it has been discussed a couple of times before. In over two years of developing several dozen plugins the number of code contributions from the community can be counted on one hand. There is absolutely no justifiable need for the extra overhead in the monitoring and release process - you have the source code for the plugin within the plugin zip file etc being uncompiled python.
And no I dont buy the argument that putting them in Git will magically increase the number of contributions. Something like Git just adds another complication. The subset of calibre users who are technically inclined in Python and care enough to want to make a change to a plugin who also happen to be familiar with Git is so small it is ridiculous.
As I have said before it may happen one day, and when I one day stop maintaining these plugins completely then that may be as good a time as any. In the meantime attaching a zip like sengian did makes it easier for other users to try it out and test it before I find time to look, which isnt going to happen if instead people had to work out how to connect to git and produce their own deployable zip...
|