![]() ![]() Adding tool tips to each item seemed easy enough, but, the content of those tooltips change depending on how many points are in the talent.This is important since without this condition talents would remain ‘active’ while the inferior conditions are no longer met.As new tiers are unlocked, previous talents cannot lose (decrement) points.Each maxed out talent will need a gold border (new class) to represent ‘full’.There are a number of things that occur as a talent is incremented such as adding points to the tree ‘points’ counter, and subtracting points from the overall ‘points total’ counter.The calculator’s points need to stem from the same total, but apply separately per each talent tree.I knew I would use Codepen to document the work and also help share it on Stackoverflow if I got stuck.īut as I worked through the logistics I came across a couple realizations: ![]() I knew I would use jQuery to build out the project. A planĪs I began reverse engineering the logic in the ClassicDB talent calculator, I realized this project was a bit more complicated than I first thought. It stacks on mobile and alots the correct amount of space for each talent. ![]() Then I took to Codepen to try and build out a basic three column CSSGrid. I spent a little time sketching out the possibilities, the logic, and the requirements in Adobe XD. I thought, this would be pretty cool to try and recreate in Javascript. One thing that I was intrigued by was the ClassicDB talent tool – Many classic fans are spending their time creatively awaiting this launch date, though some…not so much. World of Warcraft Classic is on the horizon, with a release date of August 26th in the states.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |