ericdrowell 0a8f0ddb74 got really tired of doing node.getParent().remove(node). To remove a node, you now just do node.remove(). ... I realize that this doesn't follow the JavaScript pattern of parent.remove(child), and that from an OO perspective, perhaps nodes shouldn't have the ability to destroy themselves. But, from a practical standpoint, it's a heck of a lot more convenient to just use .remove() when you want to remove something.		2012-09-26 12:50:08 -07:00
..
functionalTests.js	decided to split Circle and Ellipse shapes because it was causing too many issues related to the mixed data type of radius, which could be a number or object with x and y properties	2012-08-25 23:56:39 -07:00
manualTests.js	merged pull request #65 and updated manual tests. Also removed dragConstraint and dragBounds as they are now redundant. I may introduce a set of dragBounds helper functions, similar to filters, that provide common functions out of the box, such as Horizontal and Vertical	2012-09-25 21:23:35 -07:00
performanceTests.js	decided to split Circle and Ellipse shapes because it was causing too many issues related to the mixed data type of radius, which could be a number or object with x and y properties	2012-08-25 23:56:39 -07:00
Test.js	fixed new bug with stage toDataURL that was introduced with the new Canvas class, and added new filter unit tests	2012-07-21 13:29:22 -07:00
unitTests.js	got really tired of doing node.getParent().remove(node). To remove a node, you now just do node.remove().	2012-09-26 12:50:08 -07:00