[issue #50] added debug main action so that jalopy won't be executed
[issue #50] basic model infrastructure for an equalizer component implementation
[issue #50] minor jalopy format
[issue #50] replaced JUnit with TestNG and removed autogenerated test which did nothing, added test for Range class
[issue #50] added abstract equalizer model implementation that handles event propagation to ease implementation of an actual models
[issue #50] jalopy deleted the throws policies of the single operations, thus the policies are added to the method description
[issue #50] default equalizer model implementation
[issue #50] minor jalopy format of unit tests
[issue #50] additional policy ensuring that the category collection is not empty
[issue #50] minor jdoc adaption and correction of equalizer category hashcode implementation to match the overall style
[issue #50] minor jalopy format
[issue #50] made checkValueWithinRange method public so that anybody can test if values are within the range of the model
[issue #50] specialised rubberband implementation of equalizer model
[issue #50] view implementation for an equalizer model
[issue #50] view could not be created from single category model because the spline panel needs at least to points that can be connected (obviously), thus the spline will now not attempt to render itself if there is less than two categories
[issue #50] added a repaint in equalizer model listener so that the spline (if painted) will be displayed correctly if there is a change that did not origin from the sliders
[issue #50] to string impl for range
[issue #50] proper impl for enabled toggle
[issue #50] Fix bug that causes Rubberband model to become invalid

The RubberBand model of the equalizer panel could become invalid under
certain conditions. A value of -1 could actually occur for a category if
the carryover is negative and the goodIndexes list contains indexes that
point to 0 values. This is the case if the initial delta is smaller than
the number of available indexes (the first and only valueDelta is 0).
The carry over distribution section now handles this case correctly.
[issue #50] added debug main action so that jalopy won't be executed