Introducing an event system in composition

[ixmanuel]

• Without:

  • a single private method;
  • parameters in methods (except for out.display(label));
  • Null;
  • public constants;
  • Getters/Setters;
  • Inheritance;
  • Traits or mixins;
  • Static methods;
  • MVC but an event model;
  • If-Then-Else but an event model;
  • DTO;
  • Singleton;
  • Annotations;
  • Class casting;
  • Utility classes.

• With:

  • Naming accordingly with the EO1 approach.
  • Unique objects;
  • Just composition;
  • Decorating envelopes;
  • Encapsulation;
  • Inmmutability;
  • Final classes;
  • Vertical descomposition;
  • Configurable by composition without coupling (except for IfBase and OnBase);
  • A modified printer;
  • Validating decorators;
  • An "ugly" view in hangman.Attempt, but you can see at a glance the architecture;
  • One primary constructors;
  • Code-free constructors. Thus, the code is declarative;
  • Contract-oriented programing;

• Without following:

  • Multiple returns (I don't understad why it is a code smell);
  • Compound names in vars, but very balanced.
  • Empty lines. I let empty lines between state, constructors and methods.

• Todo:

  • Removing new in methods.
  • Caching and improving the algorithms.
  • Write identified Tests in TestPlan.md