The main issue I have with the new UI system is that it lacks versatility, and I understand why it is this way…
Cocos has long been inspired from Cocoa, even the name was inspired from there, and hence some APIs are rightfully very close. But, when you look at the basic building blocks of both libraries, they are vastly different.
When in Cocoa you get an API to set the title, image, background image, I believe that should not translate directly to cocos. It would be good to have those convenient APIs, but after implementing
setTitleLabel, … etc. I mean, I think the developer should be able to build his control with any
Node subclass, because why not? We have things like
ClippingNode … etc, and they are all awesome, but not easily integrated with the GUI code.
P.S: I wish cocos studio can focus on doing one thing, and do it extremely well. We have spine for skeleton animations, SpriteBuilderX for UI and animation (which has an excellent Mac UI), maybe it can tackle another challenge instead of scattering the energy about.