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.

• Import and export images
• Change, add or remove properties
• Import and export STREAM images
• Compile into a totally new MsStyles-file

In this post I will highlight some details of Vista Style Builder (VSB) which show how much easier this application makes it to edit MsStyles.

The Main Window

Most of the time when creating Visual Styles, you will be looking at the main window of VSB. This main window exists basically of four parts:

• The command bar in the top of the window to do things
• The UI parts browser on the left which displays every UI part in a MsStyle neatly grouped into categories
• The Preview pane, which will show the images used in a UI part
• The property view in the bottomright, showing an editable list of all properties for a UI part

As you might notice, there is no menu bar anymore. In line with most Vista applications, VSB uses a commandbar for all possible actions that can be done.

Importing Images

VSB allows a user to export the images used in a Visual Style in order to edited the images in an external application, such as Adobe Photoshop. It is possible to export a strip of images (e.g. all different button states in one image), but it is also possible to just export one state of an image (e.g. the button-pressed image).

Importing is done in a similar fashion: you can import an image with all states or just one state directly. VSB always provides a default name for importing and exporting, so if you follow that naming schemes, you can quickly import and export images.

VSB will notice it if you try to import an image of different dimensions than the original; it will actually ask you what you want to do:

Alpha Channel Importing

One of the problems people are currently facing with Vista Styles is that photoshop and Vista uses a slightly - or so it seems - different format: the alpha channel comes out wrong in MsStyles for files imported manually.
Vista Style Builder fixes this incompatibility when importing images.

Adding Properties

Another feature in VSB is the possibility to add new properties to UI parts. This makes it possible, for example, to give the taskbar fonts a glow or even make the breadcrumb bar glow.

Properties are added through a easy to use dialog which allows you to select the type of property (e.g. enum or color), the name (e.g. iconeffect or textcolor) and the value. For enumeration-types, such as Iconeffect, a listbox will automatically show all possible values.

StyleHacks

People often want to change the same things in their Visual Styles. Some good examples are a thinner taskbar and a small startmenu. Most of the time, these things involve editing a number of properties in some unexpected way.

To make it easier for everyone to use often done things in their styles we invented StyleHacks in VSB. A StyleHack is an easy way to apply an often done thing (a`hack`) to your Visual Style. For example, there is a StyleHack to change the height of the taskbar to 18px.

Visual Style Builder provides an in-application menu to browse the available StyleHacks with a preview image and apply them with a click of the mouse:

Import XP Styles

A featue of Visual Style Builder that has been secret until now is the ability to Import XP MsStyles.
That’s right, VSB makes it possible to use your favorite XP Styles on Vista! Most XP Styles only need some small modifications after importing to work correctly on Vista .

Here’s an example of XP Luna after having it converted to a Vista Style after importing:

As you can see, the dialog uses the Luna window borders as well as Luna buttons. As a bonus, the Luna theme got dropshadows and is rendered by the DWM. For this theme, I opted to keep the Aero buttons because I personally think they look great on the Luna theme.

Of course, not all themes can be imported 100% correctly: Vista has some more restrictions on the window frames than XP had. However, it will make porting much easier and it works for a lot of themes without modifications.

Availability and price

The big question is now when will VSB be available? Unfortunately, I can’t really give a date yet. The technical side of the application is completely done; the business side, however, is not.

I know a lot of people expect this application to be free, but I can tell you that it will not be free. There went a lot of work in VSB and, at the very least, I need to earn the invested time back.

Editor’s Note: A distribution policy for Vista Style Builder and AeroXperience members is currently being researched

Before I really jump in, I should explain why leaks of this magnitude are bad. Believe it or not, these leaks do hurt Microsoft and the dev process of the operating system, especially this early in the cycle. When a leak happens, Microsoft has to devote time to investigating the leak and trying to pin down a source, ultimately the internal source or OEM who leaked it. Leaks are also bad because there are just some things that aren’t ready to be seen outside of Redmond yet, especially by the average Joe user. Say a build leaks, and average Joe doesn’t like a certain feature, or even more realistic, finds a real nasty bug. He blogs about that and next thing you know everyone is jumping on the slingfest bandwagon and presto, bad image before the product is even out of the gate.

