Back-end/Front-end isolation

[Klaim]

The 'core' part of the code should be totally isolated from the 'view' part:

• it shouldn't have or rely on the dependencies of the 'view' (like Qt);
• it should be isolated enough to be used with another implementation of a view (a website or a OS-specific interface for example);
• communication between these parts should not rely on Qt;
• communication between these parts might be asynchronous;

One way to do this is to m,ake core and view as separate libraries. Then core should have some way to communicate with whatever system is used for visualization, but should act as a black box, relying on it's own thread-safe internal system. Core would expose a function to receive events, which should be used by the visualization system as frequently as possible to modify output according to changes quickly. All changes would go through requests (as functions) that should not be assumed to be synchronous.

This change a lot how the current code is orgniazed but should be benefic on the long term.

[Klaim]

Work on this is happening in this branch: https://github.com/artofsequence/aos-designer/tree/feature/back-front-ends-separation

I'll merge it with develop branch sometimes because it's a big architectural change.

[Klaim]

Work on this is now in the develop branch.

[Klaim]

The isolation is done but the code is not stable yet. Will close this issue once it is.

[Klaim]

The front-end is not stable yet but it's still isolated enough that I will close this issue.