Linked by Thom Holwerda on Wed 31st Aug 2011 19:42 UTC
Windows Over the past few days, Microsoft has been talking about improvements made to Windows 8 on its 'Building Windows 8' blog at MSDN. Strangely enough, the improvements mentioned were either dealing with the classic desktop, or were demonstrated using the classic desktop - and not the fancy Metro user interface which is supposed to be Windows 8's big new thing. Today's post finally gives a little more detail about how the classic and Metro UI work together, but questions still remain.
Thread beginning with comment 487867
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: Comment by joekiser
by benhonghu on Wed 31st Aug 2011 23:24 UTC in reply to "RE: Comment by joekiser"
benhonghu
Member since:
2008-08-24

The question is, how deep? My guess is: not much beyond explorer.exe

Think about it, the Metro interface is powered by IE 10, and IE runs on the same Win32 API as any other "classic" application. So non of the underlying stuff shall be removed.

Reply Parent Score: 1

Trident Rendering Only
by asupcb on Thu 1st Sep 2011 03:23 in reply to "RE[2]: Comment by joekiser"
asupcb Member since:
2005-11-10

Metro will only need to utilize the Trident rendering engine and not the entire IE10 application to run. I'm not really sure what dependencies Trident has but one would assume that it only needs Win32 APIs when in use as the embedded rendering engine in an application such as IE.

I assume it works the way WebKit does.

Edited 2011-09-01 03:24 UTC

Reply Parent Score: 2

RE: Trident Rendering Only
by Laurence on Thu 1st Sep 2011 08:16 in reply to "Trident Rendering Only"
Laurence Member since:
2007-03-26

Metro will only need to utilize the Trident rendering engine and not the entire IE10 application to run. I'm not really sure what dependencies Trident has but one would assume that it only needs Win32 APIs when in use as the embedded rendering engine in an application such as IE.

I assume it works the way WebKit does.

I would imagine that it would still need DirectX (unless MS are thinking of reinventing the wheel). I don't know if Win32 is a dependency of DX or even if it is, if MS are unpicking that. Either way we're not talking that much deeper than running on top of a Win32 layer.

Plus Win32 APIs are still pretty bare metal in terms of the entire Windows API stack. It's when you start including .NET and Java runtime environments that you start moving away from core Windows user land.

Reply Parent Score: 2

RE[3]: Comment by joekiser
by Halo on Sun 4th Sep 2011 01:14 in reply to "RE[2]: Comment by joekiser"
Halo Member since:
2009-02-10

That line of reasoning does not follow.

Microsoft already has a version of IE for Windows Phone 7 which doesn't rely on the underlying Win32 API.

I don't think it's a reasonable asssumption that IE10 relies on Win32, and as such you can't conclude anything about Windows 8.

I will be very surprised if the Win32 userland hasn't been modularised so it isn't loaded by default.

Reply Parent Score: 1