Project Status

If you plan to look at one of these tasks, put your name beside it, and let people know in the Slack channel.

Larger work packages

Widget interface - Will Rogers
- Prop types at runtime
- Default props
- Widget registration
- How functional widgets should share common code
Positioning and layouts
- Which of the possibilities of CSS positioning should be available?
Filesystem layout and file serving
- Opening files in different screen locations
- URL formats
Performance and benchmarking
- Coniql
- Websocket performannce, including arrays
- Benchmarking suite
- JS code
Plotting (2D and 3D) - Bryan Tester
- Server-side plotting
- Nivo charts, plotly
- How does Jupyter do plotting?
Understand Z-ordering and click pass-through
Themes, styles and classes
JavaScript VTypes and handling EPICS7
- Use Coniql's tartiflette branch
- Do we need to handle arbitrary structures?
Load EDM files directly
Databrowser
GDA UIs
Local application launches
Packaging as an Electron app
Editor
Formula functions as in Phoebus
Review existing projects
- React Automation Studio
Javascript build system
Documentation

Handle multiple PVs on one widget (see Phoebus widget runtime code)
- Could all these PVs be part of a single device?
Define rule capabilities
Prototype Pyburt UI
Can a widget define its own new prop type?
Simplify 'wrappers' and avoid extra divs where possible
Allow group-box style border on any widget
Allow PV values to be used as symbols, as in the EDM MenuMuxPV widget
Make widget parsing more generic:
- allow complex parsers to create multiple props
- allow widgets to provide their own custom parsers
- forbid unrecognised fields (at least in json files)
Investigate React Testing Library