Module 2: Using Web Parts and Digital Dashboard Components

Contents Overview 1 Using Web Part Schema Content Using Web Part Schema Basic Properties 21 Examining the Digital Dashboard Factory 22 Using the Digital Dashboard User Interface 26

Contents

Overview 1

Using Web Part Schema Content

Using Web Part Schema Basic Properties 21

Examining the Digital Dashboard Factory 22

Using the Digital Dashboard User

Interface 26

Demonstration: Accessing the Digital

Lab A: Working with Web Part Properties 34

Review 43

Module 2: Using Web Parts and Digital

Dashboard Components

to represent any real individual, company, product, or event, unless otherwise noted Complying with all applicable copyright laws is the responsibility of the user No part of this document may

be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Microsoft Corporation If, however, your only means of access is electronic, permission to print one copy is hereby granted

Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property

 2000 Microsoft Corporation All rights reserved

Microsoft, Active Directory, ActiveX, BackOffice, FrontPage, NetMeeting , Outlook, PivotTable ,

PowerPoint, Visual Basic, Visual InterDev, Visual Studio, Windows, Windows Media, and Windows NT are either registered trademarks or trademarks of Microsoft Corporation in the U.S.A and/or other countries

Other product and company names mentioned herein may be the trademarks of their respective owners

Project Lead and Instructional Designer: Josh Barnhill

Technical Lead: Chris Howd

Technical Contributor: Howard Crow

Program Manager: Phil Clark

Graphic Artist: Andrea Heuston (Artitudes Layout and Design)

Editing Manager: Lynette Skinner

Editor: Elsa Leavitt

Copy Editor: Kathy Toney (S&T Consulting)

Production Manager: Miracle Davis

Production Coordinator: Jenny Boe

Production Tools Specialist: Julie Challenger

Production Support: Ed Casper (S&T Consulting)

Test Manager: Sid Benavente

Testing Developer: Greg Stemp (S&T OnSite)

Courseware Testing: Testing, Testing 123

Creative Director, Media/Sim Services: David Mahlmann

Web Development Lead: Lisa Pease

CD Build Specialist: David Myka (S&T Consulting)

Manufacturing Manager: Rick Terek

Operations Coordinator: John Williams

Manufacturing Support: Laura King; Kathy Hershey

Lead Product Manager, Release Management: Bo Galford

Lead Product Manager, Knowledge Management Solutions: Janet Wilson

Group Manager, Courseware Infrastructure: David Bramble

Group Product Manager, Content Development: Dean Murray

General Manager: Robert Stewart

Instructor Notes

This module provides students with an understanding of Web Parts and digital

dashboard components

At the end of this module, students will be able to:

! Define Web Part, Web Part schema, and digital dashboard folders

! Use content properties of the Web Part schema

! Use execution properties of the Web Part schema

! Use appearance properties of the Web Part schema

! Use basic properties of the Web Part schema

! Describe the purpose of the digital dashboard factory

! Describe the digital dashboard user interface (UI)

Materials and Preparation

This section provides you with the required materials and preparation tasks that are needed to teach this module

Required Materials

To teach this module, you need the following materials:

! Microsoft® PowerPoint® file 2017a_02.ppt

! Module 2, “Using Web Parts and Digital Dashboard Components”

Preparation Tasks

To prepare for this module, you should:

! Read all of the materials for this module

! Read the instructor notes and margin notes for the module

! Complete the lab

Presentation:

45 Minutes

Lab:

30 Minutes

Module Strategy

Use the following strategy to present this module:

! Understanding Web Parts Define Web Part, Web Part schema, and digital dashboard folders

! Using Web Part Schema Content Properties

Explain how to use the Content, ContentLink, and ContentType

properties of the Web Part schema

! Using Web Part Schema Execution Properties

Explain how to use the MasterPartLink, CustomizationLink, CacheBehavior, and CacheTimeout properties, and additional useful

execution properties of the Web Part schema

! Using Web Part Schema Appearance Properties

Explain how to use the AllowMinimize and FrameState properties, and

additional useful appearance properties of the Web Part schema

! Using Web Part Schema Basic Properties

Explain how to use the Title, Description, Namespace, and LastModified

properties of the Web Part schema

! Examining the Digital Dashboard Factory Describe how the digital dashboard factory initializes Web Parts Explain how the digital dashboard factory processes Web content Describe the important property interactions of the Web Part schema

! Using the Digital Dashboard User Interface Explain how to access the digital dashboard customization pages Describe the title and navigation areas and the five digital dashboard zones

Overview

! Understanding Web Parts

! Using Web Part Schema Content Properties

! Using Web Part Schema Execution Properties

! Using Web Part Schema Appearance Properties

! Using Web Part Schema Basic Properties

! Examining the Digital Dashboard Factory

! Using the Digital Dashboard User Interface

At the end of this module, you will be able to:

! Define Web Part, Web Part schema, and digital dashboard folders

! Use the content properties of the Web Part schema

! Use the execution properties of the Web Part schema

! Use the appearance properties of the Web Part schema

! Use the basic properties of the Web Part schema

! Describe the purpose of the digital dashboard factory

! Describe the digital dashboard user interface (UI)

In this module, you will learn

about using Web Parts and

digital dashboard

components

# Understanding Web Parts

! Defining Web Part

! Defining Web Part Schema

! Defining Digital Dashboard Folder

Web Parts are the building blocks that digital dashboard factories use to create the digital dashboard view that users see

The following topics define Web Parts, the Web Part schema, and the digital dashboard folder and how they relate to each other

For information about creating Web Parts, see module 3, “Creating Web

Parts” in course 2017A, Creating Web Parts for Digital Dashboards

Slide Objective

To outline this topic

Lead-in

Web Parts form the building

blocks of digital dashboards

and can contain almost any

type of Web content

The “Understanding Web

Parts” section of this module

begins with some review

material on Web Parts, but

then moves quickly into the

Web Part schema topic Do

not spend more time on the

“Defining Web Part” topic

than is necessary

Note

Defining Web Part

Apply property schema

The content of the Web Part can be as complex as streaming video or as simple

as a string of text Most Web Parts provide their content by using Microsoft®ActiveX® Controls (such as the Microsoft Outlook® view control or Microsoft Office Web Components), data access pages, or existing Web pages

Slide Objective

To show that Web Parts

apply a set of properties to

Defining Web Part Schema

Web Part

Schema

Web Part Schema

Basic properties Appearance properties Execution properties

Content properties

The power and versatility of Web Parts come from the Web Part schema, which

is a set of properties that establish how Web Parts are displayed in a digital dashboard The schema properties also define the behavior of Web Parts, such

as how often they are refreshed and whether they cache their content to the digital dashboard server You set these properties when you create Web Parts, and they are stored as part of the XML code within a Web Part file Some properties are user specific, meaning that these properties can be modified by digital dashboard users to customize a digital dashboard to meet their personal preferences

Content Class

To ensure that digital dashboard factories interpret Web Parts in a consistent fashion, a content class named “urn:schemas-microsoft-com:office:Webpart” has been defined (A content class is a collection of data that describes an object’s attributes and the current state of the object, in this case a Web Part.) Any Web Part that you create by using the Web Part schema belongs to this content class

Slide Objective

To show how the Web Part

schema affects the

appearance of Web Parts

when they are rendered in a

digital dashboard view

Lead-in

Required and optional

properties of the Web Part

schema enable Web Part

authors to specify the

behavior of Web Parts

Properties are either

user-specific or view-user-specific

(view-specific properties

contain metadata for the

Web Part) For details on

why this differentiation is

necessary, see the

“Building Web Parts for the

Digital Dashboard” white

paper supplied with the

Digital Dashboard Resource

Kit

Digital dashboard

administrators can create

their own digital dashboard

factories, based on the

default digital dashboard

factory, that take advantage

of additional properties

Check digital dashboard

forums periodically for

updates on this advanced

topic

The Web Part schema defines a number of standard properties for a Web Part Some of these properties are required for the digital dashboard factory to render

a Web Part, whereas others are not Developers can attach additional properties

to a given Web Part, but the values of any additional properties will not be referenced by the default digital dashboard factory supplied with the Digital Dashboard Resource Kit 2.0 and will not be part of the base content class Extending the default digital dashboard factory engine to take advantage of these additional properties is not recommended and is not covered in this course

Nothing about the Web Part schema restricts its use to the data stores developed by Microsoft It is possible to design storage for a Web Part in many different kinds of data stores, and to enable digital dashboard factories to read Web Parts from any data store that supports the Web Distributed Authoring and Versioning (WebDAV) protocol

Categories of Web Part Schema Properties

The properties of the Web Part schema can be divided into four general categories:

