The activity library is in process of being converted to draw even more of its support from underlying types and classes contained in defobj and collections. Until this change is completed some details of the interface of the interface may change. Documentation currently focuses on basic, inherent function that is likely to remain stable.
In some cases, the interface reference sections include only a subset of the messages contained in the current activity.h header file. These messages include all those which are currently implemented and fundamental to the current supported use of the library. Other messages will be documented after their underlying implementation is finalized.
The collections library follows the documentation structure suggested by the module definition conventions of the defobj library. There are placeholders at least for each section of documentation (some of which merely indicate that the section is not available yet) so that all links should at least link up with something, whether or not there's anything there.
Throughout the documentation, a parenthesized comment that starts with (.. indicates a statement on the current status of implementation or documentation.
The documentation priority for all libraries is to complete at least their interface reference documents, so that there is the equivalent of Unix "man pages" that summarize all basic capability. A second priority is to complete the complementary "Usage Guide" documents. Unlike the reference documents, the Usage Guide will have a task-oriented organization, and will lead the initial user through actual code examples in the rough order a typical user is likely to need them. It will serve the role of a tutorial on each library.
The Usage Guide code examples have not yet been developed. For the time being, a directory of test programs (GridTurtle test programs, contained within the documentation release directory) provides code examples of many of the basic features of the defobj, collections, and activity libraries. These code examples also help indicate the portions of the libraries which are fully implemented and working, since they are run on each new release of these libraries.