System Menu Deprecation

It’s so restrictive to the developers who works with a given pipeline tool set, and I want to refer ROBLOX to a video from blender I find very comparable to how things are going on soon.

12:40-27:00 Covers what I mean mainly.

I don’t know I just find these situations very similar because of the simplistic little design of Ribbon just doesn’t cut it because it can hurt productivity.

@Scottifly

Same, I can’t even play ROBLOX in general everything is so broken.

2 Likes

But what about the people actually making games? I don’t think New users are the ones making the games. As far as I can tell, the layout only appeals to the minority.

All I see are people editing the XML to look more like SystemMenu.

1 Like

What I would give to have an editor like Maya.

http://i0.wp.com/www.cgmeetup.net/home/wp-content/uploads/2015/08/Making-Maya-Easier-To-Use-5.jpg?resize=960%2C528

If you guys will be changing us over to ribbon at least consider making it a proper collaboration of both styles and give us more control over customizing our studio.

I’m pretty sure that you guys the developers to be comfortable and more importantly efficient in their workflow, and I think plenty might agree.

4 Likes

Sure, but that conversation has already been had several times in this thread. A friendly default UI is neccessary to keep new and young users engaged, and the prevailing consensus is that faster and more permanent customization is needed so that experienced devs can do their own thing.

Ya’ll should talk to nine year olds more often.

1 Like

IMO if the following is true

A smooth and powerful Studio experience is one of the best ways we can enable you all to keep creating amazing content and so if there are obstacles in your path we want to know about them.

Then removing SystemMenu for me at least will really jeopardise this.


##I am currently using…

  1. SystemMenu Default
  2. SystemMenu Modified
  3. RibbonBar Default
  4. RibbonBar Modified

0 voters

##The removal of SystemMenu will affect me/my workflow/productivity…

  1. Strongly Agree
  2. Agree
  3. Neither Agree or Disagree
  4. Disagree
  5. Strongly Disagree

0 voters

##In the future, I plan on using…

  1. SystemMenu Default
  2. SystemMenu Modified
  3. RibbonBar Default
  4. RibbonBar Modified

0 voters

1 Like

We have to go back.
Not to the SystemMenu, but to the Legacy menu. See this post for a short explanation as to why this secret third option is in fact the superior one.

1 Like

Oh jeez, all this ranting in the thread.

I’ll be honest, I used to be just like you guys - SystemMenu 4ever, ignorant to change, never gonna use it.

But once I realized that some features weren’t working correctly in SystemMenu, such as the mobile emulator, I knew that if I wanted to stay up to date with the best ROBLOX Studio functionality, I had to move onto RibbonBar.

To this day, I still think the default layout isn’t very good, which is why I made my own modification of the Ribbon Bar XML file. Switching to RibbonBar was not the end of the world. I got used to it, and it works just fine for me.

With all that said, ROBLOX really needs to make customization support a top priority.

Some things it would be nice to have would include:

  • Tabs & Groups under Tabs
  • We should be able to create, rename, or remove certain tabs.
  • Element alterations
  • Drag/Drop items.
  • Switch between textundericon and textbesideicon
  • Toggle the display of text on an icon.
  • Create dropdown lists.
  • Allow us to add an options menu to a group (the same thing being used for Material Action as Tool)
  • Theme Options (that actually look nice)
  • Allow us to scale the height of the upper menu?

Is all of this way too complicated and insane for QTitanRibbon? Probably. But at the same time, if you guys want people to like RibbonBar more than SystemMenu, it needs to be just as flexable and configurable as SystemMenu is.

11 Likes

You need to open studio via the shortcut on your desktop, then before opening a place head to Tools->Settings. There will be an option called UIdisplay, or something along those lines. Change that from SystemUi to RibbonBar, close studio and re-open it.

It may not be as complicated as you think considering ROBLOX’s ribbon is a modified MS Office ribbon, and Office 2013 allows you to configure the ribbon freely:

For instance, here I’ve created a new group of buttons in the HOME tab (I can also create new tabs):

@UristMcSparks These poll results are frightening. Only about a third of users are satisfied with the default RibbonBar layout, which is substantially less than what the default interface should see. I’d recommend bumping up the improvement of RibbonBar to a high-priority issue so that at least the majority of Studio users can be satisfied with the interface. Since Studio’s ribbon is based off of the ribbon MS Office uses, hopefully it won’t be too difficult to implement something like tab/tab content configuration which is already supported in modern versions of MS Office.

2 Likes

Here’s a nice Ribbon regression:
Ribbon incorrectly cancels a multiple object selection when the mouse leaves the window this selection happens in.
As you can see, Legacy/SystemMenu handles this scenario correctly and identically to Windows. Thread.

1 Like

This is a poll I’d like to see.

(note, vote based on your preference based on the default SystemMenu and default, unedited RibbonBar)

##If both themes had the exact same features/support, which design would you prefer

  1. SystemMenu
  2. RibbonBar

0 voters

1 Like

That poll doesn’t really make much sense because RibbonBar is pretty much the exact same thing as SystemMenu if you don’t use the ribbon and put everything in the quick access menu, bugs aside.

1 Like

Ribbon is not even close to being the same thing as SystemMenu. For one, Ribbon lacks a menu bar. My post and many others detail the many areas in which Ribbon falls short besides the bugs it introduces.

Default SystemMenu. Default RibbonBar, unedited with XML. Not sure if I can edit the poll to add that.

Putting everything in the quick access pretty much defeats the purpose of the ribbon.

  1. A menu bar
    SystemMenu’s menu bar is trivial and mostly clutter. The menus are either desolate (Window) or crammed with useless functionalities (Edit). As a previously-avid SystemMenu user, the only menu buttons I ever used were File, Insert, and Test. All of those can cleanly be combined into a single menu. SystemMenu’s menu bar is 20px of wasted space which could otherwise be a single button which doesn’t take up a whole bar, like in RibbonBar.

  2. Multiple rows
    You wouldn’t need multiple rows if SystemMenu didn’t clutter your toolbars with buttons you never use :wink:

  3. properly divided, mouse-sized icons with no wasted space
    Same story with RibbonBar

  4. Lack of tabs/titles
    You can collapse the tabs so they don’t take up any screen space

  5. Widgets that respect the OS’s current theme
    If you didn’t use an obsolete OS / theme this wouldn’t be a problem :wink:

I completely understand if you want RibbonBar to be improved – that’s awesome if you do. But what you’re spouting is nonconstructive, anti-change rambling.

3 Likes

This is essentially turning RibbonBar into a smaller SystemMenu.

Case and point. “RibbonBar is pretty much the exact same thing as SystemMenu if you don’t use the ribbon and put everything in the quick access menu, bugs aside.”

So what’s the point of enforcing the RibbonBar and that ridiculous ribbon when everyone pretty much turns it into SystemMenu? I just don’t understand this.

The ribbon isn’t being enforced – you’re free to tuck it away. Why force RibbonBar and drop SystemMenu? Because it means 1/2 the testing and no complaints that end up being an issue with an unsupported layout. On top of that, with SystemMenu developers aren’t taking advantage of new features that are supposed to help making quality games easier since those features aren’t available on their layout.

1 Like