More Atomic Control Nodes? #9652
Shadowblitz16
started this conversation in
GUI
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
see #4994
How would you guy's feel about breaking down component into more atomic parts?
For example Button, TabContainers, ItemLists OptionButtons all have text but not all the same options for that text (for example shadow).
This could be broken down into smaller parts.
for example...
Button's focus, hovered, pressed, and disabled state and styles could be moved down to control. (There is a suggestion for this I believe)
Buttons could just be Control node's with Label's or RichTextLabels
TabContainers could be HBox and Tabs with Labels,
Itemlists into VBox and other Controls,
and Option Button's into Popup's and Controls
Control's like ItemList's or TabContainer's items could be dynamically created through data/control binding,
This way we can edit data in the inspector and the control item's for the corresponding data would be automatically be added, removed or updated
Control's could also be made to share state like pressed, focused, hovered, and disabled.
This would allow us to more easily make composite controls.
Maybe a package node that could allow use to treat it as a certain node and export/edit child node's of the scene?
This way we can make a Button Package scene that has access to both button's and it's label's properties?
Right now ui is super tied to desktop style interfaces and this could allow user's to more freely compose thing's in the way they need for their game.
Beta Was this translation helpful? Give feedback.
All reactions