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

Prototype a new GUI #6

Open
ghjansen opened this issue Feb 19, 2017 · 0 comments
Open

Prototype a new GUI #6

ghjansen opened this issue Feb 19, 2017 · 0 comments

Comments

@ghjansen
Copy link
Owner

ghjansen commented Feb 19, 2017

This issue should consider the conclusions achieved on #5.
Here is a proposal for a new GUI:

cas-gui

The three components on top of the window should act as tabs, switching everything that is displayed in other components. This way, each tab acts independent from the others, so the user can simulate three cellular automata (one per tab) and see each one of them by navigating through the tabs.

Left corner keeps all configurations grouped by domain (similar to how it is today). Each option shows a panel on the right side that provides a good amount of space to interact with components. This panel can have a scrollbar if the amount of components is too big. The user can show/hide this panel at any time by clicking in the configuration options. The visualization of each configuration option is mutually excludent.

Right corner holds the tools to analyze the result of a simulation, same as it is today.

Bottom of the window contains the flow controls of the simulation (play complete, by step, discard/new, etc.)

All the white area of the window can be used to render the result of the simulation. This way, the window can be resized or enter fullscreen mode and all components can still be oriented to the window corners.

@ghjansen ghjansen added this to Backlog in Interface lift Feb 19, 2017
This was referenced Feb 19, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Interface lift
  
Backlog
Development

No branches or pull requests

1 participant