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

First Cut Of Web UI #182

Open
azriel91 opened this issue Feb 1, 2024 · 2 comments
Open

First Cut Of Web UI #182

azriel91 opened this issue Feb 1, 2024 · 2 comments
Assignees

Comments

@azriel91
Copy link
Owner

azriel91 commented Feb 1, 2024

Related: #125

Use leptos and dot_ix to create a first cut web UI:

  1. Render flow graph
  2. Buttons to invoke commands
  3. Render progress
  4. Render outcome

Interactively rendering additional information, or highlighting the parts of the outcome when the progress step is hovered (or vice versa) is not necessarily in scope.

@azriel91 azriel91 self-assigned this Feb 1, 2024
@azriel91
Copy link
Owner Author

For rendering the flow graph, perhaps the following works:

  1. Create peace_flow_model, and define a FlowInfo which is essentially the Flow without logic.
  2. WebiOutput, is instantiated with FlowInfo, which is passed to a <FlowGraph flow_info=flow_info cmd_progress=cmd_progress /> component.
  3. FlowGraph uses dot_ix to render the graph -- specifying the nodes and edges.
  4. In impl OutputWrite for WebiOutput, the Progress* updates are used to change the WriteSignal<CmdProgress>, which influences the tailwind_css styles passed by FlowGraph to dot_ix.

@azriel91
Copy link
Owner Author

azriel91 commented May 26, 2024

Refactorings to make drawing the outcome diagram easier:

  1. Rename peace_resources to peace_resources_rt.
  2. Rename Item to Step decided this doesn't make sense.
  3. Create peace_resource_model to house the ResourceInteractions type, which represents:
    • From/to interactions between two resources.
    • Modification of n resources (e.g. 3 servers all have X patch applied)
    • Security group affecting n servers modified

Perhaps we do the first two as part of #187 first, then continue this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: In Progress
Development

No branches or pull requests

1 participant