New GUI System actually be viable for mobile?

How many of you think the 3.6 GUI system is going to viable for mobile use beyond just a performance standpoint.

If they got the current UI system working well performance wise on mobile, thatd be great. If they added in some easier functionality to animate things, and to lay out UI components, thatd be nice too.

But do you think its going to be comparable to an actual cocos2D ui? Will sliders behave the same as cocos2d sliders? Will buttons behave the same as cocos2d buttons? Will you be able to type directly into textboxes and use the magnifying glass on the text boxes?

Is it really coming in 3.6? That would be really cool but last I read is it’s supposed to come in version 4.

Version 4? It should have been in 3.5, so I think we should still expect it in 3.x.

Is there any info on this besides the mention in the roadmap for 2011?

You cannout expect it at all. It might come with 3.6, 3.7, 4.0, 4.5 or never. Lots of people waited setting up their current titles gui in the hope it would be in 3.5, but as it turned out its not.
Last word from Unity on this was - it doesn´t meet Unitys Qualitystandards yet. And it might never.

That’s nonsense. They’ve announced it and already put effort into it. Of course it will be available at some point. It’s just not known WHEN.

Show me where they said that it might ‘never meet Unity standards’, officially.

For mobile - that might be another thing, though.

What i mean by “never” is, that it is very well possible, the current state of this GUI Framework turnes out to lack some important abilities on whatever plattform. And than unity might scrap it and start all over with a different approach. And that might take a loooooong time.

Or a third party comes up with a superb solution, and thats being used. Think Scaleform.

So its better to at least make a “prototype” GUI in your titles with the existing OnGUI stuff or one of the Unity Extensions. Than you have the Design and functionally done, and can port that to the vapourish new GUI Framework once it arrives. Or leave it as is if it arrives not.

There is an indefinite timeline on the feature, i think saying ‘never’ is just wrapping it up in hyperbole. At the end of the day a responsible developer shouldn’t plan a product dependent on a feature with an indefinite deadline.