Overview

The OpenACS API Browser is obviously the ultimate source of API documentation. But of course until there is a package for the API Browser to introspect, it can't deliver any documentation.

All we're trying to do here is to identify -- before we write them -- the most important, tricky, controversial, or ingenious procs and how we might organize them.

Also, broadly speaking, decisions must be made whether to put some functions in SQL or in Tcl. As far as I can tell, the Right Way To Do This is not entirely clear and we'll probably shift back and forth while we're actually implementing all this. Consequently we won't get too compulsive about exactly what the inputs and outputs are. Rather we'll focus mostly on what the various procs do and why.

Note that we're not focusing here on the APIs that create/delete things but rather the APIs that do things. See this thread about the former task; much of the code that does this in Assessment presumably will call into CR APIs.

Proc List