Quote:
Originally Posted by haertig
My programming career (in order) went C, Unix sysadmin, C++, Perl, Linux sysadmin, networking, security. And a bit of Java, but not enough to really count. I now am 100% Linux, and still use Perl for any scripting needs I have these days. I never did anything serious in Python, although it has since overtaken Perl in popularity. While I'm still pretty much a Perl guru, I'm only a Python newbie. But since I only need ONE template, I could probably muddle my way through a Python implementation without too much fuss. I'll do some more reading on the various programming modes that Calibre offers.
|
Oh do I understand. I followed the same chain except that Pascal and C were intertwined while I was at Berkeley. I started with Python when I started working on calibre in 2010. My use of Android's version of Java started in 2012 when we started Calibre Companion. At this point my brain is so fuzzy I don't think I could do it again.
Suggestion: even though the GPM template language is a mixture of multiple languages (I made it up from lisp, Algol 68, and C), you might be better off starting there. GPM templates don't mess with calibre internal data and thus can't break much. Python templates can more-or-less do anything and can break everything, and they require more knowledge of the calibre database API. On the other hand, some things are really easier to express in Python, especially list (array) operations.
Feel free to
ask questions in this thread or by PM. I am happy to support people who want to know how this stuff really works.