Windows Live Wave 3: Messenger v9

By BajiRav
in Microsoft (Windows)

 Share

Recommended Posts

Mentor

andy2004

Posted
Posted

does vista even use GDI ? i could swear it doesnt and GDI is only XP. Older aplications which use GDI are supported on vista but internally are remapped where possible.

from http://msdn.microsoft.com/en-us/library/bb173477.aspx

The primary API for programming graphics since the early days of Windows has been the Graphical Device Interface (GDI). This API was designed to handle a plethora of 2D output devices and formed the basis for the Windows user interface experience. DirectDraw and Direct3D were introduced as alternative APIs to support full-screen games and 3D rendering as extensions to the existing hardware of the time. Interactions with GDI were complicated, and the effective intermixing of traditional GDI elements with Direct3D elements has been limited by this design. The Windows XP version of WDM, known as XPDM, reflects the side-by-side nature of GDI and Direct3D (see Figure 1).

Figure 1. Graphics APIs in Windows XP

Bb173477.Graphics_APIs_in_Windows_XP(en-us,VS.85).gif

Over the years, the power of 3D video cards has grown dramatically to the point where the vast majority of hardware is dedicated to this function. A new driver model, Windows Vista Display Driver Model (WDDM), brings the GPU and Direct3D to the forefront, allowing the creation of an entirely new experience, the 3D desktop, that seamlessly blends the 2D world of GDI with the power of modern programmable GPUs. With WDDM, the video hardware is driven entirely by Direct3D, and all other graphics interfaces communicate with the video hardware via the new Direct3D?centric driver model (see Figure 2).

Figure 2. Graphics APIs in Windows Vista

Bb173477.Graphics_APIs_in_Windows_Vista(en-us,VS.85).gif

Windows Presentation Foundation

from: http://msdn.microsoft.com/en-us/library/aa970268.aspx

Windows Presentation Foundation (WPF) is a next-generation presentation system for building Windows client applications with visually stunning user experiences. With WPF, you can create a wide range of both standalone and browser-hosted applications. Some examples are Yahoo! Messenger and the New York Times Reader, as well as the Contoso Healthcare Sample Application that is shown in the following figure.

Aa970268.WPFIntroFigure24(en-us,VS.90).png

The core of WPF is a resolution-independent and vector-based rendering engine that is built to take advantage of modern graphics hardware. WPF extends the core with a comprehensive set of application-development features that include Extensible Application Markup Language (XAML), controls, data binding, layout, 2-D and 3-D graphics, animation, styles, templates, documents, media, text, and typography. WPF is included in the Microsoft .NET Framework, so you can build applications that incorporate other elements of the .NET Framework class library.

Community Regular

Fagutish

Posted
Posted
does vista even use GDI ? i could swear it doesnt and GDI is only XP. Older aplications which use GDI are supported on vista but internally are remapped where possible.

the GDI vs. WDM situation is a little more convoluted than it should be since GDI was alot of things for alot of people.

You're absolutley right about Vista "remapping" GDI calls to render legacy (read: almost every app out there) applications. Which is what were talking about here when we say WLM v9 M1 doesn't use WLM as we can see the consequence of using GDI and calling for the removal of window borders, the loss of drop shadow. (you can also see this phenomenon in Zune app, iTunes and various other Windows applications that have non standard windows)

So Vista uses GDI calls simply to slap them on to the desktop window manager (dwm.exe) which is a part of the directx window rendering service in vista AKA DCE (desktop composition engine)

The part of GDI that Vista lacks at certain points in time is the rendering service portion of GDI. The part of GDI that renders the stuff on your monitor. That is now offloaded to DWM.exe in vista but ONLY when Aero is enabled. Thus, if your gcard doesnt support aero or you choose to run on classic theme youre back to GDI window drawing and everythings just like xp on the rendering side. Vista Home basic, contrary to popular belief, has DWM installed and enabled but microsoft has enabled some artificial barriers so users cannot have translucent windows etc. Its still DirectX rendered though so you get all the snappyness and goodness of vector based rendering via graphics card.

