Feature/now 288

Implements the price configuration of a wants widget
I find it odd that the priceMin, priceMax, and usePrice fields are tied to the product. Granted we don't persist the product at this point but the fields are only applicable and I feel they should be kept separate and only within the widget code to avoid confusion