refactor: Make the clafrica more modular

[pythonbrad]

Proposal

The service component will be responsible to handle the communication between the front-end, the OS, and the engine (processor, translator, ...). The communication will be through messages.

Structure

/
├── cli (the frontend is responsible of the binary application)
|       └── main.rs
|       └── lib.rs
├── keyboard (through enigo-rs and rdev)
├── service
|      └── src
|      |   ├── message.rs (responsible for the communication with the front-end and the keyboard)
|      |   └── lib.rs
|      └── Cargo.toml
├── config
|      └── src
|      |   └── lib.rs
|      └── Cargo.toml
└── engine
        ├── processor
        |      ├── src
        |      |   ├── message.rs (responsible for the communication with the service)
        |      |   └── lib.rs
        |      └── Cargo.toml
        └── translator
                ├── src
                |   ├── message.rs (responsible for the communication with the service)
                |   └── lib.rs
                └── Cargo.toml

Explanation:

• translator.transate , processor.process and processor.commit will return a set of instructions that the service should execute. Think about channel commiunication in the same thread.
• Except the OS and the frontend, i think that remaining are WASM compatible.

Change

• The service will be responsible for the interaction between the engine and the front-end / keyboard.
• Engine and Service are in the same thread.
• Service, Front-end and keyboard are in different thread.

Advantage

• The engine and the front-end can communicate through the service via sending / receiving of messages.
• The engine and the front-end will be independent.
• The front-end can be implemented through inter-process communication.

Further goal

• clafrica as a library (to target more platforms like the web Support for the WEB #51 )

[pythonbrad]

I forgot he clafrica-lib.
It will be still as a crate.

What will be the new name? 🤔

• buffer
• memory

[pythonbrad]

Suggestion

The cli will replace the clafrica crate.
The service will be replace the clafrica-lib.
Each crate will have his own changelog and readme.

[pythonbrad]

For more compatibility with non rust code, refer to it https://rustwasm.github.io/docs/book/reference/add-wasm-support-to-crate.html