The main thing about the 6519 leak that gets me is the fact that it leaked after so much time. I can only assume that it came from someone in the group that got the build about a month ago, and for some reason was looking for a “15 minutes of fame” moment. There is, however, a silver lining to all of this. The build is hard coded to expire on June 6th, after which date the activation system will lock you out of the system. Why someone would leak after expiration, you ask? Well it’s actually a pretty simple answer. They get their little moment of fame and (they think) cause little damage to Microsoft since Joe user can’t use it on a daily basis. The fact is though, the beta community is rather unique, we take builds of OS’s and actually use them on our machines to tinker with and see the direction that Microsoft is going with the future of Windows. With 6519, running on the current date is now impossible, but the OS can be used if you set the date back before expiration, which some will probably be willing to do, just for bragging rights.

I guess the point I am trying to make with all of this is 6519 never should have been leaked, but it is the unfortunate fact that we have some people in this community that just can’t seem to keep anything under wraps and thinks that leaking a build will gain them some kind of celebrity status. That could not be more inaccurate. Within the last few years leakers have been looked upon as the black sheep in the community, for the exact reasons that I mentioned earlier. The fact is that these people will never learn, and will likely continue to do things like this.

News broke this week that a number of senior Yahoo engineers are leaving. Despite the fact that all of them stressed that their walkouts have nothing to do with the now-failed Microsoft merger, there’s a good chance that that’s probably what it is. Let’s take a quick look at why the departures of Jeremy Zawodny, Jeff Weiner, and others are related to the fallout of a failed Microsoft buyout and the problems Google poses to some of Yahoo’s best engineers.

Yahoo is well known as a popular web property. While many people in the United States and Europe have Google set as their homepage, Yahoo is a hot landing spot for many non-western nations such as China. Yahoo also knows how to maintain the communities formed by the Web 2.0 startups they pick up. One good example is Flickr; it’s is still popular with many photographers despite being owned by a monolithic and arguably uncool parent company. Del.icio.us is also roughly as popular as a social bookmarking service as it was when it was purchased by Yahoo. The engineers which Yahoo picked up with these acquisitions have also been put towards a number of other projects, which may have been part of the reason for the acquisitions in the first place besides expanding the Yahoo brand name.

Picking up knowledgeable engineers may have also been part of the reason behind the Microsoft-Yahoo merger. Besides the engineers which would come along with such a buyout, name placement in those eastern markets as well as popular and well-maintained Web 2.0 services serve as a very healthy set of bonus reasons for a rather expensive merger.

A number of analysts and commentators have also speculated that the buyout offer may have been put forward as a means of pushing the company towards disarray and, subsequently, towards a mismanaged doomsday. Microsoft has used buyout proposals for this purpose before, and Yahoo’s board might have kept this (and ego) in mind when trying to negotiate a higher per-share price.

How does this relate to the engineers? Microsoft has a number of interesting research programs. While Yahoo’s engineers might loathe the idea of working for a “mundane” product such as Windows or Office, Microsoft’s research programs offer new opportunities for developers to branch out into brand new fields and markets, something which Yahoo currently doesn’t have in place. On the other hand, Google has let a number of their acquisitions stagnate (blogger, now nothing more than a spampool, is the largest example.) without any significant overhauls, and their research programs remain mostly on the web as opposed to spreading into new fields.

Creativity isn’t often a word associated with Microsoft, but Microsoft is much more well established in a multitude of fields than both Google and Yahoo. This may be the primary reason behind the departures of some of Yahoo’s best minds. Jeremy Zawodny, after all, is one of the most well-respected R&D engineers Yahoo ever had, and and his attraction towards a small up-and-coming firm is representative of the new environments many of Yahoo’s engineers are interested in.

I personally have always maintained that I would jump to Vista in a heartbeat if we got a machine, but that time hasn’t come yet, and frankly, for my pocketbook’s sake, I’m glad. There are some, though, who still want to get Windows XP when they buy a new machine. I’m not about to jump into a big debate on the topic – it’s just the way it is.

Many computer manufacturers took to expected approach in early 2007 of going “Vista-only”. People asked to get XP back, and many companies (Dell especially comes to mind) went and offered it up again. Microsoft then came out at a later time and said that they would continue offering XP to OEMs and at retail until June 30, 2008 – the end of the month. Some were maddened by this, wanting still to stick with XP.

While I was browsing around last week, I came across this interesting gem on a local computer shop’s web site:

Now as the image says, this shop is no small little thing, they are Microsoft Gold Partner and have close ties with Intel as well. However, I found it interesting that one of the biggest computer manufacturers, Dell, would stop selling XP on new systems on June 18, while this small shop could sell it until January 2009. It now appears that Dell figured it out, and mooted the point made in the above image.

