[development] Module Builder Module 1.0

Owen Barton drupal at grugnog.com
Wed Feb 22 12:29:36 UTC 2006

On Tue, 2006-02-21 at 08:26 -0500, Angie Byron wrote: 
> At DrupalCon, a few of us had talked about how handy it would be to have a
> module that automatically generated "scaffolding" for modules, both to help new
> developers as well as to speed up the process of creating custom modules for
> Drupal veterans.

Great work Angie!! The integration of DrupalDocs into this will
hopefully encourage contrib developers to really use/understand the
Drupal API - and also document their own modules!

Under 'Module root name:' the help text might want to add that for
modules that might get added to drupal.org it is good to reserve the
namespace at http://drupal.org/node/add/project_project (nothing worse
than writing a big module then finding the name is taken!). Also maybe
point out that modules can (I think) conflict with themes with the same

I'll try and hack out a 'module type' js/ajax autoselector when I find
some spare time :)

On Wed, 2006-02-22 at 10:42 +0100, Bèr Kessels wrote:
> However, my implmentations are not for "Joe Weblog", no. But without any 
> effort, you can use it very well, still. Since it is all aimed at being 
> tools. We, for example, have this tied into dischosting, a provisioning 
> system. OUr dischosting system calls all the commands and thus provides a 
> nice interface for all this. Far future plans are to turn dischosting slowly 
> into drupal modules. 

Ber: I have been thinking along the same lines. For these kinds of
toolkit modules/scripts (i.e. aimed at developers and/or site admins) it
would be great to work out a system where a tool (e.g. generating a
skeleton module) could easily share the same guts between a standard
drupal front end and a snappy sympal scripts command line front end.
Maybe this is possible already, but if you have any suggestions as to
how this could be wired together that would be great.

- Owen

More information about the development mailing list