Graphical User Interface #200
Replies: 1 comment
General thoughtsHaving a graphical user interface (GUI) seems like an easy win in terms of accessibility, and, so, I reckon this is something that we should definitley consider as part of the IAA grant. The GUI should be easily navigable by a user who hasn't got much experience (if any) of using Python-based tools, so, ideally, it would be runnable without using the command-line interface (CLI). It also might be a good idea to beta test ideas, as well as sketches and flows, with the wider existing userbase to see whether any designs that we come up with are suitable and work well. NavigationCurrently, CLOVER is split into three streams:
The first stream, running without either a simulation or an optimisation, is functionality that likely doesn't need to be covered within the GUI as this can be done automatically and is faff that the user could do without. The other two, simulations and optimisations, should be covered by separate streams, but with the same interface for selecting components which are present as well as determining which types of components are selected for. Note: currently, downloading data from SketchesA sketch on the GUI is given below. ⬆️ Promotion to an issue ⬆️This is likely something that we will consider as part of the IAA grant, so is being promoted to a new issue within the repository. |
Uh oh!
There was an error while loading. Please reload this page.
This would be part of the 'expanding user base' section of the IAA grant and would allow wider use from a non-technical background. The aim would be to implement a very simple GUI that wraps around existing code and facilitates easier input/output management.
All reactions