[themes] Re: [development] someone make a theme out of these templates

[Adrian Simmons]

Bèr Kessels wrote:
> 2) they are highly inter-related. If you change something in file A you need 
> to do so in B C and D. with CVS, or without CVS a hel to maintain, let alone 
> to understand, when learning an existing module.
You're losing me here. If you updated the module you'd need to update the 
module.tpl.php, and maybe the module.css. You've gone from two files to 
three - all of which (if I understand Adrian's proposal correctly) are 
sitting in modules/modulename/ anyway? Going from two to three files per 
module doesn't seem all that much harder.

You're right, that from the module builders end this would make things more 
complicated and create some extra work. But from the theme-builders end 
things would get easier.


> 3) All HTML that lives in modules is wrong there anyway. We need more HTML 
> generation API's, true. But already we can assume that ANY HTML tag in ANY 
> module is in fact a minor bug.
But isn't that part of what Adrian is proposing, the separation of xhtml 
from the module logic?
And yes API's are obviously useful for common elements, but they'll never 
replace all xhtml, and some modules will always need custom xhtml.


> I would rather call for a frenzy to actually remove ALL the HTML from any 
> (contrib) module.
Think of this as a step in that direction :)
Drupal moves in drips, not big splashes, you know that.

-- 
Adrian Simmons (aka adrinux) <http://adrinux.perlucida.com>
e-mail <mailto:adrinux at perlucida.com>