Switch GUI framework to Druid #1
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This app is for reading books. Text, images. It does not require a low level set of accesses to texture buffers, and does not benefit from using an immediate mode GUI framework/API. The Piston/Conrod stack is far too low level for this project, and we reap none of the benefits.
Switching to Druid, which would allow for more focus on the core data and business logic, less on rendering code, would be greatly beneficial for productivity, and still ensure cross-platform compatibility.
Druid makes layouts easy enough, and is Rust-native, so avoids some of the annoyance of using the all-too-common FFI binding libraries for GUIs found in the Rust ecosystem. It has support for images, and its data driven approach makes implementing the state machine required for this app relatively trivial. Barring screen reader support, it is a natural fit for this application.