An update on the New, Flexible Studio UI

[TheGrimDeathZombie (Reapimus)]

@VerticalPug

but I simply cannot bring myself to. Importing an animation, adding scripts, modeling, tool switching, etc. are all built into my brain at this point

Then create a custom tab that has all of these and is better suited to your workflow or just make use of the community-made legacy layout tabs that was even linked in OP. It’s not like they haven’t given an immense amount of flexibility for developers to take advantage of.

Bring Back Old Ribbon Style For the Next Gen Ribbon

Update on the Custom Tab Builder Plugin Hello! I have created a list of .json files that brings back the layout of the old ribbon to the Next Gen Ribbon. It doesn’t contain all of the old tabs, but contains some of the most used and requested ones from what I’ve seen. If you wish for me to add more, feel free to reply, and I’ll look into it. Also, feedback is appreciated! I especially hope this is useful for the people that still haven’t gotten used to the new layout, or simply want somethin…

@VerticalPug

It’s impractical for a massive corporation with practically unlimited resources to maintain two separate UIs?

Roblox doesn’t have unlimited resources, this is an unrealistic fantasy. They have gone into extensive detail on why it simply isn’t possible to maintain both of them:

@MeshOfPaul

Not only was the old UI built in Qt/C++, there was multiple subsystems (that’s nicer than saying “hacks”) in place to handle the interop between the Lua and C++ layers. A lot of weird state management in the C++ side that is a large problem area for obscure bugs, hangs, and crashes.

But let’s just say we didn’t need to replace the subsystems. New features would need to be implemented twice: once in Qt and again in Luau. But ok maybe we figure out some abstraction that makes that slightly less painful.

So now we have 2 fairly different UI front ends in parallel — testing and QA get exponentially more difficult (more than just double the work). Then bugs start to appear and we spend tons of time root causing them to one of the UIs. Or maybe it’s a bug in our new UI abstraction layer… the time spent doing all of this directly takes away from any time for actually adding new features.