According to a story on Neowin, Dell is now going to offer Windows XP Professional on new computers through “at least 2009 and likely longer.” The story mentioned that this means either Dell stocked up on a “year’s worth” of licenses, or is preceding an announcement by Microsoft saying that XP Pro will continue to live on. Note that Dell is not forgetting Vista here – they are including both media so that users can upgrade when they’re ready. Is it a smart move on Dell’s part? It would appear so at first. I mean, it will surely make people happy, at least those not sure if they’re ready to take the plunge yet

But come on, it’s been 16 months since Vista hit the shelves and some people are still not ready to give up XP? If you’re going to miss a car 16 months after you sell it, or call your son or daughter every day, twice a day, for 16 months after they move out of the house, people will: a) think you’re crazy, and b) in the case of the children, probably hurt you, or at least get rather irritated. However, it’s a completely different story here, and I’m not convinced it should be. Service Pack 1 is here, and although it’s not a huge “life saver”, it is a service pack. This is the magic milestone many people wait for (just look back over comments concerning Vista’s launch). And then look back further. I’m sure there was a transfer period with 2000/98/Me to XP, but was it over a year long? It surely wouldn’t seem to make sense.

The “magic” Service Pack 1 for Windows XP was delivered on September 9, 2002, about 11 months after it became generally available. For Vista, SP1 came on February 4, 2008, literally just 5 days after its one-year anniversary of general availability. So while it was a little longer development time, it still launched five months before XP is to “die”. I think that’s plenty of time to get adjusted.

Wired has an interesting article on how the iPhone boosted smartphone sales for other manufacturers (most notably RIM and Palm). With the next version of the iPhone now released, you might be asking yourself

• What will Microsoft do to keep Apple from breaking into the enterprise smartphone market?
• Why haven’t I bought this new iPhone yet?
• What’s that pretty thing in the Crystal Ball?

Now might be a good time to analyze the potential impact Apple’s iPhone might have on Windows Mobile.

The current version of Windows Mobile is version 6.1… which is still based on Windows CE 5.2 despite the release of Windows CE 6.0 back in November of 2006, which is well over a year ago. Windows Mobile 7 will be based on either Windows CE 6 or a later version of Windows CE judging by its anticipated mid-to-late 2009 release. Since the last major Windows CE release, two iPhones have come along and, according to the people watching today’s WWDC keynote, eclipsed every smartphone in existence (we’ll disregard the argument that the iPhone is not a suitable enterprise tool for now).

Since the moment news of the first iPhone broke two Januarys ago, companies such as Meizu and HTC have tried to revamp the Windows Mobile interface with their own code, though only HTC has actually managed to push anything to the market. A number of threads discussing the new HTC Touch Pro have come and gone, with many people as-yet-unaffected by Mr. Jobs’ Reality Distortion Field seriously weighing the unreleased Touch (less so with its Diamond sibling) against the new iPhone and another HTC project, the Sony Ericsson XPERIA X1.

The impact of the iPhone is already visible in the preparation of new user interfaces for both Windows Mobile and RIM’s Blackberry (the Bold UI). However, with the announcement that iPhone v2 will carry full Exchange support, the latest iPhone is also making an attempt to invade the enterprise smartphone realm, and third party innovations for smartphones in this department typically have a high FAIL rate in catching on, so it’s up to Microsoft to keep itself awake and running. HTC pulled a lucky rabbit from its proverbial top-hat, but HTC’s experience lies in what most people in the Orient prefer with their phones: glitz, glamour, and lots of overly pretty animated functions, menus, spinning icons, and other similar user interface clutterings enhancements which missed the Longhorn boat back in 2004.

This gets me to what I think Microsoft might be forced to do with Apple’s growling 2ft-tall-and-growing-fast presence in front of it.

Background Applications won’t go away. Even though Apple had a fun jab at how background applications eat battery power and performance, I personally don’t believe Microsoft will let background applications go the way of the dodo. Instead, Microsoft will likely make enhancements to how Windows Mobile manages background applications. This will save battery power (good!) while making it less likely that your phone will be infected with spyware (good!), while also preserving backwards compatibility (good, but not as enthusiastically good).

A revamped user interface will likely be issued with Windows Mobile 7. While this has already been discussed many times in the past, I personally think the new UI will be developed in tandem with Windows 7’s User Interface. We’ve seen Windows 7’s poorly executed touch demo at D6 (I’ll keep my 50 cents Steve, thank you), but I think that Microsoft will keep a similar but highly condensed touch-centric user experience for Windows Mobile 7 for two reasons:

