Op maandag 22 januari 2007 11:58, schreef Stefan Nagtegaal:
Wouldn't it make more sense to make the default templates in core better as suggested before instead of "porting" another portion of drupal into some sort of contrib project?
Probably. But just like me, many people need a solution now. By having it as acontrib we can work 'in real life' on the template files, and improved XHTML. *I* prefer that over spending many hours in the core issue threads, only to have to wait another release cycle before I can actually use something that looks like what I had in mind in the first place. But more important: this theme is not just about making lots of tpl.php files: its abotu making them use *consistent* classes, IDS and consistent use of DIVs, ULs. Consitent nesting. In order to get that in core, you first need a Big Picture. For core, preferring small iterative patches, this means the only option is to make an theoretical Class ID and XHTML standard, from wich many small patches can be derived. But it can also be done by developing it 'in the real world'. By putting it to test when people build their CSS on top of it and so on. That said, nothing withholds anyone from making patches from (parts of) that theme. Once (if) more people use it, the Real Life will prove wether or not a choice was a good one: if it was, a patch for core is made very easily. Bèr -- Drupal, Ruby on Rails and Joomla! development: webschuur.com | Drupal hosting: www.sympal.nl