Render history - Githubissues

mapsam commented 9 years ago

This PR does a few major things:

renders a visual history based on user responses, using the renderHistory() function in engine.js. This essentially redraws the history after every click using the state array
builds history in the .wand-history ordered list, and pushes all of the node renderings into .wand-node-container - preparing us for styling
starts building out some CSS because I can't stand looking at those un-styled buttons :stuck_out_tongue_winking_eye:

There are two new utility functions as well:

wand.util.getNodeObject(nodeId), which is essentially a node search, that returns the entire node object based on Id - currently used in the history renderings
wand.util.createElem(type, className, innerHTML) for simplifying the DOM element creation process - returns a DOM object

This is a pretty big PR, and @bsmithgall asked me to build off of api. Tests are currently not working, and I would be happy to split this into different PR's for the different features (especially since styles come along with this).

wand-visualhistory

mapsam commented 9 years ago

:sob:

bsmithgall commented 9 years ago

I TAKE BACK EVERYTHING I SAID

mapsam commented 9 years ago

YOU CAN'T TAKE IT BACK! NOT NOW!

dontgiveup

codeforamerica / wand

Render history #32