Recommended Posts

It doesn't take up half the window... but past your exaggerations -

It's primarily there to give more visibility to all the commands, and to make it easier and more obvious to use them. Microsoft found that outside of power users, people were wanting to use tools that already existed, but they didn't know they existed because they were hidden in random boxes / menus / tabs etc. With the ribbon, they can surface a lot more options in a single area, whilst still giving prominence to each individual item. If you think it's big, just minimise it. Most users will appreciate how easy it makes using explorer now. It does greatly accelerate a few tasks (copy path & delete permanently are certainly enough for power users to appreciate being exposed)

You know i understand your point.

But its weird when MS teach devs to only show 3 4 buttons in their Metro apps and hide the rest under the 3 dot menu so its clean.

I understand they cant do the same for Desktop. They are just scared people will stick to Win7 if they change the UI of desktop to metro.

It doesn't take up half the window... but past your exaggerations -

I'm sorry, about one fourth of the window.

It's primarily there to give more visibility to all the commands, and to make it easier and more obvious to use them. Microsoft found that outside of power users, people were wanting to use tools that already existed, but they didn't know they existed because they were hidden in random boxes / menus / tabs etc. With the ribbon, they can surface a lot more options in a single area, whilst still giving prominence to each individual item. If you think it's big, just minimise it. Most users will appreciate how easy it makes using explorer now. It does greatly accelerate a few tasks (copy path & delete permanently are certainly enough for power users to appreciate being exposed). Heck, in the ribbon and it's major tabs, there are over 60 exposed commands for Windows explorer to everyone to see, use and understand thanks to it's tooltips (which also handily expose the keyboard shortcuts in them too). That's a lot more commands than Windows 7 exposes by default.

I understand the idea behind the Ribbon, however to me it's clear that it too can become just as messy and crowded as any conventional menu can turn out. The current execution is just a screaming mess of differently sized icons and text that takes away a lot of focus of the actual content. I've come to the conclusion though that some people just love over-crowded interfaces because it makes them feel like a power user. Beyond that any of the new tasks you describe can be housed inside a menu bar or action button as well. You don't need a Ribbon for that.

I'm sorry, about one fourth of the window.

I understand the idea behind the Ribbon, however to me it's clear that it too can become just as messy and crowded as any conventional menu can turn out. The current execution is just a screaming mess of differently sized icons and text that takes away a lot of focus of the actual content. I've come to the conclusion though that some people just love over-crowded interfaces because it makes them feel like a power user. Beyond that any of the new tasks you describe can be housed inside a menu bar or action button as well. You don't need a Ribbon for that.

Though that's the problem, you're suggesting hiding them away inside a menu. Microsoft wants to expose options, not hide them away again where people might not find them :p They're also sized based on how commonly used those tasks are - most commonly used tasks get full sized icons, whereas less commonly used get normal sized buttons. In the basic sense - here are your main options, and here are some secondary options.

Though that's the problem, you're suggesting hiding them away inside a menu. Microsoft wants to expose options, not hide them away again where people might not find them :p They're also sized based on how commonly used those tasks are - most commonly used tasks get full sized icons, whereas less commonly used get normal sized buttons. In the basic sense - here are your main options, and here are some secondary options.

Minimizing the Ribbon isn't considered hiding them away? :p Most of the functions are just as unexposed as they would be inside a menu simply because of the fact the Ribbon has the ability to overflow both vertically and horizontally. Not to mention the fact there can be multiple tabs. The only functions that are better exposed compared to a traditional menu or action button are the ones that are visible on the first tab and aren't being pushed away to the overflow areas. Are you really going to try to convince me move, copy, paste, delete, rename, new folder, select all etc. need that kind of exposure...? :rolleyes: Honestly, on paper the Ribbon is a cool idea but when you really start thinking about these things it makes less and less sense, especially in Windows Explorer.

To be frank Johnny, which self-respecting power-user is going to press a button to move a file and hit another to paste? You're not much of a geek if you don't know those basic keyboard shortcuts. :laugh:

Minimizing the Ribbon isn't considered hiding them away? :p

And honestly Johnny, which self-respecting power-user is going to press a button to move a file and hit another to paste? :laugh:

Sure minimising is hiding them away, if you want to minimise it :p But even then, when you open they menu, options are given far more breathing room.

Eh, there's a lot of times where I'm just not using my keyboard so I'd rather click. Either way, even if you're using your keyboard, you're still pressing a button combo to copy and another to paste :p Power users used button combos to take the place of options that weren't immediately accessible to save time... but with the ribbon, a lot of them are more immediately available, so clicking becomes a slightly more attractive option for some, especially during lazy days. Course not everyone will like it, but the the general scheme of *all* computer users, the majority will certainly find it a handy addition.

Sure minimising is hiding them away, if you want to minimise it :p [...]

I've edited my post to explain more about what I meant.

but with the ribbon, a lot of them are more immediately available, so clicking becomes a slightly more attractive option for some, especially during lazy days.

On my Mac that just translates to two fingers for right-click > select command. :p

Are you randomly hitting that reply button without knowing/understanding what it is you're replying to, drunk, visually impaired or just really really dense? I can't tell which one of the four is the case.

Sorry, I apologise. My mind must have gone crazy when looking at that screenshot. Comment retracted.

The ribbon is not bad, but do find it ironic that in Vista and Windows 7 Microsoft simplified the explorer toolbar and made it really minimalistic, yet it was still enough to find all the commands I really needed. With the Ribbon it almost feels like too much for explorer at least from what I have tried on Windows 8.

Exactly.

The did great with Windows 7. They are taking a step back with Ribbon IMO.

but again. its good for touch. Very good for touch. But make it pretty please.

Also allow us to customize it :( ... else i wont be able to theme for windows 8 becaue i wont theme if the ribbon part will remain default.

Sure minimising is hiding them away, if you want to minimise it :p But even then, when you open they menu, options are given far more breathing room.

You can achieve the exact same thing inside a menu... As far as I know there's no law saying a menu has to look as seen below. My main issue with the Ribbon is dat it makes the window extremely top heavy and much bigger than it has to be. It almost starts to rival the content space which can't be good. My second issue is that while you can minimize it you have to constantly click it open and click it to close: It doesn't minimize automatically after clicking something or clicking somewhere outside the Ribbon, unlike a menu.

post-128385-0-55055300-1328276365.png

Someone's got to make the Ribbon themable... & make this the 1st theme!

thank u :D

well @ MASTER260 : i have another idea in my head. But for that we will have to get rid of Glass. . .

The thing is..

with Metro. Now glass hardly makes sense as part of Windows UI. They need to tone it down to atleast balance it with Metro if not Go that way.

MS: my metro desktop app concepts has a searchbar (no need to go to start screen to search for legacy apps, meaning no break in productivity). Also no start button needed, as its already in the charms menu. And Its METRO! (no ribbon ofcourse!) simple menus FTW!

Realising that Ribbon is here to stay. I challanged myself to make a Ribbon UI that is consistent. And beautiful. (also something mature)

I know you are talking about the ribbon in particular, but you were saying you want it like metro. But I personally feel metro is not beautiful, infact it's very plane jane. It's also not very mature, looks very kiddy in my opinion.

And as usual Zain makes everything so much better than Microsoft, nice one!^^ Though I agree a bit color wouldn't hurt >.<

I would suggest maybe try to add color relevant to the task, like green-ish for the clipboard and yellow-ish for organizing for example. Oh and another suggestion, maybe try to add Aero to the minimized ribbon and see how it looks :)

i like your concepts but how about this idea, if a user were to hover over an icon in the ribbon bar the icon itself would become a full colour icon and revert back when the cursor is moved from the icon.

ok guys.. the thing is..

ppl here think this is low quality linex distro like work.

The thing is i was going for the style that matches the conjusted design of ribbon and windows explorer. the direction i took suits it well..

but i said here that i was only skinning the present situation of windows 8.

Here is what i imagine a windows explorer with something like ribbon can look like if i get to play around with my rules.

My rules. My style. Metroish simplicity. But with little styles to give it a touch of our loved GUI from today. Ribbon options. But everything super sleek and sexy.

How about this? (please click to view fullsize)

post-285248-0-72488000-1328384984_thumb.