1. The iPhone has already made touch look cool, and with companies such as HTC pulling off some of the most ingenious touch interfaces , touch and gestures won’t be going away.
2. Microsoft has a history of keeping things looking alike (and yet disjointedly different at the same time) for the sake of branding. Windows Mobile 6 had this mildly Vista-esque feel through the use of gradients and glossed elements. On the other hand, this is a phone. One of the problems some people have with the iPhone is that while the user interface is great, the time it takes to go from one place to another (despite the presence of the home button) can get a bit annoying with the animations and other UI tidbits in place. In consumer environments, a glitzy UI is great, but in snappy business environments when CEOs are jumping from cabs and limousines to business meetings in skyscrapers while trying to arrange that multi-million (or billion) dollar merger during the only 30 second time slot available in the elevator trip to the top floor, the last thing that is needed are animations which eat time.

With that in mind, Windows 7 might be less of a festival of motion than Windows Mobile 6.1 with HTC’s TouchFLO, with a new interface likely catering to both businessmen and consumers alike.

Accelerated Development might split priority between Windows 7 and Windows Mobile 7. Should the two systems share a similar user interface, seeing Microsoft split its resources down the middle for both Windows and Windows Mobile might not be the largest surprise. One of Microsoft’s most successful areas is within the corporate sector, and with the iPhone trying to barge in, Microsoft might be much more inclined than before to put more emphasis on Windows Mobile development. With connectivity becoming the ultimate focus for Windows 7, seeing a heavy emphasis on connectivity between Windows Mobile, 7 and Windows 7 might be less of a shock now than it might’ve been, say, three to six months ago. This doesn’t mean we’ll see Windows 7 launch in 2009, nor does it mean that Windows 7 will come before the second half of next year (but it might). All it means is that more teams might be devoted to Windows Mobile 7, with collaboration between both Windows and Windows Mobile development climbing much higher than ever before. This could also mean that a number of Microsoft’s Windows 7 “pillars” will carry over into Windows Mobile.

Mind you, all of this is my own mindless speculation. The iPhone is not a crystal ball, I can’t see into the future, and the phone in the ball is an HTC Touch Pro. If you have any other ideas as to which directions Microsoft might take with Windows Mobile, post! Comments are below, but before you post, here’s a dose of irony, courtesy of Paul Thurrott.

In this post, I will show you a way to add custom buttons — like in the above image — to the commandbar by adding items to the registry. Unfortunately, not all buttons (e.g. New Folder) are possible via this way.

The registry key

We start by opening up regedit as administrator (start, type regedit and hit enter. Accept the UAC prompt if you have UAC enabled). Once inside regedit, we navigate to the following key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\explorer\FolderTypes

Under this key, you’ll see a list of numbers in the format of {de2b70ec-9bf7-4a93-bd3d-243f7881d492}. These numbers are CLSIDs and represent the special folders such as Documents, Music, Drives in Explorer.
Most of the CLSIDs can be figured out by clicking the registry key and looking at the CanonicalName. For example, {de2b70ec-9bf7-4a93-bd3d-243f7881d492} has its CanonicalName set to Directory.Contacts, so it is likely that these CLSID refers to the Contacts folder.

TaskNoItemsSelected

Under some of the CLSID registry keys, you’ll see another key named TaskNoItemsSelected. For example, {de2b70ec-9bf7-4a93-bd3d-243f7881d492} (the Contacts folder) has this subkey. If you further expand this key, you will see that it has numbered subkeys 0, 1, 2 and 3.
These subkeys actually contain a description of the buttons that are added to the commandbar when no item is selected in the Contacts folder.

Editing TaskNoItemsSelected

Before we can edit this registry key, you need to make sure you have the proper rights to do so. On a fresh install, only the installer can write or modify these registry keys.
If you plan on editing some of the button, take ownership of the FolderTypes registry key by right-clicking it and selecting Permissions. Next, click Advanced and go to the Owner tab. In here, you can select your own user or the Administrators group as the new owner. Before hitting OK, tick the bottom-most checkbox saying something along the lines of ‘Replace owner of the underlying objects’.
After doing this, you now have the proper rights to edit the FolderTypes.

We start by adding a new key under the {de2b70ec-9bf7-4a93-bd3d-243f7881d492}\TaskNoItemsSelected key. We name it 4, since 0 to 3 already exists.

The next thing we need to do is add another subkey under the 4 key, which needs to be a unique and long number (called a GUID). For generating GUIDs, we use the following tool: http://www.somacon.com/p113.php . Hit the Generate UUID/GUID button and copy the GUID to the clipboard. We got the {61C0D9CB-BB72-4013-8769-EC628B50C351} GUID from this tool.
Now we got a GUID, we add it under TaskNoItemsSelected\4 as a subkey, so we end up with the key:

