D7 support
joachim - November 15, 2009 - 15:51
| Project: | Module Builder |
| Version: | HEAD |
| Component: | Code |
| Category: | task |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
D7 support starts here.
| Project: | Module Builder |
| Version: | HEAD |
| Component: | Code |
| Category: | task |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
D7 support starts here.
#1
My plan for D7 is in two phases.
Phase 1 fits in the more general plan to make this module's drush aspect run on several versions at once.
This is happening on the 6--2 branch. This should eventually, when run under drush, generate module code for an installation of Drupal 5, 6, or 7.
Phase 2 will be the D7 UI, and a proper 7--2 branch of the module to run as a regular D7 module.
#2
Main problem to solve in phase 1:
How to get hook information from the new D7 api files.
Initially these seem great -- no more hook data to download, hurrah!
But they hold no information about where their hooks are to go.
Eg, system.api.php lists both hook_boot and hook_install, which go in the module file and the install file respectively, but gives no indication of this. (#633332: hook API documentation files have no information about where hooks are to go)