You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now we have a derive crate (for Prism), we could include the widget generator for enums in druid-enum. This would make it more discoverable, as there isn't really a solution for displaying enums in druid or druid-widget-nursery at present (is this claim correct?).
The text was updated successfully, but these errors were encountered:
I haven't looked at druid-enum as much as prism, but they seem pretty overlapping to me in their functionality both displaying enums.
And while i've done a bunch of things with prism, like using the List widget, with a collection of prisms, and deriving prism for a struct which holds an enum, beyond using it with plain old enums.
I haven't delved as deeply into druid-enum, but it doesn't present an interface outside of the derive macro you can manually derive so at least won't work for this struct case, though I don't see why druid-enum wouldn't work for the collection case as well.
So I kind of see prism as a bit more flexible even though prism requires a separate widget that knows about prisms.
a note on the enum-like struct prism I manually derived...
In particular my struct has 2 fields, and 1 enum with 2 unit variants, allowing you to switch which struct field acts as top-level widget. While the backend of my program needs access to both fields from the top-level, because it receives data pertaining to both.
Now we have a derive crate (for Prism), we could include the widget generator for enums in
druid-enum
. This would make it more discoverable, as there isn't really a solution for displaying enums indruid
ordruid-widget-nursery
at present (is this claim correct?).The text was updated successfully, but these errors were encountered: