[drupal-devel] module and theme names

Adrian Rossouw adrian at bryght.com
Tue Nov 8 19:05:07 UTC 2005

Hash: SHA1

On 08 Nov 2005, at 8:01 PM, Chris Johnson wrote:

> Adrian Rossouw wrote:
>> Which is why i would prefer if we did away with  
>> themename_something  and just moved to template_something, and  
>> possibly even
>> engine_something.
>> All themes (.theme files even) would become inherently copy-able.  
>> The  only thing we lose is not being able to load more
>> than one at a time. I think we can do this, but we need to  
>> introduce  meta-data first.
> If I understand the above correctly, using template_something or  
> engine_something would prevent a site from having more than one  
> theme enabled.  Is that correct?  I'm not really sure I've got it  
> right.
No, it would stop you from having more than one theme loaded at the  
same time, which is different to having more than one theme enabled.

Ie: you don't have the templates / theme functions for both your  
admin theme and your normal theme loaded all the time, you only load  
the one you are using.

The only time multiple themes are actually being loaded, is because  
of the _features hook and the _regions hook, which i think should  
both be handled by external config files.

- --
Adrian Rossouw
Drupal developer and Bryght Guy
http://drupal.org | http://bryght.com

Version: GnuPG v1.2.4 (Darwin)


More information about the development mailing list