No description
4919e1ef57
- rewrote Item/Items - BaseType: fixed querey generation wizh null-values in extraOpts - ItemList: * reworked extendJsonStats() to use ?_itemstats istead of parsing on the fly * moved onUse-components used by xml from extendJsonStats() to separate function * the enhance-string passed with tooltips is now checked first - Loot: class is no longer static - Util::parseItemEnchantment() will now accept and return arrays and does only one single lookup - cuFlags are explained in the infobox, when available - JS: * do NOT strip iconStrings. It rightly can contain whitespaces >.< * removed a redundant $WH.ct in Conditions |
||
|---|---|---|
| cache/template | ||
| config | ||
| datasets | ||
| includes | ||
| localization | ||
| pages | ||
| setup | ||
| static | ||
| template | ||
| .gitignore | ||
| .htaccess | ||
| crossdomain.xml | ||
| index.php | ||
| README | ||
TrinityCore database World of Warcraft 3.3.5 (build 12340)
I myself take no credit for the clientside scripting, design and layout that these php-scripts cater to!
This project is not meant to be used for commercial puposes of any kind!
BASIC PREMISE:
1) The current implementation is a mess, at least in part being droped and picked up again by a dozen people over several years, without coordination.
- heap of functions
- files cross-including each other
- global variables in most functions, some even being written
- naming conventions...
- localization through Smarty AND per variable
- incomprehensible russian comments and page-texts
solution:
Me, being the next in line to pick this project up and create an even bigger mess! (hopefully not)
2) The idea of a _real_ live-database will not work:
- page build times for up to 30sec masked by caching are inacceptable
- some listviews require rediculous joins to get their required data
solution:
The database has to be designed specific to the needs of aowow. Possibly create tables with custom data to JOIN-ammend on world-tables (read: sub-sub-classes of items)
There should be a script to regenerate the tables depending on what data changes.
Idealy a setup-script would be present, or at least a sql-dump .. or at the very least a manual, where to get the data from.
3) Misc:
- remove template choices .. honestly who would use something else than the current Javascripts
- expand functionality: ItemComparison, filters, profiler, ect are completely missing
- some sort of documentation .. well ... at least to keep this in mind
THANKS:
mix: for providing the php-script to parse .blp and .dbc into usable images and tables; also the zones-pages his work
LordJZ: the wrapper-class for DBSimple; the basic idea for the user-class
kliver: basic implementation of screenshot uploads
SPECIAL THANKS:
Wowhead: For providing this beautifull website!
Please do not reagard this project as blatant rip-off, rather as "We do really like your presentation, but sadly you're no longer supplying the data we need".