Справочник Пользователя для Wiley Professional InfoPath 2003 978-0-7645-5713-2
Модели
978-0-7645-5713-2
A central design concept is a “package” of files with distinct functions: a template document with a
structure definition from a fixed, industry-standard or custom XML schema; an XML file to contain
default data; and form data in an XML file that can be routed to points in a workflow. At each point, the
data is loaded into a form, which provides a view into editing all or parts of the form. This process can
be repeated as many times as necessary, with any number of participants.
structure definition from a fixed, industry-standard or custom XML schema; an XML file to contain
default data; and form data in an XML file that can be routed to points in a workflow. At each point, the
data is loaded into a form, which provides a view into editing all or parts of the form. This process can
be repeated as many times as necessary, with any number of participants.
Some approaches, like XForms, use fixed element names for controls and encourage implementers to
define the purpose of the data-gathering controls. This makes it easier to generate the related structures
automatically, for example, creating different interface objects for PDA and desktop browsers. Others are
more focused on providing a rich user interface (UI). However, most have a wide range of display prop-
erties that include showing or hiding parts of forms and repeating sections where elements can be added
or removed by users.
define the purpose of the data-gathering controls. This makes it easier to generate the related structures
automatically, for example, creating different interface objects for PDA and desktop browsers. Others are
more focused on providing a rich user interface (UI). However, most have a wide range of display prop-
erties that include showing or hiding parts of forms and repeating sections where elements can be added
or removed by users.
Points of Difference
Probably the first distinction to note is between Web-based XML forms and rich client systems. Web-
based applications have their attractions, and on office intranets they have become a common way to
collect some kinds of information from employees. They are easy to deploy and inexpensive to support.
But thus far they have not been good candidates for workflow processing. That will soon change as
XForms-based tools appear.
based applications have their attractions, and on office intranets they have become a common way to
collect some kinds of information from employees. They are easy to deploy and inexpensive to support.
But thus far they have not been good candidates for workflow processing. That will soon change as
XForms-based tools appear.
Rich client applications are relatively expensive to deploy and maintain, but they are often more robust
and can be more readily integrated with other desktop client systems. They can be operated when users
are disconnected from the network, and there is some evidence that users prefer them to Web-based
tools when they have a choice.
and can be more readily integrated with other desktop client systems. They can be operated when users
are disconnected from the network, and there is some evidence that users prefer them to Web-based
tools when they have a choice.
Another distinction is between declarative and scripting approaches. A goal of the XForms specification
was to limit the need for scripting; it therefore makes use of XPath-based calculation and validation, and
includes XML action elements that specify responses to events like setting focus or changing a data
value. In contrast, InfoPath, although it makes some use of declarative programming, including XPath
expressions, encourages the use of script more often.
was to limit the need for scripting; it therefore makes use of XPath-based calculation and validation, and
includes XML action elements that specify responses to events like setting focus or changing a data
value. In contrast, InfoPath, although it makes some use of declarative programming, including XPath
expressions, encourages the use of script more often.
InfoPath Features in Outline
Later in the book we’ll discuss InfoPath features in greater detail, but for now, here’s a summary of some
of the key XML technologies and development approaches.
of the key XML technologies and development approaches.
XML from the Ground Up
InfoPath applies a range of XML technologies recommended by W3C that we noted in the Introduction.
This is a first for Microsoft, and thus a first for you as an Office developer. Additionally, InfoPath makes
use of XML processing instructions and namespaces. There are also methods for accessing the XML doc-
ument using the InfoPath Object Model (OM).
This is a first for Microsoft, and thus a first for you as an Office developer. Additionally, InfoPath makes
use of XML processing instructions and namespaces. There are also methods for accessing the XML doc-
ument using the InfoPath Object Model (OM).
The following table outlines the use of some XML standards applied in InfoPath.
3
About InfoPath
01 557130 Ch01.qxd 3/18/04 3:59 PM Page 3