Wss3sdk How to customize Mobile's list view and form page

This section provides an overview of the basic process for customizing the Windows SharePoint Services 3.0 list view and form pages that mobile devices access. 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.

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

spmobilelistcontents-Select the Renderingtemplate control for the backbone section.

spmobilelistnavigation-Select the Renderingtemplate Control for the footer section.

One of the objects of these classes selects a Renderingtemplate object based on the current list type, such as notifications or other custom list types, and the type of the page.

These controls search for Renderingtemplate IDs in the following formats:

Mobile_ Listtypeid _ pagetype _ Pagearea

Where Listtypeid can be the ID number of the current list type (for example, 105), or it can be a value of the Splisttemplatetype enumeration (such as contacts). There are two ways to define a list type ID:

If the list is specified in the ONET.xml site definition file as part of the site type, the Listtypeid value is the Type property value of the list element in ONET.xml. The file is located under this directory: Local_drive:\program files\common Files\Microsoft Shared\Web server Extensions\12\template\sitetemplates \site_type\xml

If the list is added to the web through the UI, that is, by creating a new (list) page, Listtypeid is the ID of the list type that was originally used as the basis for the new list type. This depends on how the user clicks on the Create page (create.aspx) and which list type is clicked to enter the new page.

PageType can be VIEw, NewForm, EditForm, Dispform or Deletepage.

Pagearea can be Title, contents or navigation.

If the ID of the renderingtemplate element specified by the current list type is not found, he will use the control with the ID mobile_default_pagetype_pagearea.

Create a mobile List view or form page that contains a custom header (Title), content body, or footer (navigation area) in fact, you only need to create a rendering template with the ID of the template selector control that corresponds to the page area to search for.

Existing Renderingtemplate

When Windows SharePoint Services 3.0 is installed, the following two renderingtemplates for the mobile home page already exist in Mobiledefaulttemplates.ascx.

Mobile_comments_deletepage_navigation

Mobile_comments_view_navigation

Mobile_discussionboard_dispform_contents

Mobile_discussionboard_editform_contents

Mobile_discussionboard_editform_navigation

Mobile_discussionboard_newform_navigation

Mobile_documentlibrary_view_navigation

Mobile_events_dispform_navigation

Mobile_events_editform_navigation