! Content properties These properties define the content location, content

value, and content type for a Web Part

! Execution properties These properties control the behavior of Web Parts

within a digital dashboard

! Appearance properties These properties control the visual interface

presented to digital dashboard users

! Basic properties These properties define basic metadata for a Web Part

Note

For all property definitions, if

a particular item does not

have a value defined for the

property, a digital dashboard

factory uses the default

value for the property

Defining Digital Dashboard Folder

Property Result Result AutoUpdate Determines whether Web Parts are updated with the values of a master Web PartDetermines whether Web Parts are updated with the values of a master Web PartDashboardOrder Indicates the location of this digital dashboard in the navigation user interface relative to other digital dashboardsIndicates the location of this digital dashboard in the navigation user interface relative to other digital dashboardsDisplayTitle Indicates whether the digital dashboard view should display the title bar of the digital dashboardIndicates whether the digital dashboard view should display the title bar of the digital dashboardMergeSubDashboards Determines whether subdashboards are merged into the digital dashboard view, allowing navigation between themDetermines whether subdashboards are merged into the digital dashboard view, allowing navigation between themRefreshInterval Specifies how frequently the entire digital dashboard is refreshed

Stylesheet Embedded style sheet that defines the digital dashboard view

A digital dashboard folder is a specialized folder that contains Web Parts and must be located in a WebDAV-compatible data store It has a custom property schema—the digital dashboard schema—which applies to the digital dashboard folder and all of the Web Parts in the folder You can customize digital

dashboards by modifying the properties of the digital dashboard schema

The Title, Description, and LastModified properties serve the same purpose in

the digital dashboard schema as they do in the Web Part schema The following table defines some additional digital dashboard schema properties

Property name Description

AutoUpdate Determines whether and how often Web Parts are updated

with the values of a master Web Part DashboardOrder Indicates the location of this digital dashboard in the

navigation UI relative to other digital dashboards DisplayTitle Indicates whether the digital dashboard view should

display the title bar of the digital dashboard MergeSubDashboards Determines whether subdashboards are accessible from the

digital dashboard view, allowing navigation between multiple digital dashboards

RefreshInterval Specifies how frequently the entire digital dashboard is

refreshed Stylesheet Defines the digital dashboard view by means of an

embedded style sheet

For more information about the digital dashboard schema, see the Digital Dashboard Schema Reference document included on the Student Materials

compact disc

Slide Objective

To show how properties of

the digital dashboard

schema affect the

appearance of a digital

dashboard

Lead-in

Digital dashboard folders

contain Web Parts and

enable you to customize

properties of digital

dashboards

This one-day course

focuses on creating Web

Parts and moves very

quickly through the topic of

digital dashboard folders

Make sure that the students

know that there is more

material on creating digital

dashboard folders and the

digital dashboard schema in

the Digital Dashboard

Resource Kit

Note

# Using Web Part Schema Content Properties

! Using the ContentLink and Content Properties

! Using the ContentType Property

You use the content group properties of the Web Part schema to define the Web Part content that is described, controlled, and displayed by using the other

property groups The content properties are Content, ContentLink, and ContentType

Slide Objective

To outline this topic

Lead-in

You use the content

properties of the Web Part

schema to work with

information from other

property groups

Using the ContentLink and Content Properties

Schema

Web Part Schema

Content property property

ContentLink

Content of the Web Part Hyperlink to content

Web Parts specify their content in one of two ways, either by linking to the

content by using the ContentLink property or by embedding the content directly in the Web Part by using the Content property

Digital dashboard factories check the ContentLink property first and use its value to include content if a link is specified If the ContentLink property has

no value, or if the digital dashboard factory encounters an error when attempting to access the Uniform Resource Locator (URL), the digital

dashboard factory uses the value in the Content property for the current digital

to obtain the content for the Web Part and uses the Content property only when

this URL does not return content If the digital dashboard factory fails to access

a URL that is specified by the ContentLink property and there is no value in the Content property, then an error message will be displayed

Using the Content Property The Content property contains embedded content that is used by the Web Part when ContentLink is either not used or when the connection to linked content fails The Content property might or might not contain a value If this property does not contain a value, then the ContentLink property must contain a value

for the Web Part to display content

You can use the Content property to either embed the desired content in the

Web Part or to house error text that a digital dashboard displays if the digital

dashboard factory fails to access a URL that is specified by the ContentLink

