*[http://my.opera.com/community/forums/topic.dml?id=108345|Opera 9 beta]
|
*[http://my.opera.com/community/customize/setups/|Opera Tools for Web Dev]
|
*[http://nontroppo.org/wiki/webdevtoolbar|Another Opera tool bar] and [http://nontroppo.org/wiki/MooseCSS|more]
|
+*[http://edevil.wordpress.com/2005/11/14/javascript-libraries-roundup/|A good list of Javascript Libraries] |
+*[http://smarty.php.net/manual/en/api.register.function.php|Smarty Register Function Documentation] - easy steps for making custom functions that you can then call from your smarty templates. |
|
+ |
+!How to set up your own custom package |
----
|
+The easiest way to learn how to set up your own package is to start with the SamplePackage, which you can download or checkout from cvs. It has examples of most things described below. |
|
-!!How to set up your own custom package
|
-This is stuff I have learned about creating packages for bitweaver while creating this GMap Package.
|
|
-!!!Download the "Sample Package" from this site
|
-
|
-!!!Setting up your database tables
|
-Database (DB) Tables are defined in "schema_inc.php"
|
-This file goes in your __admin__ folder. Each package has one of these.
|
+!!Setting up your database tables |
+---- |
+Database (DB) Tables are defined in __schema_inc.php__ This file goes in your __admin__ folder. Each package has one of these. |
|
-Some conventions to follow when building these:
|
+!!!Some conventions to follow when building tables: |
*use single quotes on DB table scheme defaults
|
-*underscore between each word in table names
|
+*underscore between each word in table names, e.g. bit_gmaps |
|
-!!!Including tpl files in the page header
|
-The bitweaver Kernel is set up to automatically include header information from all packages. Any information you want included in the HTML HEAD you put in a file named "header_inc.tpl" which goes in your package's _templates_ folder.
|
+ |
+!!Setting up Smarty templates |
+---- |
+!!!Including tpl files in the html HEAD |
+The bitweaver Kernel is set up to automatically include header information from all packages. Any information you want included in the HTML HEAD you put in a file named __header_inc.tpl__ which goes in your package's __templates__ folder. |
|
To create conditional header includes simply nest tpl files in the header_inc.php file. You can do this by using the this include code:
|
|
-{CODE()}{ include file="bitpackage:yourpackagename/subheader.tpl"}
|
+{CODE}{ include file="bitpackage:yourpackagename/subheader.tpl"} |
{CODE}
|
|
-!!!Permissions
|
-* permissions can only be 30 characters long
|
|
-!!!Creating the dropdown and side panel menus
|
-Each package has teplate file that has its menus. You need to explicitly declair what you want in a menu in your own template file. For an example see the wiki package menu_wiki.tpl which you can find at:
|
-wiki/templates/menu_wiki.tpl
|
+!!Setting Up Package Permissions |
+---- |
+* Default permissions are set in your __schema_inc.php__ file |
+* Permissions can only be 30 characters long |
|
-!!!Preferences
|
+ |
+!!Creating Package Dropdown and SidePanel Menus |
+---- |
+Each package has template file for its menus. You need to explicitly declair what you want in a menu in your own template file. For an example see the wiki __package menu_wiki.tpl__ which you can find at: __/wiki/templates/menu_wiki.tpl__ |
+ |
+ |
+!!Creating Package Preferences |
+---- |
Preferences are automatically created the first time you submit a value for one. This means that a preference can be created for the first time by simply submiting one via a form on the admin_sample.tpl. For more advanced preferences examples look at admin_wiki.tpl or admin_articles.tpl.
|
|
If you want to set default 'y' values for your package preferences during install, you declare these in the __schema_inc.php__ file in __admin__. You do not need to set a preference for any that you would give a 'n' value to.
|