I don't think any actual vBulletin code is necessary (unless you count function and class names, of course), and I do plan on starting some tutorials if no one wants to copy theirs over.
Quote:
Originally Posted by Analogpoint
EDIT: In your listings of files, include the hooks (and their line number) found in each file. You might also state what different "do" branches exist in the file. Also, a summary of what the file does would be good.
|
Good ideas, I hadn't even thought about the hooks.