Improve the layout of the GenericPlanForm so that less scrolling is needed.

This was the solution to difficulties at BMM.

https://stackoverflow.com/a/66450161/1221924

Creating this as a tracker for what the acquisition web client might want to pull from a facility API. These are just initial ideas that could use more input from @stuartcampbell and @JunAishima. Initial ideas:

• Obtain a data_session_id from the facility API for the current set of runs
• Obtain related data to the session such as the proposal_id, saf_id, etc
• Obtain and display useful beamline information in the interface such as name, location, contact details for relevant staff, emergency phone/email in case of issues, current status of ?

Ideally some of these things would be obtainable in prototype API that might be hardwired, along with the link to get it, i.e. the queueserver would certainly know a beamline identifier such as its FXI, HXN, etc, that would then be used to call facility API to get more information to display about the active beamline. The beamline and user identifiers might be enough to get the proposal identifier, etc.

Task for 5LS demo.

• Make bluesky-web-client console logging quieter or more configurable
• If anything is in the History, the web app burns 0.5 CPU doing nothing
• More things Tom noticed…

Display the currently pending queue to the user formatted in a way that is understandable to a human.

This is a pre-requisite to bluesky/bluesky-queueserver#17 .

Display information about the currently running plan.

It would be great to enable CI for this repo (on TravisCI or Azure Pipelines). We'll need the manager/server running to test the client side.

Now that more of us are writing TypeScript/JavaScript code we should establish coding conventions, and maybe look at how we can automatically use some of the conventions. I would suggest using camelCase for functions/variable names, and capitalized CamelCase for class names. I think four spaces is conventional, and we should probably use either lower case filenames or (as seems more prevalent) CamelCase.tsx for classes etc. I already see Python snake_case sneaking in and making things look inconsistent.

State from one plan can get added to another plan

Currently we can only see the uid of the item in the queue. I think it would be useful to the more information, similar to the list of historical plans.

We need a "Collapse" button to minimize all open cards in the History list to quickly close potentially a large number of expanded cards.

We discussed with @gwbischof that having an "Expand" button may bring an expensive operation, so at this time we will not be adding it. Alternatively, the "Expand" button may maximize only visible cards. That's an acceptable option.

Clicking up/down on items in queue expands the accordion

Task for the 5LS demo.

Currently there is a + button to add an additional value to a parameter that is a list. There should also be a button to reduce the number of items in the list.

bluesky/bluesky-queueserver#93 adds an instruction called queue_stop which can be inserted into the queue to pause the queue when it is executed. Let's add support for this on the GUI.

We need better-structured data displayed in the history of plans. The panel should be wider, or expandable, and should contain records in a tabular form, so that not only a uid[:8] is displayed, but also a timestamp and other useful info (scan_id, detectors, motors, etc.)

FIx the way pause instructions look in the queue.
Currently they just show a uid, this isn't very meaningful.

The first time that a plan is selected from the Queue Items list the parameter input widgets are not visible.

With pip install git+https://github.com/bluesky/bluesky-webclient, this package installs as UNKNOWN-0.0.0.dist-info.

Since it's not yet on PyPI or a conda package, I mindlessly installed with pip from github, as above. The packaging needs attention. Realize this is pre-release but the concept has captured the attention of the APS now.

Support addition of items to the queue from an excel sheet

Add the bluesky logo to the GUI

Edit items that are already in the queue.

Get login working

Display queue status

Make another object like PlanList that also shows detailed information about each queue item without the need to expand.

When it's pressed on the "Home" page, the following message is appearing in the uvicorn log:

INFO:     127.0.0.1:65479 - "POST /environment/undefined HTTP/1.1" 404 Not Found

It works fine while pressed on the "Acquire" page.

Now that we have a base it is important to get to a minimum viable product defined by:

• Button to add a plan
• Ability to choose between allowed plans
• Ability to edit some parameters in the plan
• Creation of an acquisition environment
• Starting, pausing, stopping the processing of the queue
• Viewing the currently executing plan

There are other features that must follow, and pretty soon after this it will be useful to sketch this out for a minimal real beamline. This doesn't attempt to visualize any data at this stage, and concentrates on what already appears to be presently available as part of the queueserver API.

@cryos: "If you look at App.tsx, the unordered list there, I had been meaning to make that into a component that can be reused on multiple pages, and to use the Material-UI list component instead of the default ul, li etc, i.e. https://material-ui.com/components/lists/"