Quill doesn't use the Bevy Button component, because the latter designed in a way that doesn't fit well with reactivity and style selectors. Instead, it's a fairly simple matter to define a custom "button" widget using Quill views.
In addition, it is anticipated that eventually there will be many kinds of widgets that have button-like behavior but which are not buttons: toggles, radio buttons, checkboxes, and so on. "Button" should not be a built-in widget type, instead we should allow an easy way for users of the library to create their own button-like widgets.
However, one thing missing is support for accessibility: focus tracking for example. This is done via integration with AccessKit.
An important side benefit is that this will also provide an example of how make other kinds of widgets that use focus.
Quill doesn't use the Bevy
Buttoncomponent, because the latter designed in a way that doesn't fit well with reactivity and style selectors. Instead, it's a fairly simple matter to define a custom "button" widget using Quill views.In addition, it is anticipated that eventually there will be many kinds of widgets that have button-like behavior but which are not buttons: toggles, radio buttons, checkboxes, and so on. "Button" should not be a built-in widget type, instead we should allow an easy way for users of the library to create their own button-like widgets.
However, one thing missing is support for accessibility: focus tracking for example. This is done via integration with AccessKit.
An important side benefit is that this will also provide an example of how make other kinds of widgets that use focus.