FLUID-3078: move checkAll and uncheckAll functionality from builder.js to customBuild component

Description

Comments

• Laurel Williams commented 2009-08-07T09:55:58.000-0400

  Currently the checkall and uncheckall functionality is held in builder.js - a file which represents the code that the component user would create to add customBuild to a web page. This functionality is likely to be wanted, so move it into the component.

  After discussing this with JO and AC - we decided:
  1) to move checkAll and unCheckAll into the default selectors
  2) to add some setup code which checks the html code for existence of these selectors. If the selectors exist then click handlers are added to the html elements bearing these selectors so that when clicked the modules are all checked, or all unchecked.

• Laurel Williams commented 2009-08-07T10:40:59.000-0400

  Moved these elements over and refactored the code in response. Also required changes to the test code to accommodate the new functionality in the component. TODO still - add some tests for when the checkall and uncheckall buttons do not exist in the interface.

• Laurel Williams commented 2009-08-28T13:16:06.000-0400

  Actually, my last TODO doesn't make sense. If the checkall and uncheckall buttons do not exist, then the click handlers are not added. There is no way to test that this doesn't happen because there is no "error" state if this occurs. Other tests already in place to ensure that click handler is added appropriately and performs the expected task. So this task is completed.