Look at the field definitions in the view logic: they contain a lot of information that is also in our model. Minimums, maximums, increments, and possible values are defined both here and in our model code. Even the type of the input widget is related directly to the type of data being stored. Ideally, this should only be defined one place, and that place should be the model. If we needed to update the model for some reason, our form would be out of sync.
What we need to do is to pass the field specification from our model into the view class and let the widgets' details be defined from that specification.
Since our widget instances are being defined inside the LabelInput class, we're going to enhance ...
