Mike held a small roundtable for a number of pressies. He gave a quick rundown of things you all basically already know, so I took the time to ask a few questions which kept you guys in mind. The questions I asked:

• What’s the difference between “API Complete” (build 6801) is and “Feature Complete” (Beta 1)?
• Why were lots of code samples and features being shown off for the Superbar at PDC when developers can’t develop for it? (Rafael’s extension of my API v. Feature Complete question)
• Why were the sensor demonstrations missing from the Windows 7 keynote today?

The answers to these questions can be found in the true-to-life* transcript after the break.

*Given that this is a transcript, it may be wrought with grammatical errors, but this is exactly how the chat went down.

Bryant: I had a question which I had myself but my colleague Rafael phrased it much better than I did, and it kinda ties into your note about how the build given to developers here at PDC this week is “API Complete” whereas the builds you were… whereas beta 1 is going to be “Feature Complete” or at least that’s the attempt… my own question is: what’s the difference between “API Complete” and “Feature Complete”? More specifically, Rafael’s question is, um, he noted that there are a lot of sessions at PDC talking about the superbar, and developing for the superbar, and one session that he went to had a lot of code samples being shown, but he also took note that developers can’t even develop for it because the superbar isn’t even in the build.

Mike: So the question really is, first of all, “What’s the difference between ‘API Complete’ and ‘Feature Complete’, and what is a developer to do who wants to write software that takes advantage of features that aren’t in the current ‘M3’ build.” So API complete, um, says that all the interfaces that developers are gonna code to… are in the product, and the third milestone of Windows 7 always had the goal of being API complete, which means  we’re not going to add any more APIs subsequently. Feature complete means that all the functions that are gonna be part of Windows 7 are in that build, and our beta, which will ship early next year [in time for CES], will be Feature Complete. The real – One of the hard questions we had… which we faced, is “Well, do we give everyb—do we only demo the API Complete release even though we have been working since September when we cut M3, do we demo more than the M3 build” and the answer is “aaah! We only have these developers together that often. It’d seem like kind-of a shame to not show them everything we had,” which then begged the question “Well why don’t you just give them the build that Steven used on stage?” which was the stuff from last Friday. The answer is “Well, in order to stabilize that, we woulda had to start stabilizing it back in August to be done in September (which is kinda what we did), so we couldn’t give you something from last Friday at this scale, or at the same time, it’d seem like a shame to not show you everything that we had. So what you see here is that optimization. Is it perfect? No. I think the other thing—hey well I could tell anybody anything til it’s all the way done. The problem there is, you don’t give the ecosystem the chance to get going. So, you are here a little bit watching the sausage being made in the sense that you’re watching us have this dialog with our partners to make sure that they are ready so that when we get to beta, there’s some momentum for Windows 7, and then certainly as we get towards general availability for Windows 7, there’s a healthy set of things that take advantage of Windows 7 that are out there.

Bryant: So, I guess tying back into the API Complete v. Feature Complete stuff, could a developer develop for the superbar in 6801?

Mike: Certain aspects of it, yes; certain aspects of it, no.

Bryant: Okay.

Mike: and some of that is sorta enough work to do between now and then that when the beta comes out they can get, you know, have all those features be there.

Bryant: Okay, thanks.

Mike: Great question.

Bryant: A few more questions, I guess, but… in the keynote that I saw today, there was one thing that was notably absent, and that was the sensor demos which were later discussed in the expo hall. Are you guys saving the sensor demonstrations — like the accelerometer demos, the touch demos and such… well not the touch demos so much but mostly just sensor work) — but are you saving that more for… WinHEC?

Mike: If I told you, I’d have to kill you.

Some other pressie: Cool!

Mike: Okay, here’s the challenge. Today was the first time that we talked about Windows 7 in any scale, and I’d say, again, sorta the… how advanced this thing is – this phase, we’re further along than we’ve been at least in a long time. How much do people know? We’ve held a lot more back than ever, so today was like “WOW; lot to talk about and not a lot of time,” and we had to be sorta choiceful about what we talked about.

Bryant: Yeah.

Mike: Next week we have WinHEC – things that are about sorta the core of Windows 7 by default happened here. Things that are more… developer oriented… happened here. Things that are more hardware oriented, without being specific, you could expect to be in a convention center not unlike this one in a town with the same zipcode.

[laughter]

Mike: Yeah, in about a week.

Summary:

• What is API Complete v. Feature Complete? API Complete has the developer bits ready for the developers to work with, even if some of them are dead-ends for now. Feature Complete expands on this by making all of the APIs functional.
• Why were code samples and such being shown off for the Superbar? Developers will be able to code for it anyway, but they’ll have enough to work with between now and Beta 1 that once Beta 1 hits the scene, they’ll have a good amount of code that doesn’t require functional awareness actually prepared.
• Why were the sensor bits missing from the Windows 7 keynote? Because it’s more relevant to WinHEC, but there’s a session on that which I’ll be covering today, so it’s all good.

There you have it. I’ll be covering today’s sensor demonstration at 10:30 today. I look forward to bringing you what I see.

Events to choose from:

• Preconference Sessions
• Conference Sessions
• Keynotes
• Symposia
• UnSessions

If you have any people in mind whom you think would provide good insight into a particular subject, feel free to list them as well and I’ll see what I can do.

If you’re registered, please leave your ideas as replies to this forum thread. If you’re not registered, feel free to leave suggestions here. (On that note, why not subscribe? We pay out of pocket for these trips; Even a little bit helps!)

While perusing the PDC 2008 website’s preliminary agenda, I came across two sessions that really caught my attention:

Windows 7: Graphics Advances
Windows 7 enables you to advance the graphics capabilities of your applications while carrying forward existing investments in your Win32 codebase, including GDI and GDI+. New enhancements to DirectX let Win32 applications harness the latest innovations in GPUs and LCD displays, including support for scalable, high-performance, 2D and 3D graphics, text, and images. Also learn how to leverage the GPU’s parallelism for general-purpose computation such as image processing.

and

Windows 7: Web Services in Native Code
Windows 7 introduces a new networking API with support for building SOAP based web services in native code. This session will discuss the programming model, interoperability aspects with other implementations of WS-* protocols and demonstrate various services and applications built using this API.

After reading these, I could come to only one conclusion: Microsoft is building an unmanaged version of WinFX (at least the WPF and WCF components of it), currently known as .NET Framework 3.0.

This isn’t the first we’ve heard of this. Long first revealed a job description back in March that related to a new, native UI framework for Windows 7. The PDC session overview doesn’t add much (outside of the WCF component) to what was revealed there, but it does seem to indicate that this framework hasn’t been cut from Windows 7.

A native WinFX excites me for many reasons. One reason is that it opens up the robustness of the Windows Presentation Foundation (WPF) to native developers, most likely with a significant performance gain versus the current managed WPF developers use now.

Also, according to the job description, this framework will use a markup language to define user interfaces (Most likely XAML or something extremely similar), which means designers will be able to use their knowledge (and code) across Win32, .NET and Silverlight now. This could speed adoption of all three technologies, which is nice.

Perhaps the most exciting things to the average user are the possibilities this offers up to Microsoft for Windows 7 itself. Microsoft jettisoned most of its vision for a graphically rich shell when it reset Longhorn development and realized that building Explorer in .NET and on top of a framework that was still in development was a bad idea. Now that this framework (milcore) is done, Microsoft should be able to harness its power rather easily through this new unmanaged WinFX framework without having to completely rewrite Explorer.

In other words, much of the UI goodness from the early Longhorn prototypes could wind up in 7.

Here’s hoping, anyway.