Of course - when we can create our own TABs - that’s ALL you will need for your common used items - so you can design the bar however you feel useful to you.
As you can see - there’s not much to fuss about… space wise.
I use windows… so it is across the board… on all platforms.
They are aware of this… and will sort it out before the “final” product.
Thats also the reason I have to use the standard UI … also have over 40 plugins.
Pity you CAN’T scroll the Plugin “drop down” menu… that would have helped me stay with the newer UI.
At least you use a higher screen resolution… getting 27 on top… and 34 dropping down.
I on the other hand… I only get 17 plugins across on top, and 17 in the drop down list
I’m criticising the UI and not the backend code that has zero impact on me as a user, I do not appreciate your unnecessary attitude, please remain civil.
If you think that its outdated to have a user-friendly UI that doesn’t waste space or hide top-level features behind drop-downs and secondary menus, then I don’t think you’re fit to comment on the industry, especially when its those mis-informed who have changed the modern industry to be so against user-friendly and accessible design. Why do you think so many web standards have pushed for accessible design in the past few years? its because of bad UI changes like this.
That’s just ableist negligence. A few pixels on your screen could be hundreds on another, and depending on the screen size AND resolution, it could be several cm of physical space lost. Any loss is still a loss, and it is completely unnecessary.
I’d appreciate if individuals stop making passive-aggressive misinformed comments on my valid criticism of the UI as if I’m somehow talking about a framework that literally does not impact me as a user of it (Why some people seem to think I was somehow talking about the core system that I have never touched as someone who doesn’t create plugins I have no idea).
Never mind… thought I was helping… but clearly not.
I will leave my post images as is so others can learn the differences.
I will rephrase my comment to you… as I can’t deselect your name.
However… I accept that bigger screens & higher resolutions can mean more pixel lines.
In that regard… it would be interesting to know how much they/you might lose.
I myself use a modest display… (others fortunate with bigger screens)
We are moving away from Qt based UI. We cannot support two completely separate UI systems in the long run. We are running two currently as a temporary measure to ensure we get hands-on feedback and to not disrupt anyone’s workflow. This is already a lot of effort as teams are building for both UIs. Not to mention dealing with bugs and other support issues in two different systems. We are putting in this extra effort purely to provide a functioning UI for hands-on feedback.
The new UI as it sits today is a first pass and we have lots of improvements we are actively working on that will be released into the Beta as they are ready. Right now we expect to stay in this Beta state into early 2025. But make no mistake, at some point next year we will be changing the default UI of Studio.
If you like the tabs and structure of the old UI, you will be able to recreate those as accurately as you’d like. Any combination of tools will be allowed on a custom tab. If you like the compactness of the old UI, we are working on ways to offer various levels of customization. If you use a particular tool frequently and value efficient access, I would also recommend binding shortcuts.
Recently we added the ability to hide labels if you right click on the ribbon area. You can also hide the toolbar by double clicking tabs (we are working on the ability to auto hide so it’s manual for now). As far as padding goes, we’ll be making updates soon.
Yeah this is a known issue. Honestly we originally thought just the Plugins menu + custom tabs would suffice (I still think this is how most folks will work long term). But not having customization yet has shown how we need to improve the presentation of plugins. We still have lots of work to do! Thanks for the feedback.
Yeah this is something we’re also talking about. The “------------” is something added by the plugin dev so not much we can do about that. But group names are something we need to figure out.
Thanks for the response, and it’s super cool to see the feedback being read. Another piece of feedback is that one of the best changes that devs have needed for plugins for a long time is to merely sort them alphabetically instead of a random different order every single time Studio is started. I have probably spent several hours of combined time over several years simply looking for the correct plugin, since they always shift around.
My previous solution for this was the Quick Access toolbar, but I stopped using that after like the 7th time it randomly reset. Plugin sorting would also alleviate this issue really nicely, but I have no idea how difficult that would be (although custom tabs might solve that).
I’ve also seen a few attempts at a custom plugin toolbar (which is a plugin itself that activates other plugins) over the years, through very hacky methods. That’s how annoying this issue has been for developers with a lot of plugins.
Our first primitive implementation of custom tabs (using JSON files, no UI provided yet) will likely be out before the end of this month. Once you place a plugin in a particular tab and in a particular order, we will preserve it.
But still a fair point anywhere that we list all plugins should be a consistent order!
It’s very hard to navigate on the new studio with those tabs being in the middle, and looks very weird.
By my understanding, there will be no way to choose the current studio over the new one, so atleast some personalization options to make our layout similar to the old one would be nice.
I’m honestly not a fan of this redesign, just because of that little thing
This was brought up in the beginning too… and I am in favour of those 2 on the same top line.
The only thing that I hesitate is … if they have plans for more items in that … like the Tabs we can create … that would take up more space… and become bogged if the 2 lines were merged.
The way I see things going… is what we see (and new Devs) is the default menus.
Once we can create our own main Tabs (maybe 3 or 4) + our UI Tabs of choice…
… I’m sure we can hide the default UI / Menu Bars … & use our own UI design.
If that’s the case… we won’t have any issues later.
tbh i would just like to see less space between icons (looks like a mobile app…), and the tabs being moved on the side like the older layout. this would make it much easier to navigate.
would be nice to have the full old layout being brought back but they said it might be able to be brought back by creating custom presets (i can’t wait to see how well this works)
another nice change would be making it take less space, about the same as the old studio ui, because it kind of sucks losing some pixels from the game window.
and one last thing, would be cool to allow us to “hide” the default page layouts in favor of custom ones only, to be able to recreate the old layout
I have been developing since 2010. This is the Studio I am used to. When the Ribbon Bar first came out, I spent about two years using pirated copies of update-frozen Studio so that I didn’t have to update. One day, my life was saved, because I learned about the QAT and that Studio could be rearranged to essentially resemble that of the original “System Menu” design. I only open the Ribbon Bar tabs temporarily if I need an added tool from it, or a plugin.
This new design would absolutely destroy my workflow, and I fear the chances of needing to abandon the platform altogether if it is implemented. I have been working the same UI for 14+ years and it has never been an issue. Roblox was even smart enough to give us that QAT option (my fault I didn’t learn about it sooner) to mimic the previous Studio.
Please, I beg of you, reconsider this. Allow us to keep what we have right now. Give us the option to mimic what I am showing in my photo. I don’t want to leave this platform, but if my workflow is forced to crumble, I will have no choice.
You will be able to hide the default tabs, at a minimum. We are still talking through if it’s worth the trouble to allow customizing the tools on the defaults or simply say, “Hide them and make your own new ones.”
A part of the consideration is discoverability of new features we release. I’m hoping the new start page, which is also built in the new UI framework, will give us more options for telling you about new tools/features… a lot of creators don’t use or read DevForum, unfortunately!
Ah, I understand, it’s a bit unfortunate we won’t be able to move the tab on a side, however i’m hoping that could be done through a workaround, by making “presets” with no name maybe? pushing the visible text to the left side of the screen
I didn’t say that! We have not fully figured out all of our customization options yet. We are first focused on the ability to create new toolbars. Alignment of tabs is not out of the question.
