You could say there are two 'types' (Maybe 'kinds' is a better word because type sounds technical when used in the context of programming and this is not in any way a formal distinction) of addin interface routine:

1. Replacement type routines
2. All of the others

The key distinction is that you can have as many of the second type active at the same time, but only one of each of the replacement type routines.

Let's take a closer look at the replacement type routines and you'll understand why that is...

Read the rest of this post

If all addins include the same interface routines, how does ode.cgi keep things straight (i.e. avoid naming conflicts)? As you'll see once we start looking at some example subroutines, each addin must include a package statement declaring its namespace. By referencing these namespaces, Ode can target specific routines in specific addins with otherwise identical names.

Read the rest of this post

by getting to work documenting the addin interfaces (finally). I'm going to keep this fairly short and to the point (because I want to be able to finish). The idea is for me to come back periodically, adding to the descriptions, correcting small errors, etc. (Or maybe opening the documentation up as a wiki.)

Of course, if you have any questions, just ask *please*. Documentation is more of a process than a task to be completed. The process works a lot better with your involvement. By asking you can make sure that your questions get answered now, instead of eventually. That will help you and potentially many others as well. (People tend to have the same or similar questions.) So whether you want to help yourself, or be generous and help others, contributing to the documentation effort by asking questions is the way to go.

Ode's addin interface scheme is intentionally simple, as you'll see.

Read the rest of this post