16.01.2013 Views

Microsoft Sharepoint Products and Technologies Resource Kit eBook

Microsoft Sharepoint Products and Technologies Resource Kit eBook

Microsoft Sharepoint Products and Technologies Resource Kit eBook

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Chapter 31: Working with Web Parts 831<br />

■ Area Details. Used to display area details such as description <strong>and</strong> contact<br />

details. By default, this property is placed on many of the area Web Pages <strong>and</strong><br />

has custom properties to show the subtitle. It allows you to fix the image width<br />

<strong>and</strong> height in pixels, <strong>and</strong> you can decide whether you want the picture of the<br />

area’s contact to be displayed.<br />

■ Grouped Listings. Used to display listings—that is, target items held within<br />

a Portal Listings list. This Web Part is included in most area templates. This<br />

might not be immediately obvious because the title for the Web Part when it is<br />

included on area pages would be different or have no title at all. The custom<br />

properties include Maximum Number Of Listings, Fixed Image Width And<br />

Height In Pixels, Ignore Listings In Anchor Area, Subarea Layers, Display Template,<br />

Group By, Sort Listings By, Sort Direction, Display Column, Highlights<br />

Visibility, More Info Link Text Label, More Info Link URL, Description Trim<br />

Size, <strong>and</strong> Show Subtitle. This Web Part also has two custom properties—<br />

Cache Timeout <strong>and</strong> Cache Per User—which appear under the Miscellaneous<br />

group heading. A Web Part can be designed to store frequently used data in<br />

cache on a shared (all users) basis or on a per-user basis to expedite data<br />

retrieval. If the data is to be stored in cache, you can also specify the timeout<br />

value, which specifies the length of time during which the Web server should<br />

retrieve the data from cache. If the time has expired, the Web server should reference<br />

the data source, which could be the original .aspx file or the content<br />

database. The data will then be copied into the cache <strong>and</strong> would be valid for<br />

the timeout value specified. The Web Part cache can be configured to be either<br />

held in memory or in an SQL database, on a Virtual Server basis, by configuring<br />

the Web.config file; however, static Web Parts can use cache only if it is memory.<br />

A decision on Web Parts <strong>and</strong> caching should be part of the design process<br />

<strong>and</strong> involve both developers <strong>and</strong> administrators. For more information, see the<br />

“Web Parts <strong>and</strong> Caching” topic in the SharePoint Portal Server 2003 or Windows<br />

SharePoint Services SDK. Other Web Parts that are based on the Group<br />

Listings Web Part <strong>and</strong> described in this chapter are News, News Area, Links For<br />

You, <strong>and</strong> News For You.<br />

■ News. This Web Part is placed by default on a portal site’s home page <strong>and</strong><br />

the News Web Part Page. It is based on the Grouped Listings Web Part—that is,<br />

it will display links contained in the Portal Listing List <strong>and</strong> has the same custom<br />

properties as stated earlier. The maximum number of Listings is set to five. This<br />

Web Part uses the exp<strong>and</strong>ed display template <strong>and</strong> sorts listings by creation<br />

date. If you place this Web Part on a different area page, it would not show the<br />

items listed in the News Portal Listing list. To configure this Web Part to display<br />

the News links, you would need to change the location Home > News by using<br />

the link in the Current Area Override section, which is how this Web Part is<br />

configured on a portal site’s home page.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!