This branch contains the development of a "new ride" that maintain a small impact on the ui library. This is for a few reasons.

• Can customize the colors of the whole ui instead of what the os thinks a list should look like
• Can more easily switch to another ui library if the current one has issues

In the mean time I still think ride classic (classic branch) is useable but far from good or recomended for any serious rust development.

Ride is a general text editor like vs code, the name comes from concatenating R from Rust and IDE, but that has lost it's meaning, now it's just a name. It's currently not in a usable state. If you're looking for something more complete, perhaps RustDT for Eclipse, SolidOak or Rust for brackets is your thing.

Code layout

libraries

To support many "backends", each backend is generealized to a single API (virtual interface) with each backend implementing a specialization (derived class) and calling a app class. Each backend is launched via a macro and a cmake function and is selected upon config/build. This should hopefully allow the backend to to be seperated from the app but also use all features that the backend can provide.