Wss3sdk: page layout and paging of mobile development

A wss Mobile Page Template is used to describe the page layout, and to place the ASP. NET 2.0 mobile control or the mobile control that comes with Sharepoint.
A single mobiledefatemplates. ascx file contains all rendering templates for mobile pages. The user control file is located in the local_drive: \ Program Files \ common files \ microsoft shared \ Web Server Extensions \ 12 \ template \ controltemplates directory. The mobile rendering framework template will be dynamically loaded from here. Place the custom. ascx file containing the rendering template definition to this directory and assign the appropriate control IDs to these controls. You can override the control that is released to the mobile page by default.
Page Layout

Each WSS mobile page is divided into three parts: Header, content, and footer, which are separated by a horizontal line. The page area contains the title of a website, list, or entry. The content area displays the list on the home page. Entries are displayed on the list view page and fields are displayed on the list item form page. The footer area contains the operation URL for the operation list items and navigation to other pages.
The default control in the mobile page refers to the rendering template defined in the mobiledefatemplates. ascx file, which defines the subtemplates and rendering controls used in the page. The header and footer areas are implemented from ASP. NETDevicespecificTemplate, which is always displayed even when the content area is paginated.
The following example shows the template used in the default homepage listing lists. aspx:

< Spmobile: spmobileform
Runat = "Server"  
Pagetype = "Homepage"  
Paginate = "True" >
< Devicespecific >
< Choice >
< Headertemplate >
< Spmobile: spmobilecontrolcontainer
Runat = "Server"  
Weightless = "True" >
< Spmobile: spmobilepagetitle
Runat = "Server"   />
< Spmobile: spmobilecomponent
Runat = "Server"  
Templatename = "Mobiledefaultseparator"   />
</ Spmobile: spmobilecontrolcontainer >
</ Headertemplate >
< Footertemplate >
< Spmobile: spmobilecontrolcontainer
Runat = "Server"  
Weightless = "True" >
< Spmobile: spmobilecomponent
Runat = "Server"  
Templatename = "Mobilepaginatenavigation"   />
< Spmobile: spmobilecomponent
Runat = "Server"  
Templatename = "Mobiledefaultseparator"   />
< Spmobile: spmobilepagenavigation
Runat = "Server"   />
</ Spmobile: spmobilecontrolcontainer >
</ Footertemplate >
</ Choice >
</ Devicespecific >
< Spmobile: spmobilepagecontents Runat = "Server"   />
</ Spmobile: spmobileform >

Mark Spmobilepagecontents Inserted in the body area of the page, which varies with the runtime and site templates, List Templates, or forms. When using other controls in this example Templatename Attribute to identify a rendering template defined in mobiledefatemplates. ascx.
Custom Controls
If you want to apply specific rendering to the homepage Based on the site template type, you can use different list views or list item forms based on the list template type by copying mobiledefatemplates. to add a custom rendering template.
To apply a specific rendering, you can define a renderingtemplate control so that its globally unique ID is in the following format:
Home Page
Mobile _ Sitetemplatename _ Homepage_title
Mobile _ Sitetemplatename _ Homepage_contents
Mobile _ Sitetemplatename _ Homepage_navigation
List View
Mobile _ Listtemplateid _ View_title
Mobile _ Listtemplateid _ View_contents
Mobile _ Listtemplateid _ View_navigation
List form
Mobile _Listtemplateid _ Newform_title
Mobile _ Listtemplateid _ Newform_contents
Mobile _ Listtemplateid _ Newform_navigation
Mobile _ Listtemplateid _ Editform_title
Mobile _ Listtemplateid _ Editform_contents
Mobile _ Listtemplateid _ Editform_navigation
Mobile _ Listtemplateid _ Dispform_title
Mobile _ Listtemplateid _ Dispform_contents
Mobile _ Listtemplateid _ Dispform_navigation
SetSitetemplatename Replace it with the ID number defined by the site, or its name (for example, STS Or MPs ). Set Listtemplateid Replace it with the list-type Integer ID number or the corresponding Splisttemplatetype Value.

Paging

WSS uses the paging mechanism of ASP. NET 2.0 to provide paging support in the content area of the following pages:

Bloghome. aspx
Dispform. aspx
Disppost. aspx
Mbllists. aspx
View. aspx
Viewcomment. aspx

For more information about ASP. NET paging, referASP. NET mobile controls: pagination.