Author Topic: Fate of NGUI after uGUI  (Read 5363 times)

schellenberghq

  • Newbie
  • *
  • Thank You
  • -Given: 0
  • -Receive: 0
  • Posts: 31
  • Game Programmer
    • View Profile
    • Blog
Fate of NGUI after uGUI
« on: November 13, 2013, 04:22:11 PM »
What is the fate of NGUI after uGUI releases?
NGUI and uGUI are very similar because it's from the same developer, but will there be drastic enough differences to choose one over the other?
Or is it more like those using NGUI will continue to use it in current projects, but in new projects switch to uGUI.
---------------------------
Jacob S.
Game Programmer
---------------------------

ArenMook

  • Administrator
  • Hero Member
  • *****
  • Thank You
  • -Given: 337
  • -Receive: 1171
  • Posts: 22,128
  • Toronto, Canada
    • View Profile
Re: Fate of NGUI after uGUI
« Reply #1 on: November 13, 2013, 04:31:49 PM »
NGUI has grander scope than uGUI, in part due to legacy support (creation of atlases and bitmap fonts being two such examples). uGUI is a lean version of NGUI that does some things natively in C++, gaining performance but sacrificing flexibility. uGUI isn't "from the same developer" though. I am just one of them. It's true that I started it, and it's true that it derived from NGUI's codebase, but now there are several devs working on it, and I am moving to the shadows myself (I'm really itching to get back to game dev).

I will keep supporting NGUI while people are using it, and I will keep adding things to it to make it better. But that's about all I can say on the matter right now. :)