Re: define Standard Templates for theme developers - your idea
Too bad XOOPS is a Monarchy
Depends who you ask...I would do it how evo does it:
In a theme I would define OpenTable, CloseTable functions and use that as a wrapper. For example, the OpenTable function would be the top and left of my block, the CloseTable function would be the right and bottom of my block.
Then any module dev could call those functions and throw their content in the middle and format it generically with .row1 .row2 .even .odd td,tr,hr,div...etc which i would have in my style.css because every module would use those same classes. And the theme would still look how i meant it to look in any module.
@marco theres my contribution
Benchmark our themes? Why not start where the trouble is... With the module devs. You devs are so insistent that we stay out of from under the hood, yet its ok for you to come out and run your keys down the side of our fresh paint job.
You all run around talking about contributions, and helping out the project... but when it comes down to it you are just blowing smoke up our asses....
Why is it that aphex was the only designer on the design team? Anyone? Yeah... its bull #OOPS#. Why is it that kris can run around peddling his work as the standard for XOOPS without actually consulting the design community about it.
Why is it that "First Official Theme Contest For XOOPS" is being highlighted... Someone had to approve the article which makes it official, yet all of a sudden no one wants to sit next to kris.
The whole system is stupid. You all sit over on sourceforge while the rest of us actually sit in the project site. This theme contest should have never been hidden like it was, and I dont want to hear for one second in some half ass attempt at english that it wasn't.
If this was ever about the #OOPS#ing community it would have been decided on by the community, not some piece of #OOPS# on a power trip.