@@ -3,7 +3,7 @@ |
|
!Package Architecture
|
^The design is simple: Put all files related to each feature into their own directory^
|
-__A bitweaver package is simply a directory in the bitweaver root directory.__ An optional requirement is a be bitweaver-centric initialization file called "bit_setup_inc.php" that will get included by the KernelPackage during initialization. A bitweaver package can be a set of highly integrated features such as the WikiPackage or BlogPackage or it could be an external app, like phpBB, adopted to use the bitweaver framework with minimal modifications to keep it VirginSource.
|
+__A bitweaver package is simply a directory in the bitweaver root directory.__ An optional requirement is a bitweaver-centric initialization file called "bit_setup_inc.php" that will get included by the KernelPackage during initialization. A bitweaver package can be a set of highly-integrated features such as the WikiPackage or BlogPackage or it could be an external app, like phpBB, adopted to use the bitweaver framework with minimal modifications to keep it VirginSource. |
|
The KernelPackage will automatically create __two standard 'define's__ for every package: <NAME>_PKG_PATH and <NAME>_PKG_URL, where <NAME> is simply your package name (aka, the name of the directory in the bitweaver root.) For example, FISHEYE_PKG_PATH and FISHEYE_PKG_URL will be created for the FisheyePackage. You can easily rename the package directory and you don't have to touch a line of code or setting anywhere. Yes, just move "fisheye" to "[/photos|photos]" or "phpbb" to "[/forums|forums]" and reload your browser.
|
|
|
|