Will Windows 9 reintroduce the classic theme?


Recommended Posts

check this out guys & gals,  classic remade for WindowBlinds by Frogboy. :)

http://www.wincustomize.com/explore/windowblinds/2957/

 

running it in windows 8.1 now.

Thanks for the link but I find this being of low quality. It is better to use real Classic theme using the hacks http://i.imgur.com/w07G3sm.png?1

It is possible to use Classic theme without disabling the DWM via hacking:

http://web.archive.org/web/20140819031246/http://forum.thinkpads.com/viewtopic.php?f=67&t=113024

I didn't say it wasn't possible . . . Anyway, what you posted is an unofficial workaround, and so is technically not supported by Microsoft.

Classic mode has regressed in quality ever since Windows Vista. It's shocking that they managed to make its UI changes work on the Aero UI layout, but what would you rather do? Shed legacy components, or keep trying to adapt ancient paradigms on modern systems?

Care to elaborate?

 

Everything regressed in quality in Windows starting from Win2000

Maybe for you, yes, but not for others. For example, I quite enjoy the Windows Aero UI present in Windows Vista and Windows 7.

Maybe for you, yes, but not for others. For example, I quite enjoy the Windows Aero UI present in Windows Vista and Windows 7.

Can u name at least 1 bug in Win2000, especially UI-related? I cannot. I know not a single bug in Win2000 at all and definitely none affected me even though I worked with the system for years.

In Win XP there were about 10-12 or so bugs and glitchess, mostly appearance-related. In Win7 there are tens, and may be hundreds, glitches and bugs are everywhere, it looks like beta software.

 

For example, I quite enjoy the Windows Aero UI present in Windows Vista and Windows 7.

 

...which is quite buggy. For instance, Clear type not working in the taskbar (works only in Classic theme). Window maximize animations are absent. And a lot of other bugs.

Can u name at least 1 bug in Win2000, especially UI-related? I cannot. I know no bugs in Win2000 at all and definitely none affected me.

In Win XP there were about 10-12 or so bugs and glitchess, mostly appearance-related. In Win7 there are tens, and may be hundreds, glitches and bugs are everywhere, it looks like beta software.

 

...which is quite buggy. For instance, Clear type not working in the taskbar (works only in Classic theme). Window maximize animations are absent. And a lot of other bugs.

Examples?  Otherwise those are empty claims.

 

Cleartype might work on classic, but it ahs tearing when moving windows.  So you call it a bug, I believe that was probably a design decision that someone forgot to take out of classic.

 

As for broken animations this (rather crappy) video is calling you out:

Can u name at least 1 bug in Win2000, especially UI-related?

I can give you a list of bugs. Mind you, they were fixed in Service Pack 4, but they still existed at one point or another.

http://support.microsoft.com/kb/327194

 

I know not a single bug in Win2000 at all and definitely none affected me even though I worked with the system for years.

Doesn't mean they did not (and do not) exist.

For instance, Clear type not working in the taskbar (works only in Classic theme). Window maximize animations are absent. And a lot of other bugs.

What purpose would maximize window animations serve? The minimize animations are to help the user discover where the window is located on the taskbar.

Do the window tearing and redrawing errors present in Windows Classic / Luna count as a 'bug' to you? http://blogs.msdn.com/b/greg_schechter/archive/2006/03/05/544314.aspx

LYdOcGH.jpg Q0sNTP2.png

OMG please yes. Or no, better yet, include a better UXtheme engine so we can customize it as much as we'd like. I loved using Luna, Classic and Vista Aero themes on Windows 7 from time to time.

  • Like 1

Care to elaborate?

On Vista/7, a lot of the new UI elements (such as the new Windows Explorer design and taskbar) don't tend to look as elegant as they do in the Aero themes. It was becoming clear that trying to adapt the Aero HIG to work in Classic was going to look unpolished.

Cleartype might work on classic, but it ahs tearing when moving windows.

 

Yes. And under Win200/XP I had no tearing in 2D. There was a checkbox in Nvidia control panel.

 

So you call it a bug, I believe that was probably a design decision that someone forgot to take out of classic.

 

