Custom buttons

[loudinthecloud]

I believe there's room for providing custom buttons to the player, and associate those with external handlers.

In my application I've added an HD button that appears next to the full-screen button and it worked great, see - master...loudinthecloud:flutter_chewie_with_qualities:add_hd_button

Not sure if this is the best design, but it gets the job done.

I think the user should be able to provide a list of buttons in the chewie configuration, and perform any action he needs externally. I think the most common features will be to implement a stateful button, with handlers for each state. Please let me know if you'd like a pull request, and what would be the requirements.

[diegotori]

There are two ways this can be a proper API feature:

1. Create an optional builder method in ChewieController that returns a nullable Widget to display, passing in the BuildContext from the requisite controls.

2. Expose a listener from ChewieController that the controls listen to that when invoked, it would be a cue for those widgets to rebuild themselves, thus invoking the controller from the first way.

Nevertheless, 1 can be invoked from the stateful widget that's using the Chewie widget, which will in turn rebuild its UI and invoke the new builder methods from the controller.

That way, we're not hard-coding opinionated buttons into this library.

Either way, option 1 is also ideal because you can return one widget that displays a Row of widgets for example, and in turn, you can make that widget stateful, thus only scoping rebuilds to that component and not Chewie. There will need to be another duplicate optional builder methods for displaying a widget after the row of default buttons, to better controller whether to add this custom widget before or after them.

[diegotori]

If you get around to doing this, you should also create the same type of optional widget builder for each corner of the controls so that one can display custom widgets from a given area of the overlay.

Either way, I accept PRs for the first way of implementing this. Think of this added feature as a stretch goal.