Module for every type of field wiil reproduce too many modules. Is there a possibility of turn field-type-module to submodule?

Comments

jonbob’s picture

jonbob commented
Status: Active » Closed (works as designed)

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.

jonbob’s picture

jonbob commented

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.

mki’s picture

mki commented

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.

jonbob’s picture

jonbob commented

The conversation about the module page appearance is here:
http://drupal.org/node/49690

mki’s picture

mki commented
Status: Closed (works as designed) » Closed (fixed)

I'm satisfied by this explanation.