History of Porting Drupal Modules to Bitweaver

^NOTICE: THIS DOCUMENTATION IS UNDER DEVELOPMENT AND SHOULD NOT BE RELIED ON. For official documentation please go to the Documentation section of this site.^

!!!Components Map
||~Drupal|Bitweaver
Modules|Packages
Node|LibertyContent
Users|Users
Comments|LibertyContent:Comments
Blocks|Modules
Actions| ?
||

!!!Services
Drupal is organized using functions with patterned names to create relationships between packages similar to bitweaver ((LibertyServices))

The [http://api.drupal.org/api/file/developer/hooks/core.php/6/source|Drupal core.php file] provides an overview of these service like functions.

!!!Core Hooks Map
The mapping of Drupal Hooks to Bitweaver features will not always be a perfect one to one. But following these relationships will provide a good guide where to move Drupal modules processes to in a Bitweaver package port.

||~Drupal|Bitweaver
hook_block()|modules/mod_<feature>.php
hook_boot() and hook_init()|bit_setup_inc.php
hook_comment()|Comment Services
hook_elements() dynamically generated form elements|tpls
hook_link()|service tpls
hook_menu()|templates/menu_<pkg>.tpl
hook_node_grants()|LibertyService::content_user_perms_function
hook_node_access_records()|Custom Content Permission Assignment
||