Windows Phone development (15): Workshop and panorama Best Practices

 

Features of the two modes

Panorama
(1) richer User Experience
(2) item can set the screen direction to horizontal and support display of one additional Screen
(3) background images of any size can be used, and panorama automatically scales to fit the size.
(4) do not use application bar
Bytes
(1) Items that support more data volumes. Note that a maximum of 7 data records are recommended.
(2) Use more space to present data
(3) easier to use Code For example, selectedindex and selecteditem can be used for callback, but not panorama.
(4) The application bar can be used.

 

How to choose between them

Although panorama and ghost are similar, you need to pay attention to them when deciding which one to use.

With panorama, users can browse the content and provide an entry point for more operations. It is suitable for displaying information aggregated from multi-media sources. It should not be inProgramOnly a single independent operation is provided. It should implement the kind of guidance for more content and complete the user experience through the target-oriented function.

The contents control allows users to filter, sort, or organize content in programs. It is best to show only elements or data of the same type. The titles are described using natural language. This left-right switching navigation model enables users to find the information they need more efficiently.

 

 

 

 

Best practices

The following are suggestions for the panorama control:

Try to control the number of panoramaitems up to four.

Unless panoramaitems displays content, it is best to set the visibility attribute to collapsed to hide it.

By setting the orientation attribute to horizontal, panoramaitems can display content that is wider than the screen boundary.

The size of the background image is 800 pixels in height and 2000 pixels in width.

Set the title attribute of panorama as the name of the application on the Start interface.

Do not add animations or dynamically change the title size of panorama.

The following are suggestions for the render control:

Considering the performance, reduce the number of effectitem as much as possible.

Try to load the content in real time, instead of loading all the content at the beginning of the program.

Use the widgets control to display elements or data of the same type.

Do not use the navigation control to implement functions similar to the navigation tool.

Do not use the application bar to provide navigation. If the effect of navigation is used, it is abuse.