You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think aspects are to much entangled with categories. Aspects should not be defined by creating a category internal or advanced categories are something different this should be reflected. You already have a got option where to set the aspect. Unfortunately this is not working when I set it here I still see the nodes in the node browser.
I think here it is already really clear and good to find. What is missing is a visual indicator on the node to see if it is internal or advanced this could be a small colored dot or an icon before or after the name, this should not be an (Internal) or (Advanced) prepend again this is something else.
The text was updated successfully, but these errors were encountered:
Unfortunately this is not working when I set it here I still see the nodes in the node browser.
which nodes? In this example we are just talking about the process node GridNode, not the operations, right?
internal nodes show up in the document itself, but that's not what you mean?
So then is this a bug report?
I think aspects are to much entangled with categories.
We added those two places to set the aspects so that it gets easier.
We didn't want to remove those other ways of declaring aspects further outside, since those can be super useful and removing them would be breaking. If you don't like this way of declaring them just don't use them.
What is missing is a visual indicator on the node to see if it is internal or advanced this could be a small colored dot or an icon before or after the name, this should not be an (Internal) or (Advanced) prepend again this is something else.
You are talking about the node application side, right? Please add some design ideas so that we can understand.
May I ask you for a favor: please have another look at the rules for this repo. https://github.com/vvvv/VL-Language
The idea here was to describe a problem first and make it obvious that there is room for improvement. Separate this from your idea of a solution for the problem. Language decisions are far-reaching. Those deserve this dialectic approach of finding a solution for an accepted quest.
I am mentioning this mainly because I am trying to find a way how to improve idea-sharing und understanding each other. There might be other ways how to improve the idea-sharing. If you think this is something to discuss, let's move it to a new quest.
gregsn
changed the title
Optimize Aspects
[Quest] Optimize Aspects
Mar 9, 2024
I think aspects are to much entangled with categories. Aspects should not be defined by creating a category internal or advanced categories are something different this should be reflected. You already have a got option where to set the aspect.
Unfortunately this is not working when I set it here I still see the nodes in the node browser.
I think here it is already really clear and good to find. What is missing is a visual indicator on the node to see if it is internal or advanced this could be a small colored dot or an icon before or after the name, this should not be an (Internal) or (Advanced) prepend again this is something else.
The text was updated successfully, but these errors were encountered: