My mac died this weekend, but now that I have finished with DrupalCamp Johannesburg, I will have some time to work on this again.<br><br>We can make a patch now, which we couldn't have done before modules had their own dirs.
<br><br><div><span class="gmail_quote">On 7/29/06, <b class="gmail_sendername">Khalid B</b> <<a href="mailto:kb@2bits.com">kb@2bits.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I think Adrian has proposed/is working on just that.<br><br>The only difference is that he wants each theme function in a file on<br>its own (to which I have a concern about performance).<br><br>Adrian, any updates on this?
<br><br>On 7/29/06, Frando (Franz Heinzmann) <<a href="mailto:frando@xcite-online.de">frando@xcite-online.de</a>> wrote:<br>> Now that we have modules in their own directories, I think we could move<br>> forward to ease pain for designers by stripping out theme functions out
<br>> of the .module file into a .theme file.<br>><br>> We already did the same for installation, and there's currently a patch<br>> in the queue to do the same for help files.<br>><br>> Why we should move theme_* functions into a <modulename>.theme file:
<br>><br>> * ease pain for designers. Currently, they have to look through all the<br>> module code, that is not interesting for them at all, to find a theme<br>> function they want to overwrite. By having them all together in a
<br>> <modulename>.theme file, it will save a lot of time and effort for them.<br>> And IMO we should take a bit more care of them, especially if it does<br>> not hurt at all.<br>><br>> * Seperation of code and design has always been a main target. So I
<br>> think it's only logical to stick to this policy here and move the V part<br>> of a module into a different file than the C part (according to the MVC<br>> pattern)<br>><br>> best regards,<br>> Frando
<br>><br></blockquote></div><br>