Although I do understand the need for a fully realized presentation layer, notable flexibility is lost IMO. As examples I will mention the tapiar module, table_export, and other various modules that take advantage of the theming system as it sits in D5. There are certainly ways around this, perhaps the D6 version of table_export will collect table rows via JavaScript.
Another example may be the table drag API in D6, having to implement this at the tpl level is not only annoying/confusing for our designers, its annoying for me! Personally I have very very rarely had a need to override any themes ( not including small formatting changes or removal of usernames etc ), you can accomplish a lot with the right set of markup and a good chunk of CSS knowledge...
Anyways I just wanted to open up a discussion about this, no flamming please as I am not attempting to bash the new theming system it is just a concern.
As examples I will mention the tapiar module, table_export, and other various modules that take advantage of the theming system as it sits in D5.
It sounds like you are just complaining that these modules will need to be re-written for D6’s theme layer. The new theme system actually allows greater communication between modules and the theme layer since there are now Preprocess functions for modules: http://drupal.org/node/223430
Another example may be the table drag API in D6, having to implement this at the tpl level is not only annoying/confusing for our designers, its annoying for me!
I do not mind porting my modules to D6 at all, that is certainly not the issue. My main issue is that you can take advantage of data being passed through all of these theme functions, but now the majority will simply be static markup, which has its ups and downs dont get me wrong.
I don't know anything about...any of the modules you listed, so they aren't exactly effective examples to make your point.
I'm not even sure what your point is, to be honest.
The tabledrag stuff doesn't really take advantage of the new theming system, it's actually generally piggybacking on top of the old theme('table') stuff and adding to it.
But in general, I have no idea what you mean by 'flexibility is lost'.
Comments
Although I do understand the
Although I do understand the need for a fully realized presentation layer, notable flexibility is lost IMO. As examples I will mention the tapiar module, table_export, and other various modules that take advantage of the theming system as it sits in D5. There are certainly ways around this, perhaps the D6 version of table_export will collect table rows via JavaScript.
Another example may be the table drag API in D6, having to implement this at the tpl level is not only annoying/confusing for our designers, its annoying for me! Personally I have very very rarely had a need to override any themes ( not including small formatting changes or removal of usernames etc ), you can accomplish a lot with the right set of markup and a good chunk of CSS knowledge...
Anyways I just wanted to open up a discussion about this, no flamming please as I am not attempting to bash the new theming system it is just a concern.
vision media
350designs
Print Huge Edmonton Printing Services
Design Inspiration Gallery
Tj Holowaychuk
Vision Media - Victoria BC Web Design
Victoria British Columbia Web Design School
I don’t get it…
It sounds like you are just complaining that these modules will need to be re-written for D6’s theme layer. The new theme system actually allows greater communication between modules and the theme layer since there are now Preprocess functions for modules: http://drupal.org/node/223430
I couldn't find anything about a “table drag API” in Drupal. http://www.google.com/search?q=%22table+drag+api%22+drupal
So… do you have any better examples?
- John (JohnAlbin)
- John (JohnAlbin)
Table drag = tabledrag.js I
Table drag = tabledrag.js
I do not mind porting my modules to D6 at all, that is certainly not the issue. My main issue is that you can take advantage of data being passed through all of these theme functions, but now the majority will simply be static markup, which has its ups and downs dont get me wrong.
vision media
350designs
Print Huge Edmonton Printing Services
Design Inspiration Gallery
Tj Holowaychuk
Vision Media - Victoria BC Web Design
Victoria British Columbia Web Design School
I don't know anything
I don't know anything about...any of the modules you listed, so they aren't exactly effective examples to make your point.
I'm not even sure what your point is, to be honest.
The tabledrag stuff doesn't really take advantage of the new theming system, it's actually generally piggybacking on top of the old theme('table') stuff and adding to it.
But in general, I have no idea what you mean by 'flexibility is lost'.
I give up already, haha..
I give up already, haha.. wants delete button
vision media
350designs
Print Huge Edmonton Printing Services
Design Inspiration Gallery
Tj Holowaychuk
Vision Media - Victoria BC Web Design
Victoria British Columbia Web Design School