History of bitweaver and TikiWiki
Version 5
bitweaver was a originally derived (forked) from the PHP Wiki application called TikiWiki. However, after more than 8000 code changes, the differences between bitweaver and TikiWiki are numerous to say the least. Here are some important differences:
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. This makes the codebase customisable, performance tuned, and ideal as a Tiki Web Application Framework.
TikiWiki is a Content Management System (CMS) and portal application. bitweaver has taken all of the TikiWiki features and broken each into indvidual features. 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 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.
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.
bitweaver ReleaseOne introduced massive improvements in many aspects of the original schema, and ground breaking advancements in the 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. The upgrade
The larger question is what about neglected features of TikiWiki that are little used? 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 "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. What this means is that from ReleaseOne forward, not all TikiWiki features may get updated for future releases.
What are the key differences between TikiWiki and bitweaver?
- Modularity
- We have completely encapsulated all the TikiWiki features into a there own self-contained feature, what we call a bitweaverPackage
- Speed
- we are highly focused on speed and high performance.
- Features
- TikiWiki is more focused on bells and whistles. This means bitweaver has chosen to deprecate many of the obscure features of TikiWiki. Because we have completely modularized the TikiWiki feature set, it is possible to bring any of the TikiWiki features into bitweaver at any time. If you are interested, GetInvolved with bitweaver!
What is the relationship between TikiWiki and bitweaver?
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. This makes the codebase customisable, performance tuned, and ideal as a Tiki Web Application Framework.
TikiWiki is a Content Management System (CMS) and portal application. bitweaver has taken all of the TikiWiki features and broken each into indvidual features. 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 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.
Is it compatible?
Yes, you can upgrade.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.
bitweaver ReleaseOne introduced massive improvements in many aspects of the original schema, and ground breaking advancements in the 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. The upgrade
The larger question is what about neglected features of TikiWiki that are little used? 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 "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. What this means is that from ReleaseOne forward, not all TikiWiki features may get updated for future releases.