Wss3sdk How to customize the mobile home page

This section provides an overview of the basic process for customizing the Windows SharePoint Services 3.0 home page that a mobile device accesses. Detailed steps to participate in the following walkthrough article.

As previously described in the Mobile page rendering mechanism section, each control in the header, content area, footer (navigation area) of the mobile homepage causes a chained invocation, which is initiated by the following 3 template selector controls.

spmobilewebtitle-Select the Renderingtemplate control that is used to render the header part.

spmobilewebcontents-Select the Renderingtemplate control for the backbone section.

spmobilewebnavigation-Select the Renderingtemplate Control for the footer section.

One of the objects of these classes selects a Renderingtemplate object based on the site type of the requested page, such as Sts,blog or custom site. That is, you can customize mobile home pages for specific types of Web sites. For example, you can display a greeting message on the mobile home page of all STS-type sites.

Attention:

Mps,centeraladmin and wiki sites do not support access from mobile devices.

These controls search for Renderingtemplate IDs in the following formats:

Mobile_ Sitetypeid _homepage_ Pagearea

Where Sitetypeid can be an STS, a BLOG, or a custom site-defined ID number, and Pagearea specifies Title, Contents, or navigation to represent the area in the rendered page.

Based on the type of the current Web site, the Spmobilewebtitle control determines which Renderingtemplate object will render to the header area of the mobile home page. For example, the Spmobilewebtitle object will attempt to render an STS home page on a mobile device using a render control with an ID of mobile_sts_homepage_title. If this ID is not found, he will use the control with the ID mobile_defaut_homepage_title.

Windows SharePoint Services 3.0 does not provide a renderingtemplate element with an ID of mobile_sts_homepage_title by default, and you can create one.

Under this rendering mechanism, creating a mobile home page that contains a custom header (Title), content body, or footer (navigation area) actually creates a rendering template with the ID of the template selector control to search for the corresponding page area.

Existing Renderingtemplate

When WSS is installed, the following two renderingtemplates for the mobile home page already exist in Mobiledefaulttemplates.ascx.

Mobile_blog_homepage_navigation

Mobile_sts_homepage_contents

You should not modify the Mobiledefaulttemplates.ascx file. You can create a new renderingtemplate element (in your own. ascx file) and only use the same ID as the rendered control that already exists. However, there is a risk that this could disrupt other solutions that rely on the original Renderingtemplate object that is deployed in WSS.