Log in

No account? Create an account

More on Moneydance Extensions

« previous entry | next entry »
Apr. 23rd, 2007 | 12:00 am
mood: optimisticoptimistic

One of the ten Moneydance extensions currently available is called the "Python Scripting Interface".  I don't know Python, so I haven't downloaded that extension.  I more-or-less assume, though, that if you install it, you then have access, from Python code, to the full Moneydance API: can then do anything from a Python script that you could do directly from a full-fledged extension, written in Java.

And, I'd further assume, you could do it with less effort than would be involved in writing an extension: some of the overhead, setting up your access to Moneydance data, would already have been done for you.  Thus, I'd expect that if you wanted to automate some Moneydance chore for your own use, and weren't thinking of distributing the code you create to others, then it would be easier to do it in Python than in Java.

Provided, of course, that you knew Python.  As I mentioned, I don't ... and it really doesn't have a place on any list of languages I want to learn, either.  (Before a horde of Python fanatics descends upon me, let me hasten to add that I really have nothing against Python; it's just that there are various other languages which, for one reason or another, excite me more ... enough of them for one lifetime, I think.  I don't claim that this preference is anything but arbitrary, OK?)

If you have some other scripting language that you'd like to be able to use with Moneydance (at least, if it's a scripting language that's been implemented in Java), you can write your own "scripting interface" in the form of a new extension, and grant your own wish.  (Uh, that's provided that you also know some Java, of course.)

As a matter of fact, that's exactly what I have in mind: to write a Moneydance "scripting interface" for one of the Java implementations of Scheme ... of which, you may or may not be surprised to know, there are at least three.

Link | Leave a comment |

Comments {0}