Last week, Paul Thurrott wrote a post entitled, “The Dark Side of Windows Vista RC1“, in which he discusses a few things that he doesn’t like about Vista.
And the first item in his article talks about the DVD Maker UI. Paul’s complaint is that the “back” button for wizards has migrated from the previous location at the bottom of the wizard to the upper-left corner of the window, and morphed into an “IE-style button”.
This part of the DVD Maker UI comes from the new Aero Wizard framework (for those of you using wizards, you add PSH_AEROWIZARD to your wizard flags to use the new framework…). I agree with Paul about the location and style of the back button, and gave feedback to the Wizard UI folks about that issue.
The second point that Paul brings up is the behavior of ALT + Right Arrow. As Paul notes, doing this will start the burn process, which I agree may be a bit of a surprise, though unless you’re really slow in hitting cancel, you won’t make a coaster (ie junk disc) as there’s a lot of work to do before we start writing the disc.
This behavior came from our goal of creating a clean user experience.
There are two required steps for creating a DVD with DVD Maker. First, you need to add some content, and then you need to select a style (you can skip selecting if you like “Full Screen”). At that point, you can pick burn, and you’re done.
Then there are the optional actions, customization and previewing. One choice would have been to put the customization pages in line after the choose style pages (in traditional wizard fashion), but that adds two or three pages for every DVD, and implies to the user that they need to do something on each of those pages. It also would have left us trying to fit our interactive preview somewhere in the UI.
Instead, we chose to implement the customization and preview pages the way that dialog boxes work – you go to them, make your changes, and then either accept or roll back the changes you made.
I think that we made the right tradeoff in this case.
It’s true, however, that DVD Maker is bigger and more complex than the other wizards I’ve seen, and the constraints of the wizard framework therefore had more impact. If we had to do it again, we might perhaps choose to make DVD Maker an application rather than a wizard.