History of Bitweaver Framework

^''__NOTE:__ This is unofficial documentation. This page is an attempt to improve on the framework information found on ((bitweaverArchitecture)). If you are looking for official documentation, please see that pages.''^

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. ((bitweaverPackage|Bitweaver Packages)) are the largest grain of our modular architecture, they are intended to be large collections of features, such as the ((WikiPackage|Wiki Package)) or the ((BlogsPackage|Blogs Package)).

Bitweaver has a set of required packages needed to be fully operational. These are refered to as the "core". The core inlcudes
*The ((KernelPackage|Kernel Package)) is responsible for the setting up the database and manages package configuration.
*the ((LibertyPackage|Liberty Package)) is a handful of well designed base classes that are intended to be inherited from. By extending the classes, you get all the power of liberty - access control, content history, formatting like wiki parsing, html scrubbing, and more - without having to write any of the code yourself.
*The ((ThemesPackage|Themes Package)) to get page rendering read
*The ((UsersPackage|Users Package)) to get an identified user object
*The ((LanguagesPackage|Languages Package)) to handle internationalization

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:

{attachment id=125}