Quote:
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.
Yeah exactly. Everyone is trying to workaround the problem rather than just fix it. "Hey guys lets all theme like kris!"...um, no thanks.
The problem that doesn't exist in other CMS's is the lack of a uniform module template. I've never used a CMS in my life where I actually had to modify just about all of the module's templates to get them to look right.
This topic is sitting on 2 basic points and I think a couple people are getting those points mixed up and are getting confused.
The first point being that kris wants everyone and their brother to use morpho and hes wanting to make that the standard template. That is unacceptable because that template contains a TON of useless bloated code. Isn't the point of a base template to be a SMALL framework to build around? Thats exactly the opposite of what morpho is.
The second point. Standardizing every class that a themer can use is retarded. First of all, the reason that you need something like this is so that all modules flow, correct? Standardizing every class isn't the answer though. Changing module code to use MINIMAL classes and allowing module devs to wrap ANY theme around their module with a generic function call IS an answer. I gave an example a few pages back, but since you missed that one, heres another.
le="color: #000000"><?php function OpenTable() { This is where I'm going to put my html code For the images/style of the top and the left side of my wrapper } function CloseTable() { This is where I'm going to put my html code For the images/style of the bottom and the right side of my wrapper } Now when a module dev is making his new module, he templates it thusly: OpenTable(); <---that will wrap the top and left part of my wrapper appropriately This is where the module developer is going to template his content Using .row1, .row2, .even, .odd, td, tr, hr, div, span, etc etc etc... Because my theme will have those defined in the style.css as they are CORE classes And will not negatively affect the way my theme works with the module. CloseTable(); <---that will wrap the bottom and right part of my wrapper appropriately
Marco lets get real here. I can contribute till I'm blue in the face. I and plenty of other people have contributed...rather, attempted to contribute information that would be beneficial to xoops. It ALWAYS comes down to some higher individual saying "No, you're wrong because we said so and we're going to continue to do everything our own way without considering what the community thinks and not bother even asking them because that's just how we roll. If you don't like it, leave, we don't care". So I figured if I bitch about what COULD make XOOPS better long enough someone will either do something about it or just ban me so they dont have to listen to it anymore, so I just hope for the best and see what happens.
@JeromeKervie
It's pretty funny when people don't have the balls to say something under their own account in fear of what someone might think of them. Grow up.
