Qt DetailedList: Draw action buttons

[johnzhou721]

Describe the bug

Qt's DetailedLists currently uses context menus to draw actions, which is against KDE guidance:

https://community.kde.org/Get_Involved/Design/Frequently_Discussed_Topics#Context_menus_are_not_enough

Steps to reproduce

Run the detailedlist example

No buttons, only right-clicks

Expected behavior

Primary and secondary buttons drawn in each row of the widget, with refresh with a button bar on top.

Screenshots

No response

Environment

• Operating System:
• Python version:
• Software versions:
  • Briefcase:
  • Toga:
  • ...

Logs

Additional context

Originally discussed at #4021.

I think a button bar included with the widget still makes sense without being part of the toolbar, especially when the amount of bars can end up like this on a KDE app:

All that is to say number of bars is not a huge concern.

Example of actions drawn in row:

Example of Refresh in a button bar:

[freakboy3742]

Worth noting that this sort of guidance would be consistent with other platforms guidelines as well; and even if it wasn't, adding an explicit API entry point for "refresh" would be a good idea.

I'm not 100% certain if it makes sense to include the refresh widget as part of the GUI, though. That approach guarantees that there is a refresh mechanism, but possibly not in a form that is good for the rest of the GUI. There's also the question of whether it's at the top or bottom.

Another idea would be to make the "pull to refresh" behavior opt-in on all platforms. This would allow us to raise a warning on platforms where it isn't available; and as a transition mechanism, provide a warning to users who are assuming that it will be.

Yet another idea would be to merge the two. Add a "refresh_behavior" value, with values for "pull from top", "pull from bottom", "button at top", "button at bottom", "external" and "default". If the user selects "default", we pick a value that is platform appropriate; if they pick an option that hasn't been implemented, we raise a warning and fall back to one that does.

[johnzhou721]

@freakboy3742 At the top may seem more appropriate. I like refresh_behavior a bit more, though.

Worth noting that pull-to-refresh is rarely seen on macOS as well.

[freakboy3742]

@freakboy3742 At the top may seem more appropriate. I like refresh_behavior a bit more, though.

I suspect that depend entirely on the GUI layout in which the DetailedList is used.

Worth noting that pull-to-refresh is rarely seen on macOS as well.

Granted . On macOS, an in-GUI refresh button would make more sense as a default.

[johnzhou721]

@freakboy3742 Can we please tag this and #3995 the spiffy new shiny blue Qt tag? Thanks.