Windows Live Wave 3: Messenger v9


Recommended Posts

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.

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..

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. :)

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.

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.

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.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Absolutely NOBODY has suggested such a conclusion. I am affirming the sober reality check that AV2's overall market adoption will take longer than AV1's adoption rate -- which, by the way, is the whole point of the article! While PCI-SIG is productive (on paper), other WGs have created all sorts of confusing progress plans that consumers have tuned-out of their improvements... HTML/W3C, USB, HDMI, BT, WIFI (ieee802.11) as a few other groups where spec naming conventions, split progress paths, overlapping ambitions... I'm not critiquing the AV specs group; I'm simply affirming that adoption for AV2 faces headwinds beyond the macroeconomics of it all.
    • Segra 1.5.2 by Razvan Serea Segra is a free, open-source OBS-powered game recorder offering fast gameplay capture, instant clips, AI highlights, deep game integration, and seamless uploads—perfect for gamers, streamers, and content creators. Lightweight, fast, zero bloat. Segra key features: Automatic Game Recording: Begin capturing gameplay the moment your game launches, with zero manual setup. Instant Clipping: Save important moments instantly using a customizable hotkey—perfect for highlights, montages, or quick shares. Segra AI Highlights: Let Segra automatically detect kills, assists, deaths, and key events to generate polished highlight reels without manual editing. Gameplay Uploads: Upload recordings and clips directly to Segra.tv for fast sharing and cloud access. Deep Game Integration: Enjoy advanced game-data tracking across hundreds of supported titles, enabling smart highlight generation and stat-informed clipping. High-Performance Capture: Record up to 4K at 144 FPS using OBS-powered technology with minimal performance impact, supporting NVENC, AMD VCE, and custom quality controls. Segra Editor: Edit recordings easily with timeline controls, segment management, and event-based navigation to build the perfect clip. Customization Options: Adjust hotkeys, output formats, storage paths, codecs, capture quality, and performance settings for a tailored recording experience. Segra 1.5.2 changelog: Settings: Added an Airplane Mode that hides account, login, and upload features. Storage: Added a button to migrate videos into the recording path after changing it. Import: Added auto-scroll and a highlight pulse to videos right after importing. Recording: Added graceful handling of low disk space and output failures, finalizing files safely with clear errors. Recording: Added a guard blocking recording when any drive exceeds 99% full. OBS: Removed the download timeout to support users with slow internet. Clips: Fixed an error modal incorrectly appearing when clip creation was cancelled. Settings: Fixed the content folder path not refreshing in the UI after changes. Updates: Improved error handling for multiple simultaneous update checks. Stability: Fixed a WebSocket reconnect loop that ran while the window was backgrounded. Dependencies: Updated project dependencies. Maintenance: Removed dead code, reduced duplication, and fixed several latent bugs. Download: Segra 1.5.2 | 73.1 MB (Open Source) View: Segra Homepage | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • No thanks! WebView trash is unacceptable. I only use software that's native.
  • 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
      465
    2. 2
      PsYcHoKiLLa
      244
    3. 3
      Skyfrog
      79
    4. 4
      FloatingFatMan
      70
    5. 5
      Michael Scrip
      60
  • Tell a friend

    Love Neowin? Tell a friend!