Tài liệu hạn chế xem trước, để xem đầy đủ mời bạn chọn Tải xuống
1
/ 48 trang
THÔNG TIN TÀI LIỆU
Thông tin cơ bản
Định dạng
Số trang
48
Dung lượng
1,78 MB
Nội dung
Contents Overview 1 Understanding WebParts 2 UsingWeb Part Schema Content Properties 7 UsingWeb Part Schema Execution Properties 11 UsingWeb Part Schema Appearance Properties 17 UsingWeb Part Schema Basic Properties 21 Examining the DigitalDashboard Factory 22 Using the DigitalDashboard User Interface 26 Demonstration: Accessing the DigitalDashboard Customization Pages 29 Lab A: Working with Web Part Properties 34 Review 43 Module2:UsingWebPartsandDigitalDashboardComponents Information in this document is subject to change without notice. The names of companies, products, people, characters, and/or data mentioned herein are fictitious and are in no way intended 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 Module2:UsingWebPartsandDigitalDashboardComponents iii Instructor Notes This module provides students with an understanding of WebPartsanddigitaldashboard components. At the end of this module, students will be able to: ! Define Web Part, Web Part schema, anddigitaldashboard 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 digitaldashboard factory. ! Describe the digitaldashboard 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 WebPartsandDigitalDashboard 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 iv Module2:UsingWebPartsandDigitalDashboardComponentsModule Strategy Use the following strategy to present this module: ! Understanding WebParts Define Web Part, Web Part schema, anddigitaldashboard folders. ! UsingWeb Part Schema Content Properties Explain how to use the Content, ContentLink, and ContentType properties of the Web Part schema. ! UsingWeb 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. ! UsingWeb Part Schema Appearance Properties Explain how to use the AllowMinimize and FrameState properties, and additional useful appearance properties of the Web Part schema. ! UsingWeb Part Schema Basic Properties Explain how to use the Title, Description, Namespace, and LastModified properties of the Web Part schema. ! Examining the DigitalDashboard Factory Describe how the digitaldashboard factory initializes Web Parts. Explain how the digitaldashboard factory processes Web content. Describe the important property interactions of the Web Part schema. ! Using the DigitalDashboard User Interface Explain how to access the digitaldashboard customization pages. Describe the title and navigation areas and the five digitaldashboard zones. Module2:UsingWebPartsandDigitalDashboardComponents 1 Overview ! Understanding WebParts ! UsingWeb Part Schema Content Properties ! UsingWeb Part Schema Execution Properties ! UsingWeb Part Schema Appearance Properties ! UsingWeb Part Schema Basic Properties ! Examining the DigitalDashboard Factory ! Using the DigitalDashboard User Interface At the end of this module, you will be able to: ! Define Web Part, Web Part schema, anddigitaldashboard 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 digitaldashboard factory. ! Describe the digitaldashboard user interface (UI). Slide Objective To provide an overview of the module topics and objectives. Lead-in In this module, you will learn about usingWebPartsanddigitaldashboard components. 2 Module2:UsingWebPartsandDigitalDashboardComponents # ## # Understanding WebParts ! Defining Web Part ! Defining Web Part Schema ! Defining DigitalDashboard Folder WebParts are the building blocks that digitaldashboard factories use to create the digitaldashboard view that users see. The following topics define Web Parts, the Web Part schema, and the digitaldashboard folder and how they relate to each other. For information about creating Web Parts, see module 3, “Creating Web Parts” in course 2017A, Creating WebParts for Digital Dashboards. Slide Objective To outline this topic. Lead-in WebParts 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 Module2:UsingWebPartsandDigitalDashboardComponents 3 Defining Web Part Apply property schema to Web-based content Apply property schema to Web-based content WebParts are reusable components that apply a property schema to Web-based content—which can be written in Hypertext Markup Language (HTML) code, Extensible Markup Language (XML) code, and scripting languages. It is the schema property settings that affect how WebParts are rendered in a digital dashboard. The content of the Web Part can be as complex as streaming video or as simple as a string of text. Most WebParts 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 WebParts apply a set of properties to XML-, HTML-, or script- based content fragments. Lead-in WebParts can contain fragments of Web-based content from a variety of sources. 4 Module2:UsingWebPartsandDigitalDashboardComponents Defining Web Part Schema Web Part Web Part Schema Web Part Schema Web Part Schema Basic properties Basic properties Appearance properties Execution properties Content properties The power and versatility of WebParts come from the Web Part schema, which is a set of properties that establish how WebParts 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 digitaldashboard 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 digitaldashboard users to customize a digitaldashboard to meet their personal preferences. Content Class To ensure that digitaldashboard factories interpret WebParts 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 WebParts when they are rendered in a digitaldashboard 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-specific (view-specific properties contain metadata for the Web Part). For details on why this differentiation is necessary, see the “Building WebParts for the Digital Dashboard” white paper supplied with the DigitalDashboard Resource Kit. Digitaldashboard administrators can create their own digitaldashboard factories, based on the default digitaldashboard factory, that take advantage of additional properties. Check digitaldashboard forums periodically for updates on this advanced topic. Module2:UsingWebPartsandDigitalDashboardComponents 5 The Web Part schema defines a number of standard properties for a Web Part. Some of these properties are required for the digitaldashboard 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 digitaldashboard factory supplied with the DigitalDashboard Resource Kit 2.0 and will not be part of the base content class. Extending the default digitaldashboard 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 digitaldashboard factories to read WebParts 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 WebParts within a digital dashboard. ! Appearance properties. These properties control the visual interface presented to digitaldashboard 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 digitaldashboard factory uses the default value for the property. 6 Module2:UsingWebPartsandDigitalDashboardComponents Defining DigitalDashboard Folder Property Property Property Result Result Result AutoUpdate AutoUpdate Determines whether WebParts are updated with the values of a master Web Part Determines whether WebParts are updated with the values of a master Web Part DashboardOrder DashboardOrder Indicates the location of this digitaldashboard in the navigation user interface relative to other digital dashboards Indicates the location of this digitaldashboard in the navigation user interface relative to other digital dashboards DisplayTitle DisplayTitle Indicates whether the digitaldashboard view should display the title bar of the digitaldashboard Indicates whether the digitaldashboard view should display the title bar of the digitaldashboard MergeSubDashboards MergeSubDashboards Determines whether subdashboards are merged into the digitaldashboard view, allowing navigation between them Determines whether subdashboards are merged into the digitaldashboard view, allowing navigation between them RefreshInterval RefreshInterval Specifies how frequently the entire digitaldashboard is refreshed Specifies how frequently the entire digitaldashboard is refreshed Stylesheet Stylesheet Embedded style sheet that defines the digitaldashboard view Embedded style sheet that defines the digitaldashboard view A digitaldashboard folder is a specialized folder that contains WebPartsand must be located in a WebDAV-compatible data store. It has a custom property schema—the digitaldashboard schema—which applies to the digitaldashboard folder and all of the WebParts in the folder. You can customize digital dashboards by modifying the properties of the digitaldashboard schema. The Title, Description, and LastModified properties serve the same purpose in the digitaldashboard schema as they do in the Web Part schema. The following table defines some additional digitaldashboard schema properties. Property name Description AutoUpdate Determines whether and how often WebParts are updated with the values of a master Web Part DashboardOrder Indicates the location of this digitaldashboard in the navigation UI relative to other digital dashboards DisplayTitle Indicates whether the digitaldashboard view should display the title bar of the digitaldashboard MergeSubDashboards Determines whether subdashboards are accessible from the digitaldashboard view, allowing navigation between multiple digital dashboards RefreshInterval Specifies how frequently the entire digitaldashboard is refreshed Stylesheet Defines the digitaldashboard view by means of an embedded style sheet For more information about the digitaldashboard schema, see the DigitalDashboard Schema Reference document included on the Student Materials compact disc. Slide Objective To show how properties of the digitaldashboard schema affect the appearance of a digital dashboard. Lead-in Digitaldashboard folders contain WebPartsand enable you to customize properties of digital dashboards. This one-day course focuses on creating WebPartsand moves very quickly through the topic of digitaldashboard folders. Make sure that the students know that there is more material on creating digitaldashboard folders and the digitaldashboard schema in the DigitalDashboard Resource Kit. Note [...]... a digitaldashboard navigation bar if the digitaldashboard folder includes sub-dashboards ! Digitaldashboard zones The digitaldashboard zones provide a standard table layout that makes it easier for the digitaldashboard user to move WebParts from one position to another in the digitaldashboard view Module 2:UsingWebPartsandDigitalDashboardComponents 27 Accessing the Digital Dashboard. .. title bar and any standard buttons that a digitaldashboard includes in that title bar 20 Module2:UsingWebPartsandDigitalDashboardComponentsUsing 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 digitaldashboard view If you do not set these properties, or if you set them to an empty value, the digital dashboard. .. the Web Parts in a digitaldashboard Isolated WebParts are placed in an HTML IFrame and treated as separate documents Some reasons for isolation include: ! To avoid conflicts caused by WebParts that include scripts or event sinks with the same name ! To avoid conflicts caused by WebParts that include identical HTML IDs 16 Module2:UsingWebPartsandDigitalDashboardComponentsUsing the XSL and. .. ignored IsIncluded = False If a Web Part is not included, the values of most of the other properties will be ignored by the digitaldashboard factory when it renders the digitaldashboard view Non-included WebParts are usually not processed at all when the digitaldashboard view is built 26 Module2:UsingWebPartsandDigitalDashboardComponents # Using the DigitalDashboard User Interface Slide... displaying the digitaldashboard to the user ! Initializing WebParts ! Processing DigitalDashboard Content ! Understanding Property Interactions A digitaldashboard factory accesses the Web Part properties anddigitaldashboard schema properties and assembles the digitaldashboard view When a user connects to a digital dashboard, the digitaldashboard factory transforms XML data into HTML- and Dynamic... of the digital dashboards as if they were related pages However, the digitaldashboard factory also handles the more complex case of a full digitaldashboard tree by creating additional levels in the navigation strip 32 Module2:UsingWebPartsandDigitalDashboardComponents Examining the DigitalDashboard Zones Slide Objective To present the architecture of the digitaldashboard zones (Dashboard. .. the Linked Content to Travel Page Web Part is now located on the right side of the digitaldashboard 30 Module2:Using Web Parts and DigitalDashboardComponents ! To explore the Content in digital_ dashboard_ name customization page 1 On the Module 1 Demonstration title bar, click Content 2 Quickly review the Web Parts list, Open Web Part Catalog, and Create new Web Part sections of the content customization... not accessible, the digitaldashboard 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 digitaldashboard factory does not transform the Web Part’s content and renders it into the digitaldashboard view as it is Module 2:Using Web Parts and DigitalDashboardComponents 17 # UsingWeb Part Schema Appearance... (DHTML)–formatted content, and then uses Microsoft Internet Information Services (IIS) to stream the transformed content to the digitaldashboard view Module 2:UsingWebPartsandDigitalDashboardComponents 23 Initializing WebParts Slide Objective To show the process of initializing a Web Part Lead-in Digitaldashboard factories use a three-step process to initialize WebParts Update non-user– Update... consists of the digitaldashboard view and the three customization pages that can be accessed from the digitaldashboard The customization pages enable users to add WebParts to the digital dashboard, to change properties of the Web Parts in the digitaldashboard folder, and modify digitaldashboard schema properties associated with the digitaldashboard folder The digitaldashboard customization pages . and the five digital dashboard zones. Module 2: Using Web Parts and Digital Dashboard Components 1 Overview ! Understanding Web Parts ! Using Web Part Schema. Module 2: Using Web Parts and Digital Dashboard Components iii Instructor Notes This module provides students with an understanding of Web Parts and digital