Category:Bitweaver: Difference between revisions

|name                 = Bitweaver

|URL                   = http://www.bitweaver.org/wiki/index.php

|changes URL     = http://www.bitweaver.org/wiki/index.php?page=RecentChanges

|maintopic           = Wiki Engine

|status               = Dormant

|language             = English

|s/w license         = GNU Lesser General Public License

}}{{TOCright}}

*{{tag|Firebird}}

Due to the large number of databases it supports, it is considered {{tag|cross-platform}}.  In addition to ADOdb Bitweaver uses the well-established {{tag|Smarty}} template presentation framework, which allows Bitweaver to efficiently separate logic from presentation, making theming and site design logical and straight forward.  The targeted template overriding inherited from TikiWiki makes themeing much easier than traditional fixed [[:Category:HTML|HTML]] designs.  This makes it much easier to upgrade and work with the coding philosophy advocating pristine source.

Like many content management systems, Bitweaver originated as a {{tag|fork}} of another project, in this case, TikiWiki.  In late 2003, Christian Fowler began the process of integrating the open source {{tag|phpBB}} forum software.  While successful, this revealed a rift among the TikiWiki community - whether the project should remain as a tightly integrated "Swiss Army Knife" or become a more modular, and extensible application more suited to custom software development.  After a fierce, open debate [https://sourceforge.net/mailarchive/forum.php?thread_id=3752617&forum_id=12569 1], [https://sourceforge.net/mailarchive/forum.php?thread_id=3752607&forum_id=12569 2] on the SourceForge mailing lists, the founder of TikiWiki refused to permit the phpBB code changes in the main source-tree.

Being derived from the feature rich code base of its progenitor, [[:Category:TikiWiki|TikiWiki]], the primary challenges were to remove the lesser-used software features from [[TikiWiki]].  After completely modularising the code base, the main features (known as 'packages' in Bitweaver) were updated, and new capabilities were added.  During this process of modularising and code rewriting, the authors of Bitweaver decided to introduce a centralised content management package called [http://www.bitweaver.org/wikiLibertyPackage liberty].  This means that almost all content is stored in a common location, making new package development very easy, and providing a common standard across the entire platform.

This architectural design has made it is possible to work with a set of pristine files (e.g. downloaded and kept up to date using {{tag|CVS}}),^[clarify] and drop in custom packages to add any functionality required for a particular point installation.  In addition, unused packages can be removed simply by deleting the package directory from the server, thus making Bitweaver as compact or as comprehensive as desired.

As of August 2006, Bitweaver had 59 software developers who have permission to contribute to the project [https://sourceforge.net/project/memberlist.php?group_id=141358 1], and they have maintained a source code contribution pace of one commit every 80 minutes for over a year.[http://cia.navi.cx/stats/project/bitweaver 2]

*{{tag|blogs|blog}}

|+Bitweaver release history

|colspan=3 align=center|'''ReleaseAlpha

|—||2004-04-02||(as TikiPro) project naming, database prefixing

|colspan=3 align=center|'''ReleaseZero

|colspan=3 align=center|'''ReleaseOne[http://www.bitweaver.org/wiki/ReleaseOneChangelog]

|colspan=3 align=center|'''ReleaseTwo[http://www.bitweaver.org/wiki/The+Absolute+Beginners+Guide+2.0]

|colspan=3 align=center|'''ReleaseThree

*[http://www.Bitweaver.org Bitweaver site]