History of bitweaver and TikiWiki
{maketoc}
Bitweaver was a originally derived ([/forums/viewtopic.php?t=52|forked]) from an application called [http://TikiWiki.org/|))TikiWiki((]. However, after tens of thousands of code changes, the differences between bitweaver and ))TikiWiki(( are numerous to say the least.
! Key differences
;__Modularity:__ We have completely encapsulated all the ))TikiWiki(( features into their own self-contained feature, what we call a bitweaverPackage.
;__Speed:__ we are focused on high speed and high performance.
;__Packages:__ ))TikiWiki(( seems more focused on addon-like features. Bitweaver has chosen to deprecate many of the more obscure features of ))TikiWiki((. However, because bitweaver has completely modularized the ))TikiWiki(( feature set into ((bitweaverPackage|packages)), it is possible to bring any of the ))TikiWiki(( features into bitweaver. If you are interested, ((GetInvolved|get involved))!
! Relationship
))TikiWiki(( is a Content Management System (CMS) and portal application. Bitweaver started out as an experiment to modularise ))TikiWiki(( and allow admins to remove features they didn't need - not just disabling features but actual removal of the code. Bitweaver has broken ))TikiWiki(('s features into individual packages. This new modularity allows bitweaver to be an ideal Web Application Framework which is extremely customizable and ideal for integrating all kinds of other applications - proprietary or open-source.
Bitweaver supports many ((DatabaseComparison|databases)) on Linux, Macintosh and Windows. Bitweaver has added modularity, scalability (speed!), data integrity, and stability to the original ))TikiWiki(( engine. This makes bitweaver much more suitable for enterprise or large scale, high traffic websites. Its ease of use makes it ideal for small sites as well. Bitweaver will still have all the great features that made ))TikiWiki(( famous, but has made the integration of applications much easier.
! Compatibility
!! bitweaver ReleaseZero
Bitweaver ReleaseZero uses the identical schema as ))TikiWiki(( 1.8, and should be schema interoperable with a ))TikiWiki(( 1.8 install. ReleaseZero has all features of ))TikiWiki(( 1.8 working, and was an interim step between ))TikiWiki(('s all-in-one approach and bitweaver's modular framework. See ((bitweaverUpgrade|bitweaverUpgrade)) and ((bitweaverFAQ#HowdoiconvertmyexistingTikiWikiinstallto|How do I convert my existing TikiWiki install to bitweaver?))
!! bitweaver 1
Bitweaver ReleaseOne introduced massive improvements in many aspects of the original schema, and ground breaking advancements in the ((LibertyPackage|CMS engine)). This resulted in many schema changes, however we have created upgrade scripts that will eventually update the schema's of previous bitweaver and even ))TikiWiki(( releases. See ((bitweaverUpgrade|bitweaverUpgrade)) and ((bitweaverFAQ#HowdoiconvertmyexistingTikiWikiinstallto|How do I convert my existing TikiWiki install to bitweaver?))
!! bitweaver 2
See ((bitweaverUpgrade|bitweaverUpgrade)) and ((bitweaverFAQ#HowdoiconvertmyexistingTikiWikiinstallto|How do I convert my existing TikiWiki install to bitweaver?))
! Neglected features
From ReleaseOne forward, not all ))TikiWiki(( features may get updated for future releases. Support for features is dependent on the interest of the community. Being an application framework, bitweaver considers each feature as a small application inside of it - what we call ((bitweaverPackage|Packages)). Not all code is good code, and we don't want poorly written or neglected code to slow down the advancement of the most important features.
---
! Details:
{INCLUDE content_id=14413}
Bitweaver was a originally derived ([/forums/viewtopic.php?t=52|forked]) from an application called [http://TikiWiki.org/|))TikiWiki((]. However, after tens of thousands of code changes, the differences between bitweaver and ))TikiWiki(( are numerous to say the least.
! Key differences
;__Modularity:__ We have completely encapsulated all the ))TikiWiki(( features into their own self-contained feature, what we call a bitweaverPackage.
;__Speed:__ we are focused on high speed and high performance.
;__Packages:__ ))TikiWiki(( seems more focused on addon-like features. Bitweaver has chosen to deprecate many of the more obscure features of ))TikiWiki((. However, because bitweaver has completely modularized the ))TikiWiki(( feature set into ((bitweaverPackage|packages)), it is possible to bring any of the ))TikiWiki(( features into bitweaver. If you are interested, ((GetInvolved|get involved))!
! Relationship
))TikiWiki(( is a Content Management System (CMS) and portal application. Bitweaver started out as an experiment to modularise ))TikiWiki(( and allow admins to remove features they didn't need - not just disabling features but actual removal of the code. Bitweaver has broken ))TikiWiki(('s features into individual packages. This new modularity allows bitweaver to be an ideal Web Application Framework which is extremely customizable and ideal for integrating all kinds of other applications - proprietary or open-source.
Bitweaver supports many ((DatabaseComparison|databases)) on Linux, Macintosh and Windows. Bitweaver has added modularity, scalability (speed!), data integrity, and stability to the original ))TikiWiki(( engine. This makes bitweaver much more suitable for enterprise or large scale, high traffic websites. Its ease of use makes it ideal for small sites as well. Bitweaver will still have all the great features that made ))TikiWiki(( famous, but has made the integration of applications much easier.
! Compatibility
!! bitweaver ReleaseZero
Bitweaver ReleaseZero uses the identical schema as ))TikiWiki(( 1.8, and should be schema interoperable with a ))TikiWiki(( 1.8 install. ReleaseZero has all features of ))TikiWiki(( 1.8 working, and was an interim step between ))TikiWiki(('s all-in-one approach and bitweaver's modular framework. See ((bitweaverUpgrade|bitweaverUpgrade)) and ((bitweaverFAQ#HowdoiconvertmyexistingTikiWikiinstallto|How do I convert my existing TikiWiki install to bitweaver?))
!! bitweaver 1
Bitweaver ReleaseOne introduced massive improvements in many aspects of the original schema, and ground breaking advancements in the ((LibertyPackage|CMS engine)). This resulted in many schema changes, however we have created upgrade scripts that will eventually update the schema's of previous bitweaver and even ))TikiWiki(( releases. See ((bitweaverUpgrade|bitweaverUpgrade)) and ((bitweaverFAQ#HowdoiconvertmyexistingTikiWikiinstallto|How do I convert my existing TikiWiki install to bitweaver?))
!! bitweaver 2
See ((bitweaverUpgrade|bitweaverUpgrade)) and ((bitweaverFAQ#HowdoiconvertmyexistingTikiWikiinstallto|How do I convert my existing TikiWiki install to bitweaver?))
! Neglected features
From ReleaseOne forward, not all ))TikiWiki(( features may get updated for future releases. Support for features is dependent on the interest of the community. Being an application framework, bitweaver considers each feature as a small application inside of it - what we call ((bitweaverPackage|Packages)). Not all code is good code, and we don't want poorly written or neglected code to slow down the advancement of the most important features.
---
! Details:
{INCLUDE content_id=14413}