1) some refactoring done to split gui generation from creation of the logic
2) preparing to use supervisor strategy (but nothing changed yet)
example created with two actors on same system-level
- one actor is watching the second
- checking termination status of the observed/watched actor in some reusing constalations
readme updated
tmp commit to save work
- restart actor with supervisor don´t work (don´t know how to use correct)
+ resuse actor path after got terminated message
  -> actor1 watches actor2
  -> actor2 get terminated
  -> actor1 got new message Terminated
  -> in onReceive().instanceOf(Terminated) actor1 can create a new actor at the path of actor2 in the system
  -> these new actor is only known to actor1 which created the new actor. If a third actor has watched actor2 too, he is still unknown that there is a new actor at the old path and gets still (actor2.isTerminated()=true) on request.
logging example added, based on akka documantation pdf
 -> chapter 4.3 Logging (Java) page 70.
+ rename package
+ add readme file
+ rename package
+ add readme file
example how a child can be killed / stoped
- the child actor is NOT automatic restarted, like written in akka documentation pdf chaper 4.1.12 Killing an Actor
example from akka 2.1.0 pdf documentation chapter 4.9.4 page 111
using a router