Squishdot Classes, Methods and Variables : What's Available Zope Doc Project Butch Landingin butchland@yahoo.com 1 really-dry-stuff This article covers the classes, methods, and variables that Squishdot defines. While every effort will be made to make this consistent with the actual sourcecode, if in doubt, UTSL (use the source, luke!). %% There are actually five classes defined in the Squishdot product:
This is the main class of the product. It acts like a tree structure in two ways -- 1) as a regular Zope folder in which you can attach regular zope objects (e.g. dtml methods, folders, tiny tables, etc) and 2) as the root from which all postings (both articles and comments) descend from. In actuality, all postings are stored in a BTree persistent container variable named data. This object is shared by reference to all the descendants. The list of children are stored in the ids variable.
It also maintains a list of subject topics and topic image urls. In addition, it holds the two sets of indexes that are used during searches. One set of indexes contains all indexes that applicable for both articles and comments, while the other set of indexes contains only those indexes which apply to articles.
The more significant methods and services that the main class provides are :
The posting class is the ancestor class of the Article and the Comment. It represents the common functionality of these two classes. Just like SquishdotSite class, it holds the list of children it has in the ids variable.
Among the more significant methods that the posting provides are :
The difference between the article and the posting is that it has a summary text and dept field. Because of this, it has a slightly different method of being validated and edited.
The comment (i.e. reply) inherits mostly from the posting class and carries no extended functionality.
The squishfile encapsulates a file attachment. It does not provide much functionality other than its name, size, file type and contents. %%