You use the ContentLink

property to specify a Web

location from which to

retrieve content, and you

use the Content property to

specify the content of a Web

enable the digital dashboard

factory to interpret linked

content correctly

If you want to display

current or live content, you

should set the ContentLink

property

Using the ContentType Property

Schema

Web Part Schema

property property property

the Web Part correctly

Using the ContentType Property The ContentType property indicates which type of content is embedded in a

Web Part Web Part content can be written in HTML, XML, JavaScript, or Microsoft Visual Basic® Scripting Edition (VBScript) code A digital dashboard factory must determine which type of content it is accessing to process it correctly

Possible Property Values The following table lists the possible values for the ContentType property and

indicates the manner in which the digital dashboard factory interprets each value

Value in schema Value in XML Meaning

transformed through the XSL or XSLLink

You use the ContentType

property to specify the type

of embedded content

Digital dashboard factories

handle values outside this

range as an “unknown” type

so that you can extend this

list for specialized

implementations

If the Content property contains VBScript or JavaScript code, the digital

dashboard factory must allow the script to generate content back to the digital dashboard factory because the digital dashboard factory has to process the content generated by the script or it will not be displayed on the digital dashboard view The process of getting script-generated content back to the

digital dashboard factory is accomplished by including a getContent function

within the script

For more information on how VBScript and JavaScript content types are

processed, see the Web Parts Schema Reference document included on the

Student Materials compact disc

Note

# Using Web Part Schema Execution Properties

! Using the MasterPartLink and CustomizationLink Properties

! Using the CacheBehavior and CacheTimeout Properties

! Using Additional Execution Properties

You use the execution properties of the Web Part schema to control the behavior of Web Parts within a digital dashboard The execution properties

include the MasterPartLink, CustomizationLink, CacheBehavior, CacheTimeout, PartStorage (a user-specific property), RefreshInterval, RequiresIsolation, XSL, and XSLLink properties

Slide Objective

To outline this topic

Lead-in

You use the execution

properties of the Web Part

schema to control the Web

Parts within a digital

dashboard

The PartStorage property is

the only user-specific

property in the execution

property group The

property will be discussed in

the last topic of this section

Using the MasterPartLink and CustomizationLink Properties

~

Schema

Web Part Schema

Specifies the URL for a page to customize the Web Part’s content

Specifies the master version of a Web Part

CustomizationLink

property property

MasterPartLink

The MasterParkLink property enables a digital dashboard factory to obtain the master version of the Web Part, and the CustomizationLink property indicates

the URL for a Web page that can be used to customize the Web Part’s content

Using the MasterPartLink Property When specified, the MasterPartLink property contains a URL to the master

version of a Web Part, or is the primary key value in the master version of a Web Part if the data store does not use Hypertext Transfer Protocol (HTTP)

references A master version is a copy of a Web Part that can be used to update

the non-user–specific properties of distributed Web Parts to ensure that these properties reflect the most up-to-date version of the original Web Part If the

MasterPartLink property has a value, the digital dashboard factory follows

this URL to obtain the master version of the Web Part and uses that instance’s non-user–specific properties when rendering the Web Part If the master version has been modified more recently than the current instance, the digital dashboard factory updates the non-user–specific properties of the distributed Web Part (the current instance of the Web Part being processed) to match the master version

Using the CustomizationLink Property

When specified, this property indicates the URL for a Web page to customize the Web Part’s content For example, a Web Part listing a number of stocks and

their current prices can include a CustomizationLink property to provide a

method for customizing which stock symbols are displayed by the Web Part The hyperlink will usually point to the Web site that is supplying the Web Part’s content However, it can point to anywhere, including to another Web Part, or even to the same Web Part, passing a parameter indicating

specify the master version

of a Web Part, and you use

the CustomizationLink

property to specify the URL

for a Web page to

customize the Web Part’s

content

Customization pages should

include a Submit button that

commits changes and

returns users to the digital

dashboard view

Customization pages can do

this by using VBScript or

JavaScript code to go back

one page (for example, by

using the Microsoft Internet

Explorer History object’s

Back method as follows:

window.history.back)

Using the CacheBehavior and CacheTimeout Properties

~

Schema

Web Part Schema

The amount of time a digital dashboard factory stores cached HTML

How a digital dashboard factory caches HTML

CacheTimeout property property

specify how a digital

dashboard factory caches