\TasksNoItemsSelected\4\{61C0D9CB-BB72-4013-8769-EC628B50C351}

In this key, we add the following values in the right pane:

• (default), Character string, with a value of MyButton
• Icon, Expendable Character string, with a value of c:\windows\system32\calc.exe, 0
• InfoTip, Character string, with a value of My Custom Tooltip
• Title, Character string, with a value of My Custom Item

When done right, you’ll end up with:

These values let Explorer know how our button should look like. They are self-explanatory, except for Icon, which takes a string in the form of PathToExeOrDllFile, iconNumber. In our example, we tell Explorer to use the first Icon from the Calculator.

We now have told Explorer what our custom button looks like, but not what it should do. We do this by adding a the following subkeys to our custom-button key: shell\InvokeTask\command. In the command key, we change the (Default) value to the application we want to launch when the button is clicked. Let’s put in c:\windows\system32\calc.exe to launch calc.

If you did everything right, you ended up with the following key structure under FolderTypes:

Now, if you go into the Contacts folder, you will see a My Custom Item button, which, when clicked, will launch the Calculator.

Next time we will delve into the TasksItemsSelected list, which has some additional properties!

Another incident involved Neowin member Audioboxer buying a copy from eBay. His copy appears to have an Australian box, but a UK retail disk inside. According to his comments, the game runs by default at 1080p. The game also includes an installation screen, featuring Solid Snake smoking a cigarette, which burns and shrinks as the installation progresses. This is likely to cause controversy, especially in the UK, where smoking for theatrical performances is banned unless absolutely required for the performance. The installation screen also teases Xbox 360 owners, warning that the game is designed ” exclusively for use on the PlayStation 3″ .

NeoGAF member’s story and pictures

NeoWin member’s story and pictures

Yes that’s right, Builders! This week, AeroXperience was the first to get exclusive previews from Andreas Verhoeven’s Vista Style Builder.

I happen to be one of the fortunate people testing this application and giving feedback to Andreas mostly from an End-users Perspective. This Application does everything we could do before plus loads more. Whereas before we could only see numbers for images, now we will be looking at descriptions or, at the very least, class names. Instead of Hex-editing, we can insert/edit class properties using a language we can one day understand. At the moment, most of us will not understand what each Visual Style class does as they have not been publicly documented, so this is where I hope to step in and help.

I don’t want to Speak for Andreas as I am sure you will be hearing from him soon, but from what I gather, his plan is to make an application that the end-user can understand and use easily. Due to the large content of .msstyles, that will not be an easy thing to do. At the moment Avestyle is a Work in progress, but Andreas worked hard to make the application as usable and functional as possible. The actual core of the application works beautifully, but the UI is still in the process of being built. In the early builds, the Vista classes will be displayed in the application with the class name and a description.I am currently researching these classes to organize the Treeview in the application in a way where the user can find what he/she is looking for.

So Instead of researching image numbers and variant hex-edits, I will be focusing my attention on researching Vista class names and property names. This will most likely be more useful to us all as I am really confident that AveStyle is the way forward. Look out for more blog’s right here at AeroXperience about the new Customizing possibilities avestyle has to offer.

www.vistastylebuilder.com | Aves Pages | AeroXperience Forum Discussion

If anybody else would like to start getting familiar with class and property names, you will find the following links useful.

• Vista Visual Style Class names
• Property Identifiers

In a word, Nehalem is major. The motherboard they had to test on had bugs limiting performance in memory and GPU related areas, but Nehalem nonetheless manages to well and truly top-trump a higher-clocked Penryn in every test. A 2.66Ghz Nehalem boasts a 20-50% performance increase over the 3.2Ghz Penryn, currently the fastest processor on the market. And that’s not as high as this thing will clock.

Check out the article for yourself, but here are a few quotes to whet your apetite:

• “Memory accesses on Conroe/Penryn were quick due to Intel’s very aggressive prefetchers, memory accesses on Nehalem are just plain fast. Nehalem takes a little over 2/3 the time to complete a memory request as Penryn”
• “In short: Nehalem can get data out of memory quick like bunnies.”
• “Clock for clock, Nehalem is nearly 28% faster than Penryn in our DivX test. Even better is when you put this performance in perspective: at 2.66GHz Nehalem is faster than the fastest Penryn available today the Core 2 Extreme QX9770 running at 3.2GHz. At 3.2GHz, Nehalem will be fast”
• “It’s months before Nehalem’s launch and there’s already no equal in sight, it will take far more than Phenom to make this thing sweat.”

Read the Article at Anandtech