In my opinion JSON is better for things like that. Not a big fan of these
This is significantly going to improve my workflow. Does anyone know if we have a release date for the next gen studio UI?
That’s a weird one! I’m going to guess because we don’t have an icon for it.
Yeah I’ve always liked the attribute/mark up system for creating properties and custom inspectors. Maybe some day!
Our next goal is to switch from totally opt-in to more of an opt-out (it will still be a Beta feature but for most people it will default to true). To get there, we need all of the play/test controls in and we’d like to get the customization UI at least started.
After that, we have a ton of tasks to do before we can make it the new default. Our ambitious goal is to get there in the summer 2025, It will be tough but possible!
I thought we covered most of these in the original post, but here’s another example:
{
"Name": "My Stuff",
"Controls": [
{
"Id": "Autoscale",
"Type": "IconButton",
"Action": {
"PluginId": "1496745047",
"DataModel": "Edit",
"Category": "Actions",
"PluginType": "Cloud",
"ItemId": "AutoScale Lite_Scale Text"
}
},
{
"Size":"Large",
"Type":"Separator"
},
{
"Id": "MatMgr",
"Type": "IconButton",
"Action": {
"PluginId": "MaterialManager",
"DataModel": "Standalone",
"Category": "Actions",
"ItemId": "Toggle"
}
}
]
}
We’ve got a long list of tasks and this is on it. We are using a stylesheet driven UI so tweaks should be fairly simple. The design team is working on getting the global design system specified so there’s not much point in us making temporary changes when we know the “official” design is coming sooner than later.
We also want to investigate pushing UI elements into the window title bar but that will require some prototyping. Right now we are spending most of our time getting the complete play test controls built/working and starting on the UI for customization.
If you modify the default tabs we ship with, they will get stomped by any updates. This is why the custom tabs directory is in the same user space as plugins (see OP for details)
You will be able to hide default tabs once we get the “Manage Tabs” UI built.
I’ve heard the overhauled Explorer could be in Beta before the end of the year.
Our goal is by the time this switches over to the default, most of the primary UI will be on an updated, shared color palette and style system.
We aren’t opposed to allowing overriding and customization of the colors, but we’ve got to get on a modern styling and color token system first.
Did you see the ControlTypes.luau
that was attached in the OP? That’s all we have right now.
Yeah I just realized from another post this action hasn’t been moved over to the new system. I will check with the team on if we can get it migrated!
Great to hear, hoping all goes well for that.
On another note, I’ve been getting this very annoying bug with the ribbon tooltips. They appear normally, but half the time they just start jiggling oddly left and right (happens near end of clip).
It also fails to disappear when not hovering over it at times, which causes huge lag spikes in studio.
I think I’ve seen someone talk about this before but it’s been a long while since then and I was wondering if any fixes are planned?
also appears through window
Yes. The layout system will get some much needed love next year.
Right now if you double click the tabs they will collapse/expand. We have a nicer “floating” version in the works.
Talking about this, I think the plugins tab needs some work and they are the only reason I can’t use this :(( Another thing, what can I really add in custom tabs?
Another thing that annoys me is that the Material icon opens the Material Manager window instead of that tiny drop down window.
the json i used was inside of the customtabs directory
Hmm. Alright, thank you I suppose. I wish it was a schema so I could validate it better but I suppose writing one is a low priority, haha.