An open API service indexing awesome lists of open source software.

https://github.com/madeso/ride

Ride IDE
https://github.com/madeso/ride

Last synced: about 1 month ago
JSON representation

Ride IDE

Awesome Lists containing this project

README

        

![screenshot](data/logo/256text.png)

[![windows](https://github.com/madeso/ride/workflows/windows/badge.svg?branch=master)](https://github.com/madeso/ride/actions/workflows/windows.yml)
[![linux](https://github.com/madeso/ride/workflows/linux/badge.svg?branch=master)](https://github.com/madeso/ride/actions/workflows/linux.yml)
[![Project Stats](https://www.openhub.net/p/ride/widgets/project_thin_badge?format=gif&ref=Thin+badge)](https://www.openhub.net/p/ride)

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](http://www.rust-lang.org/) and [IDE](https://en.wikipedia.org/wiki/Integrated_development_environment), 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](http://rustdt.github.io/) for Eclipse, [SolidOak](https://github.com/oakes/SolidOak) or [Rust](https://github.com/rrandom/Brackets-Rust-IDE/) for [brackets](http://brackets.io/) is your thing.

# Code layout
![code layout of ride](data/ride.excalidraw.svg)

## 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.

| library | description |
|-----------|-------------------------------------------|
| assert | assert library |
| core | core library (not related to rendering) |
| api | API for creating applications |
| ride | ride logic |
| backends | actual backends like wxWidgets and OpenGL |