Databrowser timepicker

[JulReinhardt]

I added 4 QRadiobuttons to the search_input_widget to quickly select time ranges for the catalog search. I used QTDesigner for the actual layout. The .ui files were converted to .py and then I import the classes into gui/bluesky/search.py

[ronpandolfi]

Can we eliminate the .ui files and clean up the ui_*.py's?

[JulReinhardt]

Can we eliminate the .ui files and clean up the ui_*.py's?
We could, but I thought in case someone wants to quickly changes things visually the .ui files come handy as can be used in QtDesigner. But I will clean up the treeview.ui/.py that indeed sneaked in there.

[ronpandolfi]

As discussed, this PR needs:

• Remove all .ui files
• Remove auto-generated .py files
• Write ui components in PyQt, without use of Designer
• Remove unused imports

[JulReinhardt]

As discussed, this PR needs:

* [ ]  Remove all .ui files

* [ ]  Remove auto-generated .py files

* [ ]  Write ui components in PyQt, without use of Designer

We did not discuss.
What is the future strategy for building GUI in Xi-CAM?

[ronpandolfi]

There's a conflict between the selection of the time range from the radio buttons and the datetime box. Changing the datetime range to a custom value doesn't update the radio buttons. I think the UI can also be made more concise by changing the radiobuttons to QComboBox with options "All", "30 Days", "Today", "Last Hour", and "Custom...". Then we only need to show the datetime range UI when "Custom..." is selected.

• Change QRadioButton's to a single QComboBox
• Hide/show datetime range boxes based on QComboBox selection

[JulReinhardt]

Fix: Radio buttons are now reset, when custom datetime range is selected.
I like the idea of showing the QDateTimeEdit when selecting custom, on the other hand using a dropdown instead of buttons means slightly more clicking, whereas the buttons are the quickest way to select. In contrast to other cases eg. stream selector that depend on the data, we know what options to show here.
Should we add a "custom" radio button that opens up the QDateTimeEdit?

[ronpandolfi]

I can't easily confirm, but I think I see a flaw. I suspect that newly generated runs won't be shown when the standard time span modes are used, since it gets time.time() when the mode is selected, not during each update. I'm going to attempt refactoring.
Edit: Also, the start of the range wouldn't slide

[JulReinhardt]

Yes, it would be a flaw if new runs don't show up, due of the time span not being adapted. I can have a look into that. How would it be any different for using QComboBox dropdown instead of Radiobuttons, that should not make a difference?

[danielballan]

This work was revisited in bluesky/bluesky-widgets#13, now merged. Safe to close this PR?