post-285248-0-80318000-1328384997_thumb.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • The machines are starting to fight back any way they can.
    • No news articles about the Arch Linux repo being majorly infected with malware?!?
    • Waymo recalls self-driving software after cars enter closed freeway work zones by Paul Hill Waymo, the self-driving car maker owned by Alphabet – the parent company of Google –, has recalled some of its fifth-generation Automated Driving Systems (ADS). It did so after some of its cars drove through closed construction zones. According to the National Highway Traffic Safety Administration (NHTSA), the affected vehicles were capable of driving through a closed freeway construction zone and continuing to drive at speed. The listing on the NHTSA website says that Waymo is currently developing a solution to fix this issue, but in the meantime, freeway driving is being restricted. Waymo will update its ADS software so that vehicles can detect when they can avoid entering construction zones. According to the Safety Recall Report, on April 20, 2026, Waymo’s Field Safety Committee began meetings reviewing an event from April 11, 2026, and five events from April 19, 2026, where Waymo’s autonomous vehicles didn’t recognize and drove past ramp closure signs into the pre-planned freeway construction zones. This took place in Phoenix, Arizona. Separately, on May 18, 2026, seven Waymo vehicles entered freeway lanes with active construction in the San Francisco Bay Area by driving between cones that were placed to show the lane was closed. On the back of both of these events, Waymo restricted freeway driving until it could address the issue. In June, Waymo’s Safety Board reviewed the issue and additional information related to ADS performances around construction zones; then, as a result, it decided to conduct a recall. This development is not good for Waymo as it adds to a growing list of technical hiccups its cars have experienced. Ultimately, it will lead to more scrutiny from lawmakers around the world who will be more cautious about letting autonomous vehicles on their roads without tighter regulation. For readers in areas where Waymo operates, does this news make you more wary about stepping into one of these vehicles?
    • I'm still on Windows 10 22H2 because I didn't want to deal with all the issues in Windows 11, so I waited almost a week before installing the latest Patch Tuesday update (KB5094127), I went ahead and did it, and it was a huge mistake—ever since then, my File Explorer has seen a performance drop of about 30% when transferring large files... Once again, Microsoft has outdone itself! This update cannot be uninstalled, either through the Control Panel (via Settings) or by accessing Advanced Startup Options. The only possible alternative would be to use system restore points, but I’d have to reinstall all app and driver updates (and there’s no guarantee it would work). Or there’s the “nuclear option” of a in-place repair without losing files or apps, but even then, all my customizations would be lost! Microsoft just can’t help but mess everything up! Way to go, Microsoft! But I still don’t want your c****y Windows 11!
    • Microsoft: Windows 11 could finally solve a major issue across AMD, Nvidia, and Intel GPUs by Sayan Sen While Microsoft has been trying to improve it, Windows 11 is definitely not flawless, as even today some issues are taking a year to publicly acknowledge. However, one area of trouble that may finally see much better results soon is graphics driver crashes. Work on graphics driver timeouts, also called Timeout and Detection Recovery (TDR), is not new as the latest WDDM 3.2 also has specific improvements regarding it. Windows Display Driver Model (WDDM) version 3.2 is supported on Windows 11 24H2 and 25H2. However, with the upcoming version 26H2, TDR crash diagnosis could go to the next level as Microsoft is introducing a new DirectX 12 API feature called "DirectX Dump Files". Similar to how system memory dump files work when a system crashes or freezes or encounters any such major issue, DirectX Dump Files (DDF) will essentially record a snapshot of the GPU execution right at the moment a graphics-related crash or hang or freeze occurs, so that developers can better understand and diagnoze these TDR and timeout detection errors. The dump will be available as a .dxdmp file for analysis and it will be a comprehensive dump file generated with detailed insights about the hardware, drivers, Windows, as well as the affected application. This should be another welcome change in this department. Earlier at GDC 2026, when the technology was first debuted, Microsoft had shared more details regarding it. The company had explained how DDF is designed to gather data from every layer of the graphics stack into a single file, eliminating the need for developers to manually correlate logs from multiple tools. As mentioned above, the dump can contain a lot of useful details like GPU hardware state information such as register values, shader program counters, page fault virtual addresses, shader memory data, and command buffers. Alongside that, it also captures DirectX runtime and kernel information, including D3D objects, pipeline state objects, device error data, adapter details, and CPU call stacks. Microsoft says the feature has been built around two primary use cases: retail device removals and local device removals. The former allows developers to collect crash information from end users' systems in the field, while the latter helps QA teams and developers investigate issues on test machines. Developers will also be able to include up to 2 MB of custom application data through new D3D12 APIs, providing additional context for troubleshooting. In addition, Microsoft is introducing three dump collection modes ranging from zero-overhead capture, which has no runtime performance impact on supported hardware, to higher-detail modes that collect more vendor-specific debugging data. On compatible Tier 2 hardware, zero-overhead dumps will be enabled by default, meaning developers may begin receiving useful crash diagnostics without making any code changes. The table below explains the three tiers: Tier Description NO_OVERHEAD Enables crash capture with no runtime cost and is suitable for broad deployment MEDIUM_OVERHEAD Provides a balance, capturing additional diagnostic data with moderate impact HIGH_OVERHEAD Collects the most detailed GPU and driver state available, enabling deeper investigation at the cost of higher runtime overhead In terms of availability, the company expects broader release to be around the fall of 2026, which should be right around the time when Windows 11 version 26H2 lands. Right now, DirectX Dump Files are available as a preview and currently, only AMD has the compatible AgilitySDK Developer Preview driver version 26.10.07.02. You can find the official announcement post here on Microsoft's website.
  • Recent Achievements

    • Week One Done
      Eurosoft10 earned a badge
      Week One Done
    • One Month Later
      Eurosoft10 earned a badge
      One Month Later
    • One Year In
      Skeet Campbell earned a badge
      One Year In
    • One Month Later
      Sharbel earned a badge
      One Month Later
    • First Post
      BizSAR earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      599
    2. 2
      +Edouard
      190
    3. 3
      PsYcHoKiLLa
      79
    4. 4
      Michael Scrip
      77
    5. 5
      Steven P.
      70
  • Tell a friend

    Love Neowin? Tell a friend!