WPF on the other hand will work in both DWM and GDI environments. Its simply another API for programmers to present their application to users.

I hope this helps solve the confusion or maybe its borderline TLDR..

Grand Master

BajiRav

Posted
  • Author
Posted
I know I'm going to catch a ton of flak here about my next comment, but I feel brave this morning.

Nothing irks me more than people commenting on a piece of software that isn't even in the BETA test phase, and how it looks crappy, or they don't like one feature or another, or even asking if it's going to have "Feature Q" instead of "Feature R" or even "Features Q and R" - and then pass judgement on it as if it's the finished product. Heaven help you if, when you were newborn that your parents didn't like how you turned-out because you had the wrong head-shape or that your fingers and/or toes weren't long enough.

Since this is an M1 build, it means that it runs. It may crash, it may have a minimally-new feature-set if that, and may not have any other features that "the outside world" wants at that time because of internal code-changes, and it's UI is not going to be the end-product's look and/or feel. It means that they can say "Whew! It passes code review and the first smoke-test. Now, to fix the bugs we know about and find more bugs"

Have some perspective, people!

:|

--ScottKin

Although I see your point, I don't have any such faith in the Messenger team. Experience with last couple of betas has been real bad. If these shots are legit, this is pretty much what we will end up getting in the end. I would love to be proven wrong though. :)

Veteran

y_notm

Posted
Posted
The reason I'm assuming its still GDI and not WPF is partially due to

A. The windows have no drop shadows in Vista in those screenshots

and also

B. Its too similar to their GDI interface from 8.x and below to be a full rewrite. IMHO anyway..

Also check out Yahoo's WPF-using Messenger. That's the kind of thing most people were expecting hoping for..

A. has nothing to do with whether it's being rendered by GDI or WPF. You can remove the frames in WPF just as easily (if not easier) than you can in WinForms/Win32/GDI+

B. Is a much more reasonable reason to believe its being rendered by GDI, but then again they may be taking advantage of the new features of the WPF platform without dramatically changing the interface and risking alienating the hundreds of millions of current users.

Mentor

zerologic

Posted
Posted
Yeah it doesen't look better ;/

Just shows, you can have a company like Microsoft, with all the money in the world (or near enough) and still no style.

Money can't buy style.

No matter how early this build is, it's a sign that the Windows Live people behind Messenger really need a lesson in UI design.

Grand Master

Ci7

Posted
Posted (edited)
Just shows, you can have a company like Microsoft, with all the money in the world (or near enough) and still no style.

Money can't buy style.

No matter how early this build is, it's a sign that the Windows Live people behind Messenger really need a lesson in UI design.

that still alpha 1 WLM ...... so don't expect much

i bet you are from same guys who complained about windows 7 M1 looking the same as vista and having nothing more .

Edited by Skynetfuture
This topic is now closed to further replies.
 Share
Go to topic listing

  • 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 LoneWolfSL · Posted

      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.
    • Browser vendors pen open letter to Microsoft saying "enough is enough"

      By Primey_ · Posted

      The nerve of Google to sign this.
    • Browser vendors pen open letter to Microsoft saying "enough is enough"

      By s0nic69 · Posted

      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.
    • Browser vendors pen open letter to Microsoft saying "enough is enough"

      By The Norwegian Drone Pilot · Posted

      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? Here is one example of a tool that doesn't even need to be installed to be able to use: https://github.com/TheBobPony/MSEdgeTweaker 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 · Posted

      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
      468
    2. 2
      PsYcHoKiLLa
      243
    3. 3
      Skyfrog
      79
    4. 4
      FloatingFatMan
      73
    5. 5
      Michael Scrip
      60
    Show More

  • Tell a friend

    Love Neowin? Tell a friend!