Design deccision? Classic theme respects font settings (Subpixel/grayscale/no smoothing), in Aero the taskbar, menu and other elements do not. By hacking the theme file one can disable the smoothing in the taskbar, otherwise u always get grayscale irrespective of system settings. There is no possibility to enable ClearType on the taskbar other than using Classic theme.

As for broken animations this (rather crappy) video is calling you out:

 

I am not about animation speed. There is jus NO animation of maximizing and restoring(from max) a window under Aero.

What purpose would maximize window animations serve? The minimize animations are to help the user discover where the window is located on the taskbar.

 

Okay. There is no restore from max animation either. It can help to locate the application's window. But the point is that the interface is totally inconsistent and unfinished.

 

Do the window tearing and redrawing errors present in Windows Classic / Luna count as a 'bug' to you

 

I w2as asking about Windows 2000. I know that XP is more buggy than Win 2000, especially UI and theme-wise.

OMG please yes. Or no, better yet, include a better UXtheme engine so we can customize it as much as we'd like. I loved using Luna, Classic and Vista Aero themes on Windows 7 from time to time.

It seems that current enguine used in Windows 8 had been designed for just one theme and not to be changed. That's perhaps the reason why they so much simplified the theme in W8: they wanted a new theme, but this flat design is maximum that they could get out of the very regid engine.

Ugh - classic theme is hideous.

 

And, off-topic, but LOL at Andrea Borman's video. Oh God, the horrible memories from August 2012!

On Vista/7, a lot of the new UI elements (such as the new Windows Explorer design and taskbar) don't tend to look as elegant as they do in the Aero themes. It was becoming clear that trying to adapt the Aero HIG to work in Classic was going to look unpolished.

I agree with this. Also they introduced some other bugs to the Classic theme. Black point on the first tab in the tabbed dialogs, wrong shadow on the slider, no 3D (and any other) borders around icon views in Explorer, too thick Command Bar buttons, different styles of pressed and not pressed combo box in Explorer's address bar (and doubbled 3D borders when pressed), garbage on the taskbar buttons during the windows restore animations, the distance to the taskbar handle grows if to switch themes and then return to Classic, the appearance colors dialog becomes smaller each time one changes the window buttons size so at one point even the OK button becomes unaccessible (maybe this happens in Aero as well), different fonts in different dialogs  etc.

 

But still. I consider the Aero bugs more visible (no Clear type here and there, missing animations, some dialogs appearing in Classic theme, even system ones, white point in the desktop's corner). So that actually any theme under Win7 is buggy.

 

There are also theme-independent bugs, like corrupted icons, inscriptions not fitting in their space etc.

Okay. There is no restore from max animation either. It can help to locate the application's window. But the point is that the interface is totally inconsistent and unfinished.

Might I suggest that the only reason the UI in Windows 2000 is consistent is because it is literally built on Microsoft's previous UI efforts; icons from Windows 95 don't conflict with the theme in Windows 2000, for example. The same is not true with older icons and Windows XP, which is supposed to be bright, cheerful, and colorful.

I w2as asking about Windows 2000. I know that XP is more buggy than Win 2000, especially UI and theme-wise.

These visual artifacts also occur in Windows 2000. This is because the operating system does not have a compositing window manager (present in Windows Vista and later).

icons from Windows 95 don't conflict with the theme in Windows 2000, for example.

 

Win95 used different icons than Win2000. I like the icons from MS Plus for Win95 the most of all till this day, but the default W95 icons the least. The WinXP used the cartoonish style I (moderately) disliked. But a glitch with Win XP was that it still used the Luna artword in Classic theme (those green round buttons in the Explorer, for instance), this is not directly related to the file icon theme, which was more or less compatible with the Classic theme though.

These visual artifacts also occur in Windows 2000.

 

What exactly artifacts do u mean? There was no screen tearing (everywhere, including when moving Windows) at least when using Win2000/XP with Nvidia+D-Sub connector (as opposed to DVI). It seems Microsoft removed this feature from Win7 so to force everybody who dislikes tearing to Aero. Four years ago when I was using XP I had no tearing. Then I switched to Linux briefly, and now I use Win7 with Classic theme and have heavy tearing.

You realize you're hurting your system performance by doing that, right?

It is quite doubtful. Anyway I know no way to enable the DWM while remaining under Classic theme in Win7. There are Aero themes that emulate the Classic theme, but so far the disadvantages and bugs in Aero (lack of customizability, not working ClearType in Explorer etc) outweigh the advantage of no tearing. On the other hand, it is possible to use Classic theme without quitting DWM under Windows 8 via a hack, but this has its own disadwantages. That's why my next OS most likely will be Win 2000.

Win95 used different icons than Win2000.

I'm well aware of that. My point was that they do not conflict with the style set forth by Windows 2000; everything is classic. Not that there is anything wrong with that, mind you.

 

What exactly artifacts do u mean? There was no screen tearing (everywhere, including when moving Windows) at least when using Win2000/XP with Nvidia+D-Sub connector (as opposed to DVI). It seems Microsoft removed this feature from Win7 so to force everybody who dislikes tearing to Aero. Four years ago when I was using XP I had no tearing. Then I switched to Linux briefly, and now I use Win7 with Classic theme and have heavy tearing.

I am referring to the artifacts present in the images that I previously posted. It is bizarre that in your previous post you indirectly used the artifacts to support your belief that Windows XP is 'buggy,' yet you later state that you did not experience them at all while using Windows XP.

I am referring to the artifacts present in the images that I previously posted. It is bizarre that in your previous post you indirectly used the artifacts to support your belief that Windows XP is 'buggy,' yet you later state that you did not experience them at all while using Windows XP.

Where I said XP had tearing? Where I said so "indirectly"? I was referring to a lot of other bugs and glitches.

Where I said XP had tearing? Where I said so "indirectly"? I was referring to a lot of other bugs and glitches.

I did not state that you wrote about tearing in Windows XP. It was my assumption that you used the tearing as an example of 'bugs and glitches' present in Windows XP, because when I mentioned the tearing, you wrote . . .

 

I w2as asking about Windows 2000. I know that XP is more buggy than Win 2000, especially UI and theme-wise.

And then when I mentioned the artifacts (tearing) in Windows 2000 . . .

 

What exactly artifacts do u mean? There was no screen tearing (everywhere, including when moving Windows) at least when using Win2000/XP with Nvidia+D-Sub connector (as opposed to DVI). It seems Microsoft removed this feature from Win7 so to force everybody who dislikes tearing to Aero. Four years ago when I was using XP I had no tearing. Then I switched to Linux briefly, and now I use Win7 with Classic theme and have heavy tearing.

OMG please yes. Or no, better yet, include a better UXtheme engine so we can customize it as much as we'd like. I loved using Luna, Classic and Vista Aero themes on Windows 7 from time to time.

Theming of windows 8 is easier then 7, we can enable aero and enable/disable blur, make the border width very small etc.

It's just a matter of using the right software and themes.

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

    • No registered users viewing this page.
  • Posts

    • My father still uses a programme written in dbase3. Still manages to work with a little help from dosbox. 
    • Microsoft hides these secret Windows 11 performance boost settings available on every PC by Sayan Sen Windows enthusiasts often look for ways to extract as much performance out of their systems as possible, and it's often the case that they try and do so while trying to minimize the heat and power consumption. This is especially relevant in the case of mobile Windows PCs since laptops and notebooks tend to get hot and management of that heat and power is harder in such a form factor. As such users often turn to techniques like under-volting which can be used to squeeze out the maximum capabilities of a chip while also maintaining lowered power levels. There are official apps from AMD and Intel with the likes of Ryzen Master and XTU (Extreme Tuning Utility). While these are quite handy, most enthusiasts probably prefer to dig into the BIOS and play around with settings there like Curve Optimizer on Ryzen, which lets users set various frequency-voltage scaling values. These are essentially called P-States. If you are not familiar with them, Processor Power Management is done through Advanced Configuration and Power Interface (ACPI) P-states and C-states. While P-states or performance pwoer states handle CPU voltage-frequency scaling, C-states deal with CPU sleep states so that some of the CPU functions, which are not necessary at that moment, can be disabled. The P-states and C-states work together to make the processor run more efficiently. It helps the OS and apps determine which cores can be parked and which should be boosted. Of course not every user is an enthusiast or knows the technicalities and integrities of how things like overclocking or undervolting work. Thankfully for them Windows itself offers something pretty cool, though it is hidden by default on all systems. By default, Windows only has two P-States, "Minimum Processor State" and "Maximum Processor State." However, this can be changed with a Registry trick to expand the options under a secret "Processor performance boost mode" dropdown. This essentially enables the HWP or hardware P-States available on a device, and these are not controlled just by the OS itself as the underlying hardware gets involved too. In total there are five Processor Performance Boost Mode profiles that control how Windows requests and allows CPU turbo/boost behavior under the different power policies. They are: Disabled: In this mode, processor boosting is effectively turned off. The CPU will avoid entering turbo or boost frequencies and instead operate closer to its base frequency ceiling. This can significantly reduce power consumption and heat output, but at the cost of reduced burst performance and responsiveness in short workloads. Enabled: This is the standard behavior where boost functionality is allowed under normal conditions. The processor can opportunistically increase frequency when workload demands it, balancing performance gains with power and thermal constraints as managed by the system. Aggressive: Aggressive mode favors performance more heavily, allowing the CPU to enter higher boost states more readily and sustain them longer. This should in theory improve responsiveness under bursty or heavy workloads but increases power draw and thermal output compared to the default enabled behavior. Efficient Enabled: This mode still allows boosting, but with a stronger bias toward energy efficiency. The system attempts to use boost more selectively, avoiding unnecessary frequency spikes when the performance gain is marginal. Efficient Aggressive: This is a hybrid approach where boost is still performance-responsive, but the system continuously weighs efficiency more heavily than in Aggressive mode. It aims to deliver noticeable performance improvements while reducing wasted power in less demanding scenarios. Here's how to enable the Processor performance boost mode: Open Registry Editor: Press Win+R, type regedit, and click OK. Go to: HKLM\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\54533251-82be-4824-96c1-47b60b740d00\be337238-0d82-4146-a960-4f3749d470c7 (where HKLM stands for HKEY_LOCAL_MACHINE_) Modify the value of Attributes from 1 to 2 (you can find modify option by right-clicking) After that, exit Registry, you should now be able to see the new "Processor performance boost mode" dropdown menu: As you can see there are now five new P-States or CPPC states or power profile available that help define the boost mode processor setting on your PC. Wrapping it up here's a quick run-down of the settings as defined by Microsoft itself. Setting Description Disabled The corresponding P-state-based behaviour is disabled. Collaborative Processor Performance Control (CPPC) behaviour is disabled. Enabled The corresponding P-state-based behaviour is enabled. CPPC behaviour is Efficient Enabled. Aggressive The corresponding P-state-based behaviour is enabled. CPPC behaviour is Aggressive. Efficient Enabled The corresponding P-state-based behaviour is Efficient. CPPC behaviour is Efficient Enabled. Efficient Aggressive The corresponding P-state-based behaviour is Efficient. CPPC behaviour is Aggressive. Aggressive At Guaranteed Windows calculates the desired extra performance above the guaranteed performance level, and asks the processor to deliver that specific performance level. Efficient Aggressive At Guaranteed Windows always asks the processor to deliver the highest possible performance above the guaranteed performance level. In the next part we shall be comparing these settings to explore how much of a benefit or regression they can provide in terms of performance and power efficiency. If you decide to change the values on your system and are experiencing problems like crashes or an overheating PC, make sure to revert the steps back to the original state.
    • I think he means you haven't reviewed previous UFC games. Of course it doesn't matter... Every time you just report on something that involves the President even if just simply what happened you guys usually get accused of being anti-Trump. We live in fun times.
  • Recent Achievements

    • One Month Later
      Leroy Jethro Gibbs earned a badge
      One Month Later
    • Conversation Starter
      flexorcist earned a badge
      Conversation Starter
    • One Month Later
      AndreaB earned a badge
      One Month Later
    • One Month Later
      agatameier earned a badge
      One Month Later
    • Week One Done
      agatameier earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      518
    2. 2
      +Edouard
      198
    3. 3
      PsYcHoKiLLa
      147
    4. 4
      ATLien_0
      93
    5. 5
      Steven P.
      77
  • Tell a friend

    Love Neowin? Tell a friend!