History of bitweaverArchitecture

bitweaver is a web application that offers a complete suite of powerful feature sets in a higher modular design. To understand how bitweaver is designed, you must understand that it is completely modular, on multiple levels.

Our terminology:

• Package - the largest grain of our modular arcthitecture, it is a intended to be a large feature scope - such as the WikiPackage or BlogsPackage. The term Package was introduced as a concept in TikiWiki by Dennis Hetzel.
• Modules - we have maintained the "Modules" term to be identical to the TikiWiki usage. Modules are the "blocks" (in *nuke terms) of data that appear on the sides of the page - such as "Last changes" or "Last blog posts"
• Plugins - Packages can contain plugins inside them to enable modular functionality. The LibertyPackage and WikiPackage both have their own plugin architecture to handle different data.

These feature sets are known as a bitweaverPackage. The primary goal for bitweaver was to place the fewest possible requirements possible on a bitweaverPackage and provide the most flexible enviornment possible.

This diagram uses a powertool metaphor to illustrate the functional inter-relationships of our packages:



There is a KernelPackage that provides a core set of functionality that provide global services (such as preferences, user authentication, themes, permisions and such).

1. bitweaverArchitecture
   1. bitweaverPackage
      1. TemplatesPackage
      2. ClassStructure
   2. SamplePackage
   3. KernelPackage
      1. KernelFlowchart
      2. KernelInitialization
      3. Kernel_Storage
   4. LibertyPackage
      1. LibertyAttachments
      2. LibertyFormats
      3. LibertyContentPermissioning
   5. ThemeStructureIdea
      1. BitTabs
      2. IconThemes
      3. ThemeTutorial
      4. CssSchema
   6. SamplePackage
   7. UsersPackage

bitweaver is a web application that offers a complete suite of powerful feature sets in a higher modular design. To understand how bitweaver is designed, you must understand that it is completely modular, on multiple levels.

Our terminology:

• Package - the largest grain of our modular architecture, it is a intended to be a large feature scope - such as the WikiPackage or BlogsPackage. The term Package was introduced as a concept in TikiWiki by Dennis Hetzel.
• Modules - we have maintained the "Modules" term to be identical to the TikiWiki usage. Modules are the "blocks" (in *nuke terms) of data that appear on the sides of the page - such as "Last changes" or "Last blog posts"
• Plugins - Packages can contain plugins inside them to enable modular functionality. The LibertyPackage and WikiPackage both have their own plugin architecture to handle different data.

These feature sets are known as a bitweaverPackage. The primary goal for bitweaver was to place the fewest possible requirements possible on a bitweaverPackage and provide the most flexible environment possible.

This diagram uses a powertool metaphor to illustrate the functional inter-relationships of our packages:



There is a KernelPackage that provides a core set of functionality that provide global services (such as preferences, user authentication, themes, permission and such).