UiSurface should implement component,no just for the camera

[MushineLament]

What problem does this solve or what need does it fill?

Sprite does not have a layout, but node do.But the node only follows the camera.
When I wanted to replicate some simple blender graphs, my situation was quite awkward.

No one answered my question, maybe question it's not accurate.
#discussions/21242

I found a discussion about graphs, but it focuses more on functional logic
#discussions/6719

I have reviewed the source code related to node layout and moved the globaltransform,it is work. Nodes should not be limited to camera layout at all.This will increase bevy_ui's higher degrees of freedom.

What solution would you like?

Add a Component to Node, root node no longer calculates layout based on camera.
This component will make transform transformable and affect the position of the root node, without affecting the layout of all child nodes of the root node.

By using globaltransform, all children node can be transform, but there may be layout issues

What alternative(s) have you considered?

New plugin bevy_sprite_layout has been added to solve layout issues, but some node functionalities may be missing

Additional context

I haven't found a solution that can transform transforms like sprite and has node layout and functionality.
I don't have strong enough ability to solve my ideas, I think nodes should be more powerful and versatile.

[MushineLament]

In my idea, when Root Node is no longer limited to camera, its position will be rendered by default(game world center).This may require the introduction of sprite anchor to control the rendering orientation of the transform node.

[MushineLament]

Allowing the root node's transform to freely seems unwise. Because useless data was generated when the root node was subjected to UiSurface. I think there should be a NodeContains component that functions like a camera and can layout nodes.This also means that UiSurface should no longer be used as a resource, but each NodeContains Component has its own UiSurface, including the camera. For potentially different target cameras, it still uses UiSurface Resource

[MushineLament]

I have been studying rendering for a week and can roughly solve the rendering problem.But I'm a bit indecisive about the handling of functionality. I don't want to make too many modifications to the system of bevy_ui.However, the required components involved in bevy_ui's system will be affected under UiSurface. And UiContact uses the component UiSurface, which is therefore affected.This means that I need to encapsulate the necessary components related to the node or modify bevy_ui. I am not very confident in my abilities, so I plan to develop it as a feature, which also means encapsulating the node once.

[akimakinai]

Does this overlap with (or equals to?) world-space UI (#5476)?

[MushineLament]

这是否与世界空间 UI （#5476） 重叠（或等于？

Yes, issues repeated it