Desktop Window Manager Index of Post Topics

Here's a list of topics that I have posted on (with active links) or expect to post on (without links) related to the Desktop Window Manager in Windows Vista.

• Under the Hood of the Desktop Window Manager -- a technical introduction (and response to comments)
• DWM's use of DirectX, GPUs, and hardware acceleration (and response to comments)
• The role of the Windows Display Driver Model in the DWM (and response to comments)
• Redirecting GDI, DirectX, and WPF applications
• How underlying WPF concepts and technology are being used in the DWM 
• High DPI support (and response to comments)
• APIs in the Desktop Window Manager 
• Rendering and visibility optimizations
• Memory usage in the DWM
• Power management and battery life
• How the DWM paints the window frame and other non-client area
• Remoting, Magnification, and Accessibility under the DWM
• Best practices for applications under the DWM

If there are specific other topics you're interested in, please comment away.

Comments

• Anonymous
  March 25, 2006
  I'm interested in how third parties can create their own effects and manupulate the DWM. But I suppose that will come under "Publicly exposed DWM APIs"?
• Anonymous
  March 25, 2006
  And one of the more spesific things is if it will be possible to customize the appearance Aero. At the moment we have Stardock's WindowBlinds that allows us to customize the appearance of XP. Will the same be possible for Aero?
• Anonymous
  March 28, 2006
  I'm interested in how Open GL will play in the model too.  Today we are able to have higher perf thanks to h/w acceleration with OpenGL.  But it looks like Vista is forcing that to s/w mode and slowing things down.  Any thoughts on this front are appreciated!
  
• Anonymous
  March 28, 2006
  The comment has been removed
• Anonymous
  April 04, 2006
  John Schroedl:
  
  I looked into this a while ago, based on David Blythe's presentation at WinHEC last year. At that time, if I recall correctly, the plan was as follows:
  
  If the video card manufacturer supplies an OpenGL ICD and the application chooses it, it will be used. If it's a legacy ICD, because the ICD can't be interrupted, DWM will switch off. There is apparently to be a new API for writing DWM-compatible ICDs.
  
  Otherwise OpenGL calls will go through an OpenGL to DirectX translation layer. The resulting DirectX calls will be interruptible and DWM will remain on. The translator will only support OpenGL 1.4 IIRC, not the latest 2.0.
  
  See http://blogs.msdn.com/kamvedbrat/archive/2006/02/22/537624.aspx.
• Anonymous
  April 05, 2006
  From Nick Kramer.
• Anonymous
  April 11, 2006
  As an access technology developer, I am especially looking forward to learning about magnification and accessibility under the DWM.  Thanks for providing all of this useful information.
• Anonymous
  April 17, 2006
  对于从事Windows驱动开发的朋友，或者是对Windows内核感兴趣的朋友，以下几个BLOG值得经常看看！
  1，Kernel Mustard by Steve Dispensa link:...
• Anonymous
  April 23, 2006
  It's been just over seven months since my last post, so I'm happy to inform that reports of my death...
• Anonymous
  May 02, 2006
  As mentioned in earlier posts, by far the most important aspect of the DWM is the fact that application...