[development] how to identify "root" modules?

Gábor Hojtsy gabor at hojtsy.hu
Fri Oct 12 16:42:27 UTC 2007

On 10/12/07, Cog Rusty <cog.rusty at gmail.com> wrote:
> I want to throw-in a related problem to be taken into account. It is
> about the "human readable names" of the modules. I am looking at the
> /admin/build/modules page of a "tryout" site, searching on the page
> for "image" and I find 3 different "Image" modules with their own
> dependencies.
> Ad group
> Image: Enhances the ad module to support banner ads.
> Depends on: Ad (disabled), Upload (enabled)
> CCK group:
> Image: Defines an image field type.
> Depends on: Content (enabled)
> Required by: CCK Slideshow (disabled)
> Image group:
> CCK slideshow: Depends on Image (enabled) -- ***notice the group***
> ...
> Image: Allows uploading, resizing and viewing of images.
> Required by: Acidfree (disabled), Flash Gallery (disabled), Image
> Attach (enabled), Image enhanced scaling (enabled), Image Gallery
> (enabled), Image Import (disabled), Image assist (enabled), Mailsave
> to image (disabled), Postcard (disabled), Upload image (disabled),
> Video Image (disabled)
> There are several modules which "Depend on Image". The only way to
> tell which one of the 3 is going to each "Image module" and reading
> its dependents.
> I would love to see the "human readable names" disappear.

??? Why not name the modules properly instead? From the list you have
above, I would say:

 - Banner image or ad image
 - Image field
 - Image


More information about the development mailing list