HTML, and you use the

CacheTimeout property to

specify the amount of time a

digital dashboard factory

stores cached HTML

Using the CacheTimeout Property The CacheTimeout property indicates how long a digital dashboard factory

will store and reuse cached HTML content before discarding it The value in this property is in seconds By default this value is zero, which indicates that the factory will not cache generated HTML content

For example, setting the value in this property to 60 (and the value in the

CacheBehavior property to something other than the default value of None)

will cause a digital dashboard factory to cache the generated HTML content for this Web Part for 60 seconds After that, the digital dashboard factory would regenerate the HTML content for the Web Part and cache it again for 60 seconds

A digital dashboard factory will ignore the cache settings for Web Parts that are isolated on the digital dashboard It will not cache these isolated parts, because the generated HTML content for an isolated Web Part is small and regenerates quickly, placing a smaller overall load on the server when the HTML content is not cached

If a digital dashboard

encounters a value other

than None, PerUser, or

AllUsers, it uses the default

setting of no caching

Note

Using Additional Execution Properties

Schema

Web Part Schema

XSLLink XSL RequireIsolation

RefreshInterval PartStorage

Additional execution properties of the Web Part schema control the behavior of Web Parts within a digital dashboard

Using the PartStorage Property You can use the PartStorage property to store any data related to a specific Web Part This property is similar to the Tag property in Microsoft Visual

Basic, and it can be used to store Web Part customization information This property accepts a single string value, so Web Part developers should devise a format that enables them to add more than one piece of information into this property value

Using the RefreshInterval Property

This property is no longer supported by the digital dashboard factory However,

it is listed in the Dashboard/Web Part Properties pane when a Web Part is selected This property should not be used by a Web Part developer

Using the RequiresIsolation Property You can use the RequiresIsolation property to indicate whether a Web Part

must be isolated from the rest of the Web Parts in a digital dashboard Isolated Web Parts are placed in an HTML IFrame and treated as separate documents Some reasons for isolation include:

! To avoid conflicts caused by Web Parts that include scripts or event sinks with the same name

! To avoid conflicts caused by Web Parts that include identical HTML IDs

Slide Objective

To list the additional

execution properties of the

Web Part schema

Lead-in

You use additional

execution properties of the

Web Part schema to control

Web Parts within a digital

dashboard

It will be helpful to have the

Web Parts Schema

Reference document

(available in the Web Part

Software Development Kit)

open and available for

reference when you present

this topic

Using the XSL and XSLLink Properties The XSL property contains Extensible Stylesheet Language (XSL) code that a

digital dashboard factory uses to sort, filter, or format a Web Part’s XML content before rendering the Web Part into the digital dashboard view

The XSL and the XSLLink properties are much like the Content and ContentLink properties A digital dashboard factory first determines whether the XSLLink property has a value If it does, the digital dashboard factory uses the results of that link and ignores the XSL property If the XSLLink property

is not defined or is not accessible, the digital dashboard factory uses the

contents of the XSL property If neither property is defined, or if the XSLLink property fails and the XSL property has no value, the digital dashboard factory

does not transform the Web Part’s content and renders it into the digital dashboard view as it is

# Using Web Part Schema Appearance Properties

! Using the AllowMinimize and FrameState Properties

! Using Additional Appearance Properties

You use the appearance properties of the Web Part schema to control the visual interface presented to the digital dashboard user These properties include

FrameState, Height, Width, IsVisible, IsIncluded, PartOrder, and Zone, which are all user-specific properties, in addition to AllowMinimize, AllowRemove, HasFrame, and DetailLink, which are view specific

Slide Objective

To outline this topic

Lead-in

You use the appearance

properties of the Web Part

schema to control the visual

interface presented to digital

dashboard users

Using the AllowMinimize and FrameState Properties

~

Schema

Web Part Schema

Specifies whether a Web Part is currently minimized or displayed

Specifies whether users can minimize a Web Part

FrameState property property AllowMinimize

The AllowMinimize property specifies whether a Web Part can be minimized

by users, and the FrameState property indicates whether a Web Part is

currently minimized or displayed

Using the AllowMinimize Property The AllowMinimize property specifies whether the digital dashboard

customization pages will allow users to minimize the Web Part, reducing it to just a title bar or some other title-only, no-content appearance If the value in this property is set to False, the digital dashboard view displays the Web Part and does not allow the users to minimize it

