Would you consider changing the module name to a more meaningful and shorter alternative? "Linodef" doesn't have a meaning and "Linodef - Link nodes & taxonomy terms and embed titles, field values & term names" is too long and confusing. I think something like "Internal link" would be more suitable for this module (see http://en.wikipedia.org/wiki/Internal_link).

Comments

Roi Danton’s picture

Roi Danton commented

I do agree in general but Linodef must stay as name because I can't change the folders name in CVS anymore. So something like

  • Linodef - Internal links & element embed
  • Linodef - Link & embed
  • Linodef - Insert elements & internal links

would be better.

drupaloSa’s picture

drupaloSa commented

I don't think there is an obligation for the module and directory/file names to be same. As far as i know, the module name is the one you define in the .info file. For example, the directory for the "Meta tags" module is named "nodewords" and the files are named as nodewords.info, nodewords.module, etc. So if you're not happy with the module name, then you should be able to change it.

And in regard to the alternatives you've provided; i think the third one is better.

Roi Danton’s picture

Roi Danton commented

@Naming: Thats correct but if the user downloads multiple modules it is helpful when the folders/archive name is mirrored somewhere in the modules name. I think I'll stick to

  • Insert elements & internal links (Linodef)

like CCK: Content Construction Kit (CCK).

Btw, the fantasy word Linodef means Linod == Link nodes, ef == embed fields. (I'm not the best in creating words :D )

Roi Danton’s picture

Roi Danton commented
Status: Active » Fixed

I've changed the name, thx to you for mentioning this! :)

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for two weeks with no activity.