Windows Phone 7 core controls panorama and ghost

Recently, I was working on an azure project where server-side data is stored on Microsoft's cloud. Clients include PCs and smartphones, some of which are Windows Phone 7 clients.

Most applications in the project use the Panorama and ghost controls. The following are their main features:

◆ Simple XAML and programming interfaces
◆ Fully supports data binding, content template attributes, and project container styles
◆ Built-in black and white skin styles
◆ Built-in touch navigation allows you to quickly slide the control and locate the specified item
◆ Beautiful transition animations are provided when pages or content items are slide by navigation
◆ Powerful Scalability: users can expand their functions by means of events, visualization status, and redefinition of templates.
◆ Native support of Visual Studio 2010

The difference between the panorama control and the ghost control is that the ghost control displays multiple different pages, while the panorama control divides a page into multiple child pages that can be animated, like a horizontal canvas, the screen side is extended. Unlike the ghost control, the panorama control has a background image expanded to all sub-pages, which looks like a wide screen.

The slider is generally used for different display forms of the same content, and the background does not slide. To some extent, it can be said that it is a substitute for the tab control, while panorama is a relatively wide display of content that can not be used when the screen is displayed, the background slides along when sliding,

The following figure shows the effect of compaction.

The following is the effect of panorama:

Msdn documentation:
Panorama and describoth controls
• Items can be added in XAML
• Items can be added in code, items. Add (New effectitem (...)) Or items. Add (New panoramaitem (...))
• Itemssource can be used for data binding
• Do not support alternative types of items: registrcontrols must use specified titem, Panorama must have panoramaitem
Differences
• Panorama exposes a defaultitem Property

• Selectedindex and selecteditem are settable in Hangzhou but not in Panorama

In addition, it is strongly recommended that you use a real machine for debugging, which is much better than debugging on a simulator. The memory occupied by the simulator (I used MB of memory after I started the project) and started slowly.

When deployed on a real machine, do not lock the screen; otherwise, the error message "failed to connect to device as it is pin locked" appears.