For example, you could set the value in the AllowMinimize property to False

for an advertising banner Web Part or a primary navigation Web Part that should always be visible

Using the FrameState Property The FrameState property indicates the current frame state of a Web Part; that

is, it indicates whether the Web Part is displayed in its expanded or minimized

state You can set the value in the FrameState property to Normal (display the

Web Part) or Minimized A digital dashboard factory uses the value in this property to determine how the Web Part should be rendered initially If a user minimizes a Web Part, the digital dashboard view updates this value so that future renderings will use the new setting

The value in the FrameState property is stored per Web Part instance,

not per user If a digital dashboard folder is in a public folder hierarchy, all these layout settings are stored and used for all users

You use the AllowMinimize

property to specify whether

digital dashboard users can

minimize a Web Part, and

the FrameState property

indicates whether a Web

Part is currently minimized

or displayed

It will help students to

understand these properties

if you demonstrate

minimizing and maximizing

a Web Part

You can show the students

that the availability of the (+)

and (-) control buttons on

the Web Part title bar are

dependent upon the value of

the AllowMinimize property

and that the FrameState

property controls the normal

state (maximized) versus

the minimized state of the

Web Part frame

Note

Using Additional Appearance Properties

Schema

Web Part Schema

DetailLink PartOrder

Zone IsIncluded IsVisible

Using the HasFrame Property The HasFrame property specifies whether a digital dashboard view displays a Web Part in a visible frame If the value in the HasFrame property is set to

True, the digital dashboard view displays a frame around the Web Part If the value in the property is set to False, the digital dashboard view does not display

the Web Part schema to

control the visual interface

presented to the digital

dashboard user

If a Web Part is minimized

by default, and the value in

the HasFrame property is

set to False so that the Web

Part is not displayed inside

a frame, the Web Part will

not be displayed on the

digital dashboard If you

have time, demonstrate this

to the class

Note

Using the Height and Width Properties You can set the Height and Width properties to restrict the height and width of

the Web Part in the digital dashboard view If you do not set these properties, or

if you set them to an empty value, the digital dashboard view will allow the Web Part to be as large as its content requires

Using the IsVisible Property The IsVisible property specifies whether a Web Part is included on the digital

dashboard and is visible in the digital dashboard view, or whether it is included

on the digital dashboard but is invisible in the digital dashboard view For example, you might need to have an invisible Web Part that stores intermediate data for other Web Parts on the digital dashboard

Using the IsIncluded Property The IsIncluded property specifies whether a Web Part is currently included on the digital dashboard If you set the value in the IsIncluded property to False,

the digital dashboard factory does not include the Web Part on the digital dashboard

Using the Zone Property The Zone property indicates where on the digital dashboard a particular Web

Part will be displayed The available values for this property are Top, Left, Center, Right, and Bottom

Using the PartOrder Property The PartOrder property indicates the relative vertical location (order) for Web

Parts that are located within the same digital dashboard zone For example, you might create a digital dashboard that includes six Web Parts in the left-side

zone, along with Web Parts in the other four zones The PartOrder property is

used by the digital dashboard factory to determine the order in which to display the six Web Parts (the Web Parts in the left-side zone) with respect to one another

If you have multiple Web Parts that are located in a single digital dashboard

zone and that have the same value for the PartOrder property, the order of

those Web Parts with respect to each other is unpredictable, but all of the Web

Parts sharing the same PartOrder value will still appear below Web Parts that have a lower PartOrder value and above Web Parts that have a higher PartOrder value

Using the DetailLink Property The DetailLink property contains a URL that appears in the Web Part frame or

heading This property allows users to view a full-page, detailed interface for the Web Part; for example, you could set this property for a Web Part that exposes top news headlines to provide a way for users to jump to that site’s home page

Note that the Height and

Width properties are string

values, which allows you to

use any height and width

measurement allowable in

HTML or Cascading Style

Sheets (CSS) For example,

you could set this value to

50 to get 50 pixels, or you

could set this to 50% to get

50 percent of the parent

size CSS also allows for

real unit measurements,

such as inches and

millimeters

If students are having

trouble understanding the

PartOrder property, this

example might be helpful:

You have six Web Parts in a

zone with PartOrder values

{1, 2, 3, 3, 3, 4} The parts

with the value 3 would

appear after the part with

the value 2 and before the

part with the value 4, but

you cannot assume any

particular order for the parts

with a value of 3