History of IntegrationTutorial
Version 5 | Current version | |
---|---|---|
Integrating applications into bitweaver involves two key parts:
This tutorial is focused on "loosely coupled" integrations where minimal modifications of the integrated application source are desired. Data Integration(Further information forthingcoming. Feel free to add it...) Visual Integrationphpinfo()this example will insert phpinfo() into the center column of bitweaver using the output buffereing method file: test/index.php
file: test/templates/info.tpl
PHPbbIntegration of non-smarty application such as PhpbbPackage or bitcommercePackage (an OSCommerce / Zencart fork) is achieved through the use of PHP's output buffering capabilities. This "cheap and dirty" trick enables the integrated package to stay virtually untouched, while displaying properly in the bitweaverArchitecture. The technique in psuedo-code looks like:
The display template needs to live in fooforum/templates/view_fooforum.tpl and is a *very* simple template:
You can get much more advanced and capturing modules and other interface elements from the integrated app. The best example is the bitcommercePackage and here is some source code that does module capturing. | Integrating applications into bitweaver involves two key parts:
This tutorial is focused on "loosely coupled" integrations where minimal modifications of the integrated application source are desired. Data Integration(Further information forthingcoming. Feel free to add it...) Visual Integrationphpinfo()this example will insert phpinfo() into the center column of bitweaver using the output buffereing method file: test/index.php
file: test/templates/info.tpl
phpBBIntegration of non-smarty application such as PhpbbPackage or bitcommercePackage (an OSCommerce / Zencart fork) is achieved through the use of PHP's output buffering capabilities. This "cheap and dirty" trick enables the integrated package to stay virtually untouched, while displaying properly in the bitweaverArchitecture. The technique in psuedo-code looks like:
The display template needs to live in fooforum/templates/view_fooforum.tpl and is a *very* simple template:
You can get much more advanced and capturing modules and other interface elements from the integrated app. The best example is the bitcommercePackage and here is some source code that does module capturing. |