anchor.diff:  ==== Html
   
   With html content you can break out from the constraints given by Minimal-J. A HtmlPage can display basically every URL or html
  -string. The frontends may depend on system funcionality for that. For example the SwingFrontend uses the JavaFX bridge to the system
  +string. The frontends may depend on system functionality for that. For example the SwingFrontend uses the JavaFX bridge to the system
   browser. And for the web based frontend displaying web content is the easiest part.
   
   Displaying html is meant to be used for start or help pages. Also report engines (not in scope for Minimal-J) could present their
  
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.
  