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
What is shown as content of a Space View in the Blueprint View is an Entity Tree. Under the hood it's the result of applying a query, which is specified in the Space View Blueprint. That query can include selecting multiple sub-trees from the EntityStore, transforming / overriding some of it, plus adding some new inline data (e.g. a background mesh). However, even after all that, the thing you klick on in is still an Entity Tree, just like what you see in the Streams View, and that should be conveyed visually.
First things to try
We've made a decision on the first things to try.
Remove the "group" concept from the Entity Tree in the Blueprint
Use the entity and component icons everywhere (Blueprint View, Streams View, Entity Query Modal)
If this ends up looking too cluttered, improve the icons
nikolausWest
changed the title
Make entity tree in blueprint view look the same as in the streams view
Harmonize all Entity Tree visualizations
Jan 23, 2024
What is shown as content of a Space View in the Blueprint View is an Entity Tree. Under the hood it's the result of applying a query, which is specified in the Space View Blueprint. That query can include selecting multiple sub-trees from the EntityStore, transforming / overriding some of it, plus adding some new inline data (e.g. a background mesh). However, even after all that, the thing you klick on in is still an Entity Tree, just like what you see in the Streams View, and that should be conveyed visually.
First things to try
We've made a decision on the first things to try.
Background / more context
The goal is to make it obvious that Entity Trees in different parts of the UI are the same thing. We currently show three different Entity Trees:
Streams View
Blueprint View
Entity Query Modal
Related but not exactly on topic
The text was updated successfully, but these errors were encountered: