Lets be honest, working with the legacy chat was hell. You had to fork it, look through unreadable code and edit it.
Yes, they probably shouldn’t have removed it entirely, deprecation was enough. Also, you can still somewhat make your own build of it using the legacy core modules.
I don’t remember if this was asked before but with the Luau UI is there a chance we’ll be able to make custom themes for Studio in the not-too-distant future?
Legacy Chat was very good for customizations, yeah, and It was a Legacy feature. I like legacy features of Roblox instead of getting it more modernized. I think They should just stop removing Legacy features because they give nostalgic feelings.
Yes there’s lots of styling updates in the pipeline. We will deploy them to the Beta over the coming weeks (as we get them done!)
I’ve been waiting on this for so long. People saying its bad just can’t handle a change.
What I’m wondering though, are there any plans to allow for custom coloring for all the uis?
Here’s the updated version for the folks who haven’t seen it yet, I think it’ll be useful to see.
Consolidating all testing modes under one dropdown window is something I didn’t even know that I needed in my workflow. Thanks!
Thanks - Looking forward to this when it’s all fixed.
Many people don’t realize or forget - that the reason this version was created in the 1st place - was because it was created on old technology… and couldn’t be upgraded to features users were asking to be added to the old Studio.
It is like trying to Fix Windows XP with todays Tech - which is wasted exercise.
Let’s keep grinding - pointing out bugs - and it will be fixed more.
I have decided to stick it out on the New Studio (even if some Plugins are still missing). 
This is just the Blender 2.8 overhaul all over again. An old, dated, frustrating to change ui gets replaced with a new, modern ui with extra functionality, and everyone freaks out.
I’ve been using this beta for a while, and I’m loving it. I hope to see the color and padding changes soon, as those will definitely help! Looks much nicer than the old ui, and a lot more professional too. It’s very much less of an eyesore than before.
Ok I do have a solid question, so firstly is most of the new studio UI built with the new UIStyle system and secondly will plugin developers be able to use those same built-in tags or attributes to make their own plugin UI?
Technically, it will be possible. First we’ll need to continue converting Studio UI to using the new style driven system and using the same color tokens. We’re doing that as a part of our design system implementation. Once that’s done, we’ll be that much closer to supporting custom themes. Unfortunately it’s a ton of work to get there - 10+ years of random UI approaches and hard coded colors values 
so I can’t promise the “not-too-distant” part.
Please, please make this toggleable. while it looks great, it isn’t practical. everything is spaced out, unlike with the current design which is compact and neatly organized. the goal of a game engine should be ease of use, not just visual appeal. Other than that, there is no point in making everything a monotone gray, its just makes it harder for everyone to distinguish between the tools and instances.
Especially for people with small screens, this new interface is about 20% bigger in height, which believe me when I say, makes a day and night difference.
(please, do correct me if I’m wrong)
Becomes a question of whether you want to prioritize nostalgia, or cleaner, far easier to use internal code. Can’t have both, and one is clearly more necessary than the other.
Unrealistic to think that the latter wouldn’t be prioritized.
Yes, yes, and yes!
We are building a reusable UI component library as we go and we fully intend community plug-in developers will be able to make UI the same way that we do. Then we can start offering better UI building tools and workflows that benefit everyone. 
I’d assume most developers would want things to stay the same, generally, layout-wise. I should be able to open Studio, and my normal workflow/knowledge of where things are should not be entirely gutted.
Has the feedback been positive in that regard? It looks difficult to get used to still.
The platform should stop improving because old = better? Sorry, but practicality is more important than “well, it was that way in 2016, which makes it better!”. We need change especially when it’s for the better and this is one of those changes (so is TextChatService)
this sounds awesome! I know you cant promise any exact dates or timelines, but would it be possible to know how far ahead this project is?
This is probably related to the tooltips issues, but when the ribbon is undocked, I get similar problems of it rendering over other active windows:
That’s a good comparison! As someone that suffered through pre-2.8 Blender, I’m always impressed by how much they’ve improved — it still doesn’t make me a very good 3D modeler though haha
Unfortunately many people would prefer to drown in nostalgia, than to see the truth:
Old systems get harder to maintain each passing day, change is inevitable, and the quicker you adapt and perhaps provide useful feedback, the better your experience will be.
