Unity UI or roll your own (need opinion for Runtime Editor App)

Hi everyone,

I will soon start working on a runtime editor application and my current dillema is whether I should use Unity's UI or build my own GUI system.

I would like to mention that I haven't worked with the Unity UI before so my experience with it is next to 0. In my application I will need to have access to all sorts of different GUI controls like tree views, lists, combo boxes, dockable/floating windows, tabs etc.

Watching some videos of Unity UI in action it seems that it's a pretty nice system, but I don't believe it can help me with what I need. It would probably take me much more time to make it behave the way I want it to rather than build my own, which to be honest would also probably be a much more interesting and educational experience

Any thoughts on this are highly appreciated.

Best Regards,
Andrew

 

LOL. The obvious answer is to use a 3rd party package like NGUI, but the editor I am building will also be released on the Store so I can not do that.

 

As a hobby, i've been making my own UI system for more than 2 1/2 years, and i'm still not done adding stuff.

Only a few days ago, did i get to adding Radio Options.

ex: Work In Progress, Using many images for a single radio toggle for kissUI


Rolling your own might take a while.

 

similar concern. is unity considering buying noesis, or microsoft considering buying both of you, making building wpf into unity a waste of effort ?

ie. custom controls, owner draw, super classing, and property system etc.

ps. UI and extensions on bitbucket , wpf on referencesource.microsoft
if we could just get MS to opensource it ... (while we're waiting)

shaderlab, cg, hlsl, glsl, webgl, spir-v, gamemaker, minecraft ...
ahhh, microsoft bought minecraft instead
what a mess

 

Thanks for the reply guys! Means I'll have to start playing around with the Unity UI then

@IzzySoft
kissUI is looking great by the way!