Справочник Пользователя для Wiley Professional Windows Phone 7 Application Development 978-0-470-89166-7
Модели
978-0-470-89166-7
Chassis Design
So far you know that hardware manufacturers can optionally include a keyboard, but what else can they
modify? In the past this was quite an open - ended discussion as manufacturers could build a device to
meet a certain price point. For example, for high - end devices, they could include GPS, an accelerometer,
and a high - resolution camera; a low - end device may only have a T9 keypad and no camera at all.
Even the number and layout of physical hardware buttons could change between devices. Of course,
all these options come at a cost, and the fi rst place this took hold was with developers. When building
applications, developers were seldom able to rely on a particular hardware feature being present.
Instead, you would typically either query an API to determine if hardware existed, or simply attempt
to address the hardware. Failure or an exception would indicate the lack of supported hardware.
modify? In the past this was quite an open - ended discussion as manufacturers could build a device to
meet a certain price point. For example, for high - end devices, they could include GPS, an accelerometer,
and a high - resolution camera; a low - end device may only have a T9 keypad and no camera at all.
Even the number and layout of physical hardware buttons could change between devices. Of course,
all these options come at a cost, and the fi rst place this took hold was with developers. When building
applications, developers were seldom able to rely on a particular hardware feature being present.
Instead, you would typically either query an API to determine if hardware existed, or simply attempt
to address the hardware. Failure or an exception would indicate the lack of supported hardware.
After the application had been developed, the problem was transposed to the end users. They would
see a product advertised as being compatible with Windows Mobile and purchase it, only to discover
that it required hardware that they didn ’ t have. No two Windows Mobile devices were alike. When
it came to Marketplace for Windows Mobile, Microsoft acknowledged this issue, and as part of
application submission, developers had to indicate what device capabilities their application required.
The Marketplace client running on the device would then restrict the list of applications to only those
that matched the device capabilities.
see a product advertised as being compatible with Windows Mobile and purchase it, only to discover
that it required hardware that they didn ’ t have. No two Windows Mobile devices were alike. When
it came to Marketplace for Windows Mobile, Microsoft acknowledged this issue, and as part of
application submission, developers had to indicate what device capabilities their application required.
The Marketplace client running on the device would then restrict the list of applications to only those
that matched the device capabilities.
For Windows Phone, Microsoft has taken the proactive position of enforcing a set of requirements
around device capabilities. This has been achieved by taking the traditional minimum hardware
specifi cations and turning them into what Microsoft calls a chassis design . This specifi es the external
buttons, and in some cases their location, and the inclusion of particular hardware features such as Wi - Fi,
GPS, accelerometer, compass, camera, light and proximity sensors, and the ability to vibrate. A device
that doesn ’ t include all of the features dictated by a chassis design cannot be called a Windows Phone.
around device capabilities. This has been achieved by taking the traditional minimum hardware
specifi cations and turning them into what Microsoft calls a chassis design . This specifi es the external
buttons, and in some cases their location, and the inclusion of particular hardware features such as Wi - Fi,
GPS, accelerometer, compass, camera, light and proximity sensors, and the ability to vibrate. A device
that doesn ’ t include all of the features dictated by a chassis design cannot be called a Windows Phone.
On the front - facing side of a Windows Phone there will be three buttons: Back, Start, and Search.
There will also be dedicated camera, power, and volume controls. Figure 1 - 1 shows an example
device in both portrait and landscape, illustrating the relative positions of the three front - facing
hardware buttons.
There will also be dedicated camera, power, and volume controls. Figure 1 - 1 shows an example
device in both portrait and landscape, illustrating the relative positions of the three front - facing
hardware buttons.
FIGURE 1 - 1
Minimum Specifi cations
❘
3
CH001.indd 3
CH001.indd 3
10/6/10 9:13:11 PM
10/6/10 9:13:11 PM