-{maketoc}
|
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
|
+Bitweaver has a set of required packages needed to be fully operational. These are refered to as the "core". The core includes: |
*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 ((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 ((Themes Package|Themes Package)) manages the theming of your site |
+*The ((UsersPackage|Users Package)) manages user data |
+*The ((LanguagesPackage|Languages Package)) handles 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}
|
-
|
-!For Developers
|
-The Bitweaver Framework, consisting of Liberty and Kernel, offers you the above mentioned services. Here we'll try to show how you can make use of that.
|
-
|
-!!Business Objects a la Liberty
|
-!!Sorted Lists
|
-!!Detail Views
|
-!!Confirmation Dialogues
|
-!!Authorisation Required |