Task Observer Pattern

This is a type of Observer pattern that I may or may not have come up with. Regardless, this tutorial is built of rules rather than how-to:

Rules:
1. There is a global operation thread for every task. That means , even a non-looping task, should be wrapped, as threads still run even if it only has one line of code that doesn't loop in it. It doesn't loop the code, but when you tell it to run, it will run alongside the rest of the program concurrently.

2. Your program should be run entirely by Listeners (e.g. press a key, click a button), automated background tasks exempt (e.g. loading objects, animations, timers, debuggers, menu animations, etc)

3. The only reason you should have a loop at all in your program is for updating the state of your objects, not schedulers as traditional, inefficient games do.


Here is the reason why this works and why it is more efficient than a scheduler:
Using a scheduler, it depends on the order of execution.

 Thread main = new Thread(){
  @Override
  public void run() {
      while(true) {
        input();
        update();
        states();
        repaint();
      }
  }
 }

Using this method, you repaint when it isn't necessary, you check for things when unnecessary, and you update sometimes even thousands of objects depending on your hertz, causing major overhead for no reason at all. If nothing happens at all, your overhead should be close to absolute zero, not updating the screen when you aren't moving or a moving object is not visible. In contrast, this is easier to manage as everything is usually in one place unless you are some beginner or novice, an amateur just messing with code.

On the contrary, Task Observer Pattern is more efficient than a scheduler as you cause a lot less overhead due to the great lack of loops (except for updating positions when necessary, like press down, a loop updates every object in an ObjectTree). It can, at times be harder to manage as you have code in many different objects and places, though everything still goes to  one place: your Listeners.

Must I tell you?

DOCUMENT YOUR CODE!!!