Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up

Ride IDE

License

NotificationsYou must be signed in to change notification settings

madeso/ride

Repository files navigation

screenshot

windowslinuxProject Stats

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 fromRust andIDE, 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, perhapsRustDT for Eclipse,SolidOak orRust forbrackets is your thing.

Code layout

code layout of ride

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 allfeatures that the backend can provide.

librarydescription
assertassert library
corecore library (not related to rendering)
apiAPI for creating applications
rideride logic
backendsactual backends like wxWidgets and OpenGL

Releases

No releases published

Packages

No packages published

Languages


[8]ページ先頭

©2009-2025 Movatter.jp