anchor.diff:  
   ==== Form
   
  -Forms in Minimal-J have basically the same funtion as in HTML.
  +Forms in Minimal-J have basically the same function as in HTML.
   You define with a Form what fields of an entity are shown and in which order.
   Fields can depend on each other. This could mean if a checkbox is selected some fields get editable.
   
  
positive.code: ===== FormElement
  
  FormElement objects represent the business side. Fields of an entity are 'bound' to a FormElement.
  Minimal-J doesn't emphasize much on binding.
  
  It's very important to note that a FormElement is _not_ a IComponent but _provides_ one. This
  is necessary as the specifc implementations of the components depend on the chosen Frontend.
  
  The framework provides the basic form elements like the ones for formatted strings, dates, numbers and enumerations. But
  for more complex types you will define your one FormElement classes. Look at the existing examples how to do this!
  
negative.code: ===== Inputs / Components
  
  Minimal-J doesn't try to have as many shiny components as possible. Where other frameworks are proud to present pages of predefined components
  Minimal-J restricts you basically to texts, comboboxes and checkboxes (with some variations).
  
  The Frontend class acts a factory for all components. This makes sense as for different frontends (web or rich client) different components have
  to be created.
  