Merge all modules into one
mki - May 4, 2006 - 12:06
| Project: | Content Construction Kit (CCK) |
| Version: | 6.x-1.x-dev |
| Component: | General |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Description
Module for every type of field wiil reproduce too many modules. Is there a possibility of turn field-type-module to submodule?
#1
There is no need to have one module per field type. A single module can define as many field types as you want; for example, number.module defines both integer and decimal fields.
If you're asking about merging the existing modules, I have hesitations because then we're requiring users to have a lot of code loaded even if they never use, say, date fields. The separation will stay as it is for now, until/unless it is deemed this needs to change for a technical reason.
#2
There is no need to have one module per field type. A single module can define as many field types as you want; for example, number.module defines both integer and decimal fields.
If you're asking about merging the existing modules, I have hesitations because then we're requiring users to have a lot of code loaded even if they never use, say, date fields. The separation will stay as it is for now, until/unless it is deemed this needs to change for a technical reason.
#3
Thank's for your answer, you're right, but there is difficulty to enable/disable modules if every module has different name. Mayby names of modules shoud be prefixed, for example "cck_". Then in list of modules at first glance I will know what part of CCK is enabled.
#4
The conversation about the module page appearance is here:
http://drupal.org/node/49690
#5
I'm satisfied by this explanation.