Windows Media Player 11 SDK Ensuring that Windows Media Player Opens the HTMLView ContentÂ
.gif)
| Previous | Next |
Ensuring that Windows Media Player Opens the HTMLView Content
Currently, Windows Media Player 9 Series and Windows Media Player 10 are the only players that support the HTMLView parameter in .asx files. This means you should take steps to ensure that your HTMLView content plays back in these versions of Windows Media Player.
You must first determine whether Windows Media Player 9 Series or Windows Media Player 10 is installed on the user's computer. The Windows Media Player SDK includes a comprehensive sample that demonstrates how to detect different versions of Windows Media Player in different Web browsers. Although a complete analysis of the detection sample is beyond the scope of this section, there are some basic steps you can take to determine which version of Windows Media Player the user's computer is running.
In its simplest form, detecting Windows Media Player involves embedding the Player control in the Web page that links to your HTMLView content and then inspecting the value retrieved by the Player.versionInfo property. Once you have verified that the user has Windows Media Player 9 Series or Windows Media Player 10 installed, you can use the Player.openPlayer method to open the content in the full-mode Player. The openPlayer method ensures that your content is initially displayed in the Now Playing feature of the full-mode Player, rather than in a skin, in mini Player mode, or in another player that has registered itself as the default program for files with an .asx file name extension, but doesn't support HTMLView. Once the content is displayed, however, the user has complete control of Windows Media Player, meaning that he or she can choose to display a feature other than Now Playing, switch to skin mode, or even quit the Player.
The following example code creates a Web page for Internet Explorer. This page opens an .asx file, which specifies an HTMLView Web page that appears in the full-mode Player when Windows Media Player 9 Series or later is installed.
The code in the preceding example embeds the Windows Media Player control with the uiMode property set to "invisible" and the Player height and width attributes set to zero. This is because the Web page does not require the Player control user interface to be displayed initially—it only requires access to the Player object model. The page also displays an input button that enables the user to play the .asx file.
When the user clicks the Play ASX button, the Microsoft JScript function PlayASX runs. This function first retrieves the value for the Player versionInfo property, using the JScript parseInt method to inspect the numerical value of the string retrieved. If the numerical value is greater than or equal to 9 (meaning that the user has Windows Media Player 9 Series installed), the script code calls the openPlayer method, passing the URL of the .asx file that contains the HTMLView parameter. This method opens the .asx file using Windows Media Player in full mode, plays the digital media content in the .asx playlist, and displays the HTMLView Web-based content in the Now Playing feature.
If the numerical value of the version string is not greater than or equal to 9 (meaning that the user does not have Windows Media Player 9 Series or later installed on his or her computer), the script code changes the uiMode of the Player control to "full", sets a new width and height for the control, and then opens the .asx file in the embedded Player by specifying a value for the URL property. When this happens, the digital media content plays in the Web page, but any HTMLView values specified in the .asx file are ignored.
How content is played back when the user does not have Windows Media Player 9 Series or Windows Media Player 10 installed is up to you. The preceding example shows how to specify that the content play in the Web page instead of the full-mode Player, ignoring any HTMLView content in the process. There are other approaches you might take. For example, you could prompt the user to install a newer version of Windows Media Player, making that version of the Player a requirement for playing back your digital media content.
See Also
| Previous | Next |