logo       

[task] Multi-file Modules Should Go in Subdirectories: msg#00929

php.drupal.devel

Subject: [task] Multi-file Modules Should Go in Subdirectories

Project: User experience
Version: <none>
Component: other
Category: tasks
Priority: normal
Assigned to: Anonymous
Reported by: jhriggs
Updated by: jhriggs
Status: active

Modules that use multiple files (.module, images, .inc files, etc.)
should be installed by placing all necessary files in a subdirectory
for the module, i.e. modules/mod_name/. Currently Project.module and
Textile.module do this, as do others, I am sure. Several, though, use
misc/ for images and the like. It seems to me that a module should be
self-contained (as much as possible), not affecting other parts of the
Drupal install. For example, the sample images that come with
Smileys.module should go not in misc/smileys, but rather in
modules/smileys/images or something similar.

Thoughts/questions/concerns (just brainstorming...please jump in):

* This will make installation much easier, but the fact that modules
can be installed in a subdirectory should be better documented. I have
had several users get confused with Textile.module.

* Should all modules be installed in a subdirectory (even if it is just
the single .module file) for consistency's sake and to avoid
confusion?

* When Adrian's installation API goes in, keeping all resources in one
location will likely be a must.

* If my proposed multisite changes that include site-specific themes
and modules (http://drupal.org/node/view/5942) go in, modules will need
a function to determine where they are installed so that they can
create correct paths to their resources, images, etc.

jhriggs

--
View: http://drupal.org/node/view/6019
Edit: http://drupal.org/project/comments/add/6019





<Prev in Thread] Current Thread [Next in Thread>
Google Custom Search

News | FAQ | advertise