Skip to content

Latest commit

 

History

History
21 lines (14 loc) · 1.55 KB

UI_Framework_Decision.md

File metadata and controls

21 lines (14 loc) · 1.55 KB

Design Decision for UI Framework

After digging around, I've decided that Rust will be a better fit than Kotlin, purely because the UI libraries for Kotlin are mostly lackluster (Jetbrains Compose looks promising, but it's not mature enough yet for me to commit to using it).

The JVM in general is a bad idea for a mod manager that will need to be running in the background in order to listen for DSR exiting in order to restore the vanilla files.

Besides, I doubt people will be willing to adopt a mod manager that runs on the JVM.

Outcome + Rationale

I've decided on FLTK-RS

  • it's currently in active development
  • is explicitly cross-platform
  • is lightweight (both in terms of performance and executable size)
  • appears to be very stable (this is based on the fact that there are very few open issues, many closed issues, and the major version number isn't 0).

Ok, so FLTK-RS achieves most of the functionality by using macros.

This is all well and good, but when neither VSCode nor Intellij IDEA can provide completions for Window::default()...

I'm going to have to start from scratch, because I can't go developing like this...

I'm going to give Tauri a try, because it lets me leverage web technologies without bundling an entire browser a-la electron.