[sweede]

Originally Posted by tuaguild

if you use the provided class_bbcode.php and class_bbcode_alt.php it doesnt using those files fixes the editor problem with gitemstats and i prefer my code and the differance in speed is negligable plus i am more for guild sites that do not use a guild bank on the site plus yours has to use an outside js in order to show the tooltip mine is internal and if you require a large item cache it is much faster to use your own database for the files than to rely on wowhead every time it parses also i am working on an integration of wowroster from wowroster.net with vbulletin and that requires the original itemstats code

Nothing really requires the itemstats code. ItemStats was written because wowhead.com didnt exist. Intergration into any code base that said it needs ItemStats can be fixed by creating a function called ItemStats() that accepts a single input (the item string including the [item] bbcode) and returns a wowhead URL or whatever. (hey.. that gives me an idea )

WowRoster is obsoleted with the Warcraft Armory and gryphons gWowRoster product and it is almost always in best practices to use one, centralized source for data than copying it all over, even if it is a cache (how do you update the cache?)


Not trying to say no no no ! to you about what your trying to do, only that before you go and do it, save yourself the time and energy and see if these things already exist first so you don't repeat the work over and over.

Before i put together the wowhead item code product, i had written an entirely new ItemStats type product that worked with vBulletin used wowhead's XML files and everything. Then someone in the original gItemStats plugin posted a link to wowhead's powered.js information and i was like " whats the point? this single javascript file did the work of a dozen or so php functions and several hundred lines of code".

The only thing i need to do to my product now is to add wowheads new multilingual support