[development] lucid menu & aggregation

Yves Chedemois yched.drupal at free.fr
Tue Mar 20 13:14:53 UTC 2007

Ashraf Amayreh a ecrit le 20/03/2007 09:43:
> Maybe you aught to submit an issue with your suggestions to the
> "closest" module? Many enhancements I made were based on such
> submissions.

I sometimes cross post features request to similar modules suggesting 
mainainers to merge their efforts.
And yes, that's my point, submitting patches / features requests to 
existing modules should be the first step before rolling your own module.

> I'd hate to say this, but some contributed modules are so badly
> written, so badly documented, that patching them up would be a living
> nightmare 

Quite true, obviously :-).

> Some had the logic thrown right into them in a pretty ugly way. I
> attempted to create a module that's extremely clean, extensible and
> efficient. So it's a software engineering standpoint that made it the
> right decision.

Now, _that_ is a good reason to consider forking or rolling a new 
module. The 'new and exclusive features' argument, whiich I was reacting 
to, is not, IMO. There are too many modules in contrib. Consolidation is 
not always possible or appropriate, but should be considered first.

More information about the development mailing list