Users' Guide (Draft)
1. Introduction
This page explains how to use the Count From Zero (CFZ) website. CFZ provides a community for software engineers and the publishers of their tools. The primary feature is the directory of programming libraries and APIs. See the about page for more details. Check out the advertiser and publisher pages for information about CFZ's objectives. For communications email cfz@countfromzero.biz.
CFZ provides two primary types of content pages: packages and categories. Package pages contain all the data CFZ publishes for a particular software package, while the category pages list packages and subcategories within the category.
Notes about the package pages:
- The release date refers to the date of the latest release, not of the first release.
- Currently CFZ caters to Java. CFZ contains some packages for other languages, but not many.
- CFZ identifies ten types of software licenses. CFZ does not support multi-licensing yet, so only one license will be noted. See section 2 for more details on licenses.
- CFZ records five types of relationships between packages. These relationships are identified in section 3. The relationship section only displays if applicable.
Notes about the category pages:
- The columns containing "H" and "D" are links to the homepage and download page respectively.
- If a category contains subcategories then a subcategory section and a tree view section will be visible. The subcategory section lists the immediate subcategories while the tree view section provides information about all subcategories down to the leaves. Tree views are explained in section 4.
2. License Types
Listings for shareware always use the license status applicable after purchase.
license terminology
- commercial released by an organization rather than an individual. Paid support usually available.
- cost only available for a fee. Assumes registration and commercial support.
- open source source code available. Does not imply rights to redistribute or modify.
- registration disclosure of personal information required before use.
licenses
- closed source freely available without source code or commercial support.
- commercial freely available without source code and with commercial support.
- commercial, open source freely available with source code and commercial support.
- commercial, open source, registration freely available with source code and commercial support and requires registration.
- commercial, registration freely available without source code, with commercial support, and requires registration.
- cost available at a price without source code.
- cost, open source available at a price with source code (very rare).
- open source freely available with source code.
- open source, registration freely available with source code and requires registration.
- registration freely available without source code and requires registration.
3. Package Relationships
A package relationship always consists of two packages, a parent and a child. The parent identifier is listed first.
- required by/requires child has compile or run-time dependencies on parent but is otherwise unrelated.
- extended by/extends child adds functionality to parent and cannot operate without parent.
- forked by/forks child started a new version of the parent and the parent is still maintained.
- succeeded by/succeeds child started a new version of the parent and the parent is not maintained.
- compatibility/compatible with child provides an interface to operate with parent but can function independently.
4. Tree Views
- packages/alphabetical alphabetical list of packages.
- packages/categorical list of subcategories and the packages containing them. Not yet implemented.
- categories/alphabetical alphabetical list of categories with statistics.
- categories/categorical view of the entire subtree structure for the category with statistics.