Hi, just now I heard news about Behaviour teams. How about UI Toolkit team? especially package of App-UI? Affected?
1 Like
I kind of hope so.
That data binding stuff is still an affront to programming, because nobody dogfoods their code at Unity anymore.
App UI seems like it shows at least a little bit of understanding how data bindings can work, but it’s still bafflingly verbose and boilerplate-heavy.
I think we will need to wait for a Unity official blog post to know that. App UI project could be a good candidate to open-source I think. That’s a kind of project that can be easily improved by a community.
Honestly for the binding system just set it in the uxml file. Opening them in a code IDE and editing the UXML is a lot faster. Also, inside of the UXML file you can do things you can’t inside of the UI Builder.
Example in the UI Builder, as far as I know, you can’t set the content-container attribute which is a huge improvement to workflow for bigger systems.
By changing the UXML code itself there is a single attribute you can add to a file to set the DataSource. I got a character, stat, and item editor with full data binding in less than 80 lines of C# code.
Wow it’s up to 80 lines? 
I was complaining when it was 11.
i.e. 11 lines for 1 binding. (And 22 for two, etc.)
(Ok I misread that, and it gives me hope at least that that person didn’t see the original bindings system through, because for the love of it I couldn’t convince them that Boilerplate shouldn’t scale linearly with program code)
I have 80 lines of C# for about 40 fields that are binded to a different value.
Most of that code is reading the database, listening for selection changes on the ListView showing all data entries, and for creating new data assets.
UXML has a property you just set there. Most of the stuff you can do without even using C# or the UI Builder.
1 Like