[development] Move all core modules into their own directories.

James Gilliland neclimdul at gmail.com
Sat May 6 17:43:44 UTC 2006

On the theming subject could there be some middle ground here.  First we
have a default theme file for the module you can through all your one line
theme functions in here.  Then we allow for individual files that can
provide seperation for more complicated and elaborate themeing.  There might
be a name spacing issue but there might be some way we could allow the
individual files to overide the default functions which would allow some
flexibility for people themeing functions and keeping up to date with bug
fixes etc.

Just my 2 cents.

On 5/6/06, Adrian Rossouw <adrian at bryght.com> wrote:
> On 06 May 2006, at 5:31 AM, Khalid B wrote:
> > Count me in with Morbus, Earl, et al camp who are  concerned by the
> > number of files that will have to  be included. A site with 15
> > extra modules
> > each with 3 theme_function will have 45 more files to include. If
> > we have
> > just one file per module, then it is only 15. A world of  difference.
> One theme file per module has exactly NO benefits to designers over
> having them in the .module to begin with.
> If we find that having them in individual files is too slow (which I
> don't believe will be the case, but is something
> we have to benchmark, not go either way on just because of a gut
> feeling!) we can develop a caching layer
> to handle this.
> --
> Adrian Rossouw
> Drupal developer and Bryght Guy
> http://drupal.org | http://bryght.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/development/attachments/20060506/aaee9ee4/attachment.htm

More information about the development mailing list