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

Better UI #8

Open
edeetee opened this issue Feb 6, 2023 · 1 comment
Open

Better UI #8

edeetee opened this issue Feb 6, 2023 · 1 comment
Labels
enhancement New feature or request

Comments

@edeetee
Copy link
Owner

edeetee commented Feb 6, 2023

The current UI is not useful for what I want.

Reasons

I don't think egui is the best option. Want a more mature framework.

I'm not sold that the full node graph layout is the best for what I want.

Node graphs end up looking messy and chaotic without a lot of supporting containerization and abstraction. They are useful for conceptualizing the flow of data but fail when dealing with complex webs of data.

In TD, I often end up defining my main data sources with named nulls and referencing them later on. It would be good for a rendering framework to be centered around this.

Often, I have nodes set up in chains and only connect them together at the end.
Also I often end up doing the same thing repeatedly

This is kind of solved with containers but the workflow for this is slowed down.

I mention these things because maybe there can be some clean approach that fixes both of these problems.

Solutions

'Recipes' + 'Implementations'

Have half of the window show the recipes you have and the other half allow for complex connections between the recipes. I see this being problematic because it stops being able to just use the graph for simple things. Also this is pretty much just like having TD open with two windows, one inside and one outside the COMP.

Auto-aligned node graph

Instead of a free node graph, show the nodes as a grid where one dimension shows the data flow and the other dimension shows different element groups. I see having problems with understanding the flow of data when you have nodes that have a lot of input

More naming and referencing

I need a UI that forces you to do what I do in best case TD. Clearly named minimal graphs that are reusable.

@edeetee edeetee added the enhancement New feature or request label Feb 6, 2023
@edeetee
Copy link
Owner Author

edeetee commented Feb 6, 2023

I think this UI should also make reusing and abstracting things simply

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant