Overview
This section provides a feature overview of WHIP! and how to use the guide.

Introduction — What is WHIP! data?
WHIP! data is the new name given to classic DWF (Design Web Format) files of version 0.55 and earlier. The DWF 6 format is described in detail in the DWF Specification document accompanying this distribution. WHIP! data was developed because widely accepted 2D vector file standards did not address the needs of Internet aware applications. In addition, commercial formats were too closely tied to specific proprietary data structures to support the exchange of illustrations among systems.

WHIP! data is a format for the standardized description of 2D, vector-based drawings and illustrations, intended for encapsulation within a DWF package file. WHIP! data files of version 6.0 and greater are not intended to be used as stand-alone files, but rather a data channel within a DWF package file.

This specification was developed with the following in mind:


About The Guide
This version of the Guide also expands upon the development system and opcode library that originated with the Whip! Toolkit. This section tells how to use the guide.

Synopsis
The guide has one primary focus:
Technical overview of the WHIP! data specification intended for use as a channel (file resource) within a "Design Web Format" (DWF) — package. WHIP! data contains information facilitating the transmission of 2D vector drawings. A reference of opcode definitions is included.
The following sections are included:

Overview — Provides a feature overview of WHIP! data and how to use this guide.

WHIP! Data Architecture — A description of the WHIP! data and opcode structure, details and examples.

Standard Opcode Definitions and Reference — An alphabetical reference of the WHIP! data opcodes and operands.

Appendix A: Opcodes Listed by Format — A quick reference of opcodes listed by opcode category: single byte, extended ASCII, and extended binary formats.

Appendix B: License Agreement  The End User License Agreement which must be acknowledged, as noted, prior to using the toolkit.
This guide is based on revision 06.00 of the WHIP! data specification. Future versions will specify additional functions that were not included. As such, some content in this revision is marked "To Be Determined" (TBD).

Typographical Conventions
In this guide, certain typographical conventions are used to make reading and understanding easier.

The Courier font is used for methods, file objects and items expressed in code and fragments of C or C++ language code:

 
Methods
process_next_object()
Function names (when in code)
establish_configuration
 
A Times Roman bold font is used for opcodes and function names:
Define Compressed Data, or Draw Ellipse.
An italic font is used for arguments, values, and also emphasis, names of documents, files, and directory locations supplied with the kit:
a four-bit literal data run length value.
Underlined Courier font characters indicate binary operand data:
1xxxxyyyyxxxx.
In code samples or code sequences, the use of a C++ comment identifier followed by ellipses indicates code that has been omitted for clarity:
// ....
Actions, attributes and references to sections in the guide appear in the text as Times Roman font in double quotes:
"process", "Color" and, see the "Notes" section of....

Technical Support, Information and Revisions
The DWF and WHIP! Toolkits are provided free on an as-is basis. There is no technical support available. Please post questions, comments and suggestions pertaining to the toolkit and this guide to the internet news group at news://discussion.autodesk.com/autodesk.internet or the web version at    http://discussion.autodesk.com/WebX?14@@.ee937e6.

It is recommend that you update your WHIP! Data Specification with each new release of DWF, as it is continually revised when new information becomes available.