Paweł Grabarz a00efb28f3 Widgets integrated with graph nodes (#6347) ... Rewrites node input component. Now the input is composed of multiple widget components arranged in a tree of views with automatic layout. That allows creating complex UI elements on top of the node itself, and further widget positions will be automatically adapted to that. The tree roughly follow the span tree, as it is built by consuming its nodes and eagerly creating widgets from them. The tree is rebuilt every time the expression changes, but that rebuild process reuses as much previously created widgets as possible, and only updates their configuration as needed. Each widget type can have its own configuration options that can be passed to it from the parent, or assigned based on configuration received from the language server. <img width="773" alt="image" src="https://user-images.githubusercontent.com/919491/233439310-9c39ea88-19bc-43da-9baf-1bb176e2724e.png"> # Important Notes For now, all span-tree updates are sent over to the shared Frp endpoint of the whole tree, so there is no mechanism for intercepting them by the parent widgets. One idea would be to use existing bubbling/capturing events on widget display objects for that purpose, but I think existing implementation is simpler and more convenient, and we can always easily change that if we have a use for it. There are some issues with performance due to much more display objects being created on the graph. Expect it to be a little worse, especially at initialization time.		2023-04-26 19:37:54 +00:00
..
src	Widgets integrated with graph nodes (#6347)	2023-04-26 19:37:54 +00:00
Cargo.toml	Ability to change the execution environment between design and live. (#6341)	2023-04-25 20:28:15 +00:00