The Arcive of Official vBulletin Modifications Site.It is not a VB3 engine, just a parsed copy! |
|
|
#1
|
|||
|
|||
To enforce a valid coding style in the community!
I have noticed that most of the coders @ vBulletin.org do not follow vBulletin coding standards and / or make a code unnecessarily long with extra queries and other unnecessary stuff like creating code / variables that are already present on a certain vBulletin page... There are only about 4 or 5 coders who follow those standards..
While most of the hacks themselves are great, these coding faults pose security and stability errors, making server load higher than it could be if the code would be optimized. Plus, poorly written code might take more space than an optimized version of the same code. What I suggest is making a system where we would help people perfect their hacks after which it would be marke as PHP Valid. It should be no problem for the forum administrators to add a field "QA Verified", editable only by the QA team and the administrators. Once the field is created, allow users to choose from displaying all hacks or only the ones marked as "Containing an optimized PHP". This way, while the coding style will not be enforced, vB hackers will be encouraged to code properly in order to rate higher and display their hacks better. The best part is, this system is easy to implement (I could help making it), and it would not require immediate validation, which is a plus from the QA team's point of view. What do ya'll think? If this works out, I could help creating that system and later be a member of the verification team. |
|
|
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
More Information | |
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|