Port DTMM to new UI framework #80
Labels
No labels
ci
crate/dtmm
crate/dtmt
crate/sdk
crate/serde_sjson
kind
bug
kind
documentation
kind
enhancement
kind
feature
kind
question
kind
upstream
part/bundle
part/filetype
stage
actionable
stage
design
stage
proposal
status/duplicate
status/good first issue
status/help wanted
status/invalid
status
need-replicate
status/wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: bitsquid_dt/dtmt#80
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Apparently, Druid was marked as discontinued around the same time I started using it. But the with the notice being relatively easy to overlook in the README's entire wall of text, I am now on Druid anyways.
Either way, github.com/linebender/xilem is the new deal, but in very early stages, still.
Other options:
The native implementations are likely to provide more Rust-y ergonomics than the library bindings. But out of all the different libraries, the FLTK and GTK bindings seem to be used regularly enough that they would probably be fine to use.
Port to Xilemto Port DTMM to new UI frameworkXilem is still considered very experimental.
Iced seem to be getting popular, though their roadmap still puts them a few steps away from a v1.0.
Their "book" is only getting started, so it'd take a bit of digging to get started. But they do have a selection of examples.
I'll have to go through those and evaluate if all the things I need, especially the ones Druid doesn't have, are there: