[development] Strip out theme functions into a .theme file

Adrian Rossouw adrian at bryght.com
Mon Jul 31 08:40:32 UTC 2006

My mac died this weekend, but now that I have finished with DrupalCamp
Johannesburg, I will have some time to work on this again.

We can make a patch now, which we couldn't have done before modules had
their own dirs.

On 7/29/06, Khalid B <kb at 2bits.com> wrote:
> I think Adrian has proposed/is working on just that.
> The only difference is that he wants each theme function in a file on
> its  own (to which I have a concern about performance).
> Adrian, any updates on this?
> On 7/29/06, Frando (Franz Heinzmann) <frando at xcite-online.de> wrote:
> > Now that we have modules in their own directories, I think we could move
> > forward to ease pain for designers by stripping out theme functions out
> > of the .module file into a .theme file.
> >
> > We already did the same for installation, and there's currently a patch
> > in the queue to do the same for help files.
> >
> > Why we should move theme_* functions into a <modulename>.theme file:
> >
> > * ease pain for designers. Currently, they have to look through all the
> > module code, that is not interesting for them at all, to find a theme
> > function they want to overwrite. By having them all together in a
> > <modulename>.theme file, it will save a lot of time and effort for them.
> > And IMO we should take a bit more care of them, especially if it does
> > not hurt at all.
> >
> > * Seperation of code and design has always been a main target. So I
> > think it's only logical to stick to this policy here and move the V part
> > of a module into a different file than the C part (according to the MVC
> > pattern)
> >
> > best regards,
> > Frando
> >
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/development/attachments/20060731/98bf8c71/attachment.htm

More information about the development mailing list