History of Bitweaver Framework
Version 1 | Current version | |
---|---|---|
NOTE: This is unofficial documentation. This page will try to consolidate framework relative information found on ((http://www.bitweaver.org/wiki/bitweaverArchitecture)), bitweaverOverview, and ((http://www.bitweaver.org/wiki/bitweaver)). If you are looking for official documentation, please see those pages. -Will | The Bitweaver application Framework offers a complete suite of core features in a higher modular design. The Bitweaver Framework is designed specifically for developer flexibility. To understand how Bitweaver is designed, you must understand that it is completely modular, on multiple levels. All parts of Bitweaver are encapsulated in what we call Packages. Bitweaver Packages are the largest grain of our modular architecture, they are intended to be large collections of features, such as the Wiki Package or the Blogs Package. Bitweaver has a set of required packages needed to be fully operational. These are refered to as the "core". The core includes:
The primary goal for bitweaver was to place the fewest possible requirements on a package and provide the most flexible environment possible. This diagram illustrates the functional inter-relationships of the core packages and optional features packages: |