Microsoft Office InfoPath 2003 Articles

Gerald Bauer <[email protected]>
Newsgroups gmane.comp.lang.xul.announce
Message-ID <[email protected]>
Hi,

  I've collected links to articles about InfoPath 2003
- Microsoft's latest Office family addition that lets
you design rich, dynamic forms using a plethora of XML
and Web standards such as XML Schema (XSD), XPath,
XSLT, CSS, DOM, Javascript and more with the notable
exceptions of XForms, XUL or SVG, of course.

  InfoPath is Microsoft's latest entry in the race to
create the next-gen universal client (aka "HTML
killer"). Here's the current line-up:

Microsoft: * Office is the Universal Client
           * Windows is the Universal Client
           * .Net is the Universal Client

Adobe: * Acrobat is the Universal Client

Sun: * Java is the Universal Client

IBM: * Lotus is the Universal Client

Micromedia: * Flash is the Universal Client

and so on and so forth

I guess every industry giant dreams that their own
products will be the next universal client with a 100
% market share. They push their own agenda non-stop
instead of joining the Free World and helping to build
a better browser for everyone by using open
royality-free standards such as XHTML, SVG, XUL,
XForms, CSS, Python and more.      

  Anyway, here's the InfoPath article line-up to get
started with Microsoft latest offering:
  
Technology Overview of Microsoft Office InfoPath 2003
=====================================================
by Anonymous, May 2003, 9 printed pages

Summary: Microsoft Office InfoPath 2003 is a hybrid
tool that combines the best of a traditional document
editing experience, such as a word processor or e-mail
application, with the rigorous data-capture
capabilities of a forms package. This article
describes the problems InfoPath is designed to address
and explains the design principles and XML industry
standards used to solve these problems. 

Full story @
http://msdn.microsoft.com/library/en-us/odc_ip2003_ta/html/ODC_InTechOV.asp


Architecture of Microsoft Office InfoPath 2003 
==============================================
by Michael Hoffman (Microsoft), June 2003, 17 printed
pages

Summary: Discover the architecture of Microsoft Office
InfoPath 2003, including how InfoPath supports
structural editing, several levels of validation,
loading and submitting of XML documents, and multiple
views of the DOM tree. 

Full story @
http://msdn.microsoft.com/library/en-us/odc_ip2003_ta/html/odc_inArch.asp


How XML Standards Are Used in Microsoft Office
InfoPath 2003
============================================================
by Michael Hoffman (Microsoft), June 2003, 12 printed
pages

Summary: Learn how Microsoft Office InfoPath 2003 is
built using XML standards, including integrated
support for XML Web services, providing full
interoperability with XML-enabled systems. 

Full story @
http://msdn.microsoft.com/library/en-us/odc_ip2003_ta/html/odc_inXMLs.asp


Introducing InfoPath Development
================================
by Acey James Bunch (Microsoft), May 2003, 20 printed
pages

Summary: Microsoft Office InfoPath, the newest
addition to the Microsoft Office System, supports a
robust programming model and development environment.
This article introduces InfoPath development and
includes an overview of the main development
components, information about the development
environment, an overview of the object model and form
definition file, and a discussion of the key
development areas. 

Full story @
http://msdn.microsoft.com/library/en-us/odc_ip2003_ta/html/odc_inIntro.asp

 - Gerald


-------------------------------------------------------
This SF.net email is sponsored by: VM Ware
With VMware you can run multiple operating systems on a single machine.
WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the
same time. Free trial click here: http://www.vmware.com/wl/offer/345/0
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.