Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UI/UX Improvements #28

Open
8 tasks
burgholzer opened this issue Apr 22, 2022 · 0 comments
Open
8 tasks

UI/UX Improvements #28

burgholzer opened this issue Apr 22, 2022 · 0 comments
Labels
feature New feature or request

Comments

@burgholzer
Copy link
Member

At the moment the graphical editor is functional, yet not very user-friendly and pretty. The following represents a non-complete list of possible improvements:

  • The UI is not really responsive, e.g., the circuit that is displayed should, in general, fit the display area as a whole and not be cut off. The editor should also resize appropriately to fit its content.
  • The Log Messages sub-element can be moved around arbitrarily. It would be great if this was also possible for the circuit view.
  • The costs window can easily be integrated into the main UI by making the Log Messages Window smaller.
  • Cost calculation should probably always be performed in combination with synthesis, since it takes practically no time and provides useful information. This also fits nicely with integrating this information directly in the UI.
  • In a similar fashion, the statistics about the resulting circuit should most probably also include what is currently printed to the console: number of lines, inputs, constants, outputs, garbage values.
  • The simulation result could/should also be integrated into the main UI. It could be placed instead/besides of the Log Messages since they do not occur that often.
  • The simulation result does not look very appealing and is hard to read in general. there is definitely a way to format this in a nicer fashion (grouping of signal variables, spacing between in and out, removal or summary of const_0 inputs, etc.)
  • On the implementation side, it is rather inefficient to synthesize the circuit again for the simulation and the calculation of the cost. If a circuit has already been synthesized, the resulting circuit can be used for the simulation. if a new circuit shall be simulated, it first has to be synthesized anyway.

Each of these task can be a separate pull request and any further feedback is welcome!

@burgholzer burgholzer added the feature New feature or request label Apr 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant