Input base widget
- Dominant language
- Dart
- Stars
- 3.5k
- Forks
- 506
- Avg merge
- 11d 2h
- Merged PRs (30d)
- 3
Description
Currently, most of our inputs make use of `HoverButton` to respond to mouse (hover, press, touch events and even keyboard events, as well as disabled mode. In addition to it, [`ButtonThemeData`](https://pub.dev/documentation/fluent_ui/latest/fluent_ui/ButtonThemeData-class.html) static methods are used to change the color of the box, usually a `Container`, based on the current `WidgetState`.
While this method works fine, we should expose the developers a better way to handle input, like material's `InkWell`.
There are multiple variants of buttons, and it should be handled by this new input, dev friendly widget.
_Originally posted by @Nico04 in https://github.com/bdlukaa/fluent_ui/discussions/928#discussioncomment-13178043_
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the current use of HoverButton and ButtonThemeData, then compare the requested behavior with Flutter's InkWell. Define how the new input widget should support the listed pointer, keyboard, disabled-state, and button-variant behaviors; the work is done when those variants have a clear, developer-friendly API.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dart, flutter
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100