History of Bitweaver Framework
Version 21 | Current version | |
---|---|---|
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 inlcudes
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: For DevelopersThe 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 LibertyUp to now, the answer is to look at the SamplePackage and guess.Sorted ListsUp to now, the answer is to look at the SamplePackage and guess.Detail ViewsUp to now, the answer is to look at the SamplePackage and guess.Feedback and ConfirmationUp to now, the answer is to look at the SamplePackage and guess.gBitSystem->setBrowserTitle() gBitSystem->confirmDialog() Authorisation RequiredUp to now, the answer is to look at the SamplePackage and guess.Menus and ModulesUp to now, the answer is to look at the SamplePackage and guess.Installation and MigrationUp to now, the answer is to look at the SamplePackage and guess.Services | 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: |