Jelsoft/Vbulletin is XHTLM 1.0 transitional W3C compliant and so it would make sense that any code/hack added to it should also be XHTLM 1.0 transitional W3C compliant.
Now, why CAN'T we as a community have an oversight group of advanced coders to see that the rest live up to that standard prior to posting a code?
As somone else pointed out, an open source community does it and does it well...validates each one of their hacks prior to release. They have a minimum that the hackers have to code to and if that isn't met the hack isn't passed, plain and simple. And if you know going into the process, why should it be a problem?
It's kind of like getting your DL...if you know going into the test that this is the minimum standard, and you fail to meet it, than why should it bother you to not pass? Put out a list of the minimum standard for a code for a Jelsoft hack and then put together a team of volunteers and see what happens. Just because it failed the first time doesn't mean it will fail now...MAKE IT WORK. All it takes is people who want it to work but if you are convinced it won't, then it won't.
It would also be helpful if the hacks that were updated were indicated that way...I've noticed that some listed as beta 1 are 5 pages deep and are now working on RC1.
As for quoting entire posts...that is considered rude by netiquette standards. One should only use the part of the posts that is needed to the conversation at hand.
Liz
|