Recommended Posts

They're bundled inside iTunes.rsrc. Why? iTunes had to carry all of those interface elements inside its own package contents because Mac OS 9 didn't feature Aqua. Absolutely clueless why it's still that way today. No idea what the role of those new matte scrollbars are in the first place.

Given that you didn't even know that iTunes was still lugging around it's widget graphics I'd say there's little real harm in it.

Also consider that it would take some time to re-write iTunes to use the resources provided by the operating system and that it does a lot of custom drawing, notably in the store, there's some reason not to. Add to that the need to support Windows and older versions of Mac OS X which don't provide the same UI elements that 10.6 does it begins to make even less sense if cross-platfrom UI consistency is a primary goal.

Given that you didn't even know that iTunes was still lugging around it's widget graphics I'd say there's little real harm in it.

What do you mean? I've known that for quite some time now.

Also consider that it would take some time to re-write iTunes to use the resources provided by the operating system and that it does a lot of custom drawing, notably in the store, there's some reason not to. Add to that the need to support Windows and older versions of Mac OS X which don't provide the same UI elements that 10.6 does it begins to make even less sense if cross-platfrom UI consistency is a primary goal.

That still doesn't really explain the need for a custom GUI that differs from default Aqua. Things like scroll bars, checkboxes etc. remained largely unchanged since Mac OS X' initial version.

Eventually I see Apple adopting a more native appearance on Windows, like they did with Safari, and dropping Mac OS X 10.4 Tiger support.

Edited by .Neo
What do you mean? I've known that for quite some time now.

Whether or not images for iTunes are loaded from within the bundle or from without - you wouldn't notice a difference.

That still doesn't really explain the need for a custom GUI that differs from default Aqua. Things like scroll bars, checkboxes etc. remained largely unchanged since Mac OS X' initial version.

Apple doesn't have any major commitment to the default widgets. Take a list of all the software they ship apart from OS X and you'll see the majority doesn't use bog-standard widgets.

Bolt on Apple's apparent desire to have iTunes stand-out from the crowd and I think this will be the case for some time to come. Apple seems to ship new versions of iTunes roughly once a year. The current version is coming up on 10-months old and 10.6 is due to ship in 2 months.

My money is on no significant platform changes (ie: 64-bit re-write using Cocoa, dropping PowerPC support, dropping support for Windows 5 products) until the version after next at the earliest.

Eventually I see Apple adopting a more native appearance on Windows, like they did with Safari, and dropping Mac OS X 10.4 Tiger support.

I think Apple puts too much stock in the brand-image of iTunes to make a sweeping change to native UI. Changes will be slow & gradual spanning years. I wouldn't be surprised to see them continue the whole custom UI thing they've been doing for 10 years.

I also think there's some unwritten law that media players must not use standard controls under any circumstances. Has any major media player ever used them? ;

Whether or not images for iTunes are loaded from within the bundle or from without - you wouldn't notice a difference.

If all images and resources were exactly copied, unfortunately that is not the case today. Of course this is a choice Apple made rather than a technical limitation.

Bolt on Apple's apparent desire to have iTunes stand-out from the crowd and I think this will be the case for some time to come. Apple seems to ship new versions of iTunes roughly once a year. The current version is coming up on 10-months old and 10.6 is due to ship in 2 months.

My money is on no significant platform changes (ie: 64-bit re-write using Cocoa, dropping PowerPC support, dropping support for Windows 5 products) until the version after next at the earliest.

iTunes has always been an indication of what was about to happen to Aqua in the next mayor Mac OS X version. Like a public testing ground for interfaces. Back in the Jaguar days iTunes suddenly traded its Aqua-blob buttons for the flat plastic ones: Panther applied this system-wide. On Tiger we saw the appearance of the dark unified toolbar style (multiple revisions and button types) later adopted by Leopard. The only thing so far that doesn't seem to make it system-wide are those matte Aqua replacements (scroll bars, checkboxes etc.). We haven't really seen this before, at least not to this extent.

It remains to be seen what changes Snow Leopard will bring once it hits GM and what iTunes 9 will be like. If iTunes 8 is still around once Snow Leopard is completed and the new iPods have been released, the only interface tweaks we'll see are probably the min/max/close widgets.

I also think there's some unwritten law that media players must not use standard controls under any circumstances. Has any major media player ever used them? ;

iTunes and QuickTime more or less faded in quite nicely with Mac OS X' default look up until Tiger (for iTunes) and Snow Leopard (for QuickTime). On Windows that's a totally different story. But then again there is no such thing as consistency in Microsoft Land. ;)

The only thing that strikes me as odd is that the matte Aqua replacements are starting to make it to more and more Apple applications, just not Mac OS X itself.

Edited by .Neo

There won't be any significant changes to Snow Leopard's GUI. Anyone who thinks otherwise is missing the point of Snow Leopard entirely. It's meant to be Leopard just refined and polished. So its GUI is polished, not changed. Anyone using it knows many of the GUI has been polished ever so slightly, from centering the finder arrows, to placing the buttons equally apart, making aqua a little brighter, smoother. 10.7 is more likely to have more drastic changes. Snow Leopard won't. If you think it will, you will be let down.

There won't be any significant changes to Snow Leopard's GUI. Anyone who thinks otherwise is missing the point of Snow Leopard entirely. It's meant to be Leopard just refined and polished. So its GUI is polished, not changed. Anyone using it knows many of the GUI has been polished ever so slightly, from centering the finder arrows, to placing the buttons equally apart, making aqua a little brighter, smoother. 10.7 is more likely to have more drastic changes. Snow Leopard won't. If you think it will, you will be let down.

I'd call Black menus/New Quicktime graphics/controls significant GUI changes.

I could see them springing a new theme, maybe not new UI elements or a redesign throughout the OS, but unifying the GUI to a darker tone could happen yet.

They need to do something, these different GUI elements scattered throughout the OS is getting really aggravating. Perhaps resolution independence will shimmy it's way in, as these dark simple gradients could easily be vectorized.

I'd say they have a month or less to wrap up development and get the GM to packagers. And at that point we'd probably end up with a late September release.

So really... there won't be any *massive* changes to how the OS looks, and I doubt even resolution independence will come on by default.

I'd say they have a month or less to wrap up development and get the GM to packagers. And at that point we'd probably end up with a late September release.

So really... there won't be any *massive* changes to how the OS looks, and I doubt even resolution independence will come on by default.

Well visual changes have happened in as little as just over a week ago.

Apple's running a little late with the new seed (was averaging once a week).

Perhaps there are some surprises in store....

I'd say they have a month or less to wrap up development and get the GM to packagers. And at that point we'd probably end up with a late September release.

So really... there won't be any *massive* changes to how the OS looks, and I doubt even resolution independence will come on by default.

These changes came in relatively late as well. They might have the entire package of files waiting in their lab waiting to be implemented in a public build. In Tiger they didn't settle on the Menu Bar appearance until the few very last builds, with Leopard same thing applied to the 2D Dock and Menu Bar transparency.

Personally I'm not expecting a whole theme change at this stage either, but like I said some of the redesigned elements seen in the Dock and QuickTime X might make it into other areas as well.

Yeah, some bits in their applications could happen. But universal window chromes will stay the same, because I imagine many developers have Snow Leopard-ready software designed and ready to go based on the current feel of the OS.

Yeah, some bits in their applications could happen. But universal window chromes will stay the same, because I imagine many developers have Snow Leopard-ready software designed and ready to go based on the current feel of the OS.

I agree that the main toolbar and window elements will stay the same, but elements such as scrollbars, buttons, and system wide menu changes could appear - as they don't really affect the overall look of a program.

The current mesh of icons/buttons on toolbars would cause icons to look extremely bright/contrasty on a glossy black background. And you can't really go asking dev's to change their icons to glyphs in just a few weeks to release.

EDIT: Well you could, as they have made devs port over their code several times in the past :D

Edited by Binary

I still gotta disagree with you Binary. While the changes are definitely noticeable they are limited to their respective applications. Quicktime X is a new application. New icon, new interface. While they are significant its changes aren't seen anywhere else. The only other app to get a facelift is the dock, the black menus match Stack's Grid view and 2D dock perfectly. Something that should have been done in the first place. However you don't see them changing the menubar's menus or the standard CTRL+Click menus because it doesn't tie in with anything.

I consider significant changes something that is system wide, across all apps. So far we haven't had that. Sure a few minor tweaks here and there but nothing compared to the Dock/Quicktime changes. I stand by my comment before with no major changes happening in this version. 10.7 is another story. Think about what Snow Leopard is, it's not an overhaul, its a second edition if anything. Apple doesn't want it to look drastically different, they want it to look the same, just more polished. 10.7 they will need to make more drastic changes to warrant the upgrade as Snow Leopard is easily the best version of OS X to ship.

I will say though, the mix of bright and dark elements is a little odd, but I don't see them switching to a dark interface as much as I'd love one. Perhaps a separate theme but Apple isn't the type to offer a variety of themes. I can see them using the dark elements to separate huds/menus/controls from the main interface, with the brighter window. This way you can distinguish one from the the other quickly and easily. The day we can theme it, I'll make a lovely black glass theme for everyone to enjoy ;) Until then we're stuck with Aqua or whatever you want to call it at this point.

Same. Parallels developers might as well release a free update to support Snow Leopard (Parallels 5.0 or 4.1?)
Are you saying that you can't get VMware to work on SL? Mine is running just fine and has been for the longest time.

Yeah, I just tried it, but it says 64 bit kernel incompatibility. Maybe your SL isn't running in 64 bit?

post-5976-1249998144_thumb.png

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

    • No registered users viewing this page.
  • Posts

    • Microsoft launches Godot Sample to streamline Xbox PC game development on the engine by Pulasthi Ariyasinghe Microsoft today announced a new endeavor that aims to make it simpler for Godot developers to get their products into the Xbox PC ecosystem. Dubbed the "XBOX Godot Sample," this is a new public reference for developers using the open-source engine. This is set to serve as an example of how Microsoft GDK, Xbox Services, and PlayFab can be integrated into their projects. The sample is available now on GitHub as a working example. This covers key features in gaming projects that developers may need to release their projects on Xbox PC, with everything from matchmaking and game sign-in to gamepad compatibility with Godot being covered. This release is being called the first step in giving Godot developers the tools to bring their games over to Xbox PC, with more changes to come based on feedback and issue reports. However, the company was clear that this is not related to bringing Godot projects to Xbox consoles. The engine's open development model stops it from accessing console SDKs due to the requirement of NDAs and legal contracts. Here's how it explained this Godot sample project's focus: This is a source-only sample, not a product. It's MIT-licensed at the wrapper layer; the GDK and PlayFab dependencies still require their own installs and license acceptance, consistent with our other XBOX samples. There is no set update cadence for support or maintenance. We’ll watch the repo, monitor issues, and iterate where it makes sense, but this isn't a commercial release. That said, we’re excited to hear your feedback and see any community PRs, as we evolve this together. This is the first step in bringing Godot for XBOX on PC. We plan to evolve it over time based on what the community tells us is most valuable. This sample is built specifically for XBOX on PC. It doesn’t include support for XBOX Series X|S or XBOX One. If you’re already building for XBOX Series X|S or XBOX One, please talk with your XBOX representative. If not, you can get started by signing up here. Game developers can find the XBOX Godot Sample by heading to GitHub over here. Documentation on how to get started with Godot for building an Xbox PC project can be seen here.
    • I don't understand the vision. Do people really want to buy a new computer from Dell with 6 browsers installed? We all keep asking for Microsoft to stop having so much junk on their OS, and adding a bunch of browsers seems to go against that. Ideally, we would just be asked what browser we want during OOBE but Google is just going to pay Dell a bunch of money to include Chrome. Additionally, would you want your phones to start including all the browsers too when you get them? The only thing I ever wanted was to be able to uninstall IE or edge and I believe you are now able to. I do agree that microsoft needs to chill with their "are you sure you don't want to try edge before you install chrome" ads when going to download chrome.
    • It is notable that around 70% of web browser users choose Google Chrome. However, it is puzzling why anyone on Windows would opt for Chrome when Microsoft Edge is often superior in many aspects and comes pre-installed. Edge collects less data, uses less RAM, and is more optimized for Windows as a native Microsoft product. While some may point to bloat in Edge, much of it can be removed with simple tools, requiring no more effort than installing Chrome. Meanwhile, Chrome reportedly downloads large amounts of AI data (4 GB) without explicit consent. I'm sure you Chrome users love that, or? Although Microsoft’s aggressive promotion of Edge may be questionable, the browser’s current advantages make it a preferable choice over Chrome today, even if Chrome may have been better in the past.
    • JetBrains rolls out IntelliJ IDEA update with Markdown preview fixes and more by David Uzondu Image via JetBrains IntelliJ 2026.1.3 from JetBrains has landed, bringing several highly requested bug fixes that target common UI glitches and terminal rendering issues. If you run tmux inside the integrated terminal, the IDE no longer renders the cursor above the active line. The Markdown preview bug, which was fixed in this release, had annoyed developers for quite some time, as the preview pane failed to render images saved outside the project directory. Instead of displaying the actual image, the IDE simply showed a broken image icon, a problem that stuck around for two years before this update. Over on Windows, developers running WSL can now use wsl.exe to spin up their environments without losing terminal functionality. In previous builds, launching a terminal shell with something like wsl.exe -d ubuntu inside a Windows-based project broke both shell integration and active process detection. Other bug fixes in this release include: An issue where Gradle sync incorrectly reported success as a failure on WSL when using Gradle 9.5.0. A syntax highlighting bug that flagged valid Java for-loop initialization blocks with multiple statements as incorrect. A warning bug that triggered a false non-null local variable alert when using JSpecify annotations. A database generation bug that hid the option to use a DELETE statement instead of a TRUNCATE checkbox. A Kotlin highlighting failure where an assertion error in the Gradle redundant library inspection broke error highlighting. A UI bug where the ComboBox popup lacked a maximum height restriction. A Snowflake syntax error where DataGrip failed to support the "create temp" command. A Svelte syntax parsing failure that incorrectly flagged quotes inside inline expressions. A VCS repository manager deadlock that triggered thread pool exhaustion. A memory leak where the LazyTree component kept all previous versions of a tree in memory. IntelliJ 2026.1.3 is the third bug fix release for the IntelliJ 2026.1 series. The first one landed back in April with a fix for the WSL Python interpreter freeze, another fix for guest participants using Emmet abbreviations, and corrected WildFly server deployment errors.
  • Recent Achievements

    • Collaborator
      Asgardi earned a badge
      Collaborator
    • Conversation Starter
      mobandz earned a badge
      Conversation Starter
    • Apprentice
      fernan99 went up a rank
      Apprentice
    • One Month Later
      nothanks earned a badge
      One Month Later
    • One Month Later
      B2Proxy earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      469
    2. 2
      PsYcHoKiLLa
      243
    3. 3
      Skyfrog
      79
    4. 4
      FloatingFatMan
      73
    5. 5
      Michael Scrip
      60
  • Tell a friend

    Love Neowin? Tell a friend!