Encapsulates a multi-page document with support for raster and SVG images, bookmarks, annotations and text data.
The LEADDocument class provides uniform support for any type of document. The actual data behind can be a PDF document, Microsoft Word document, TIFF image, AutoCAD DWG drawing or any other of the hundreds of different raster, document or vector file formats supported by LEADTOOLS. LEADDocument uniformly encapsulates the common functionality needed to access this data with the same properties, methods and data structures.
LEADDocument is used as an input to the LEADTOOLS DocumentViewer, which can be used to view the document and its pages with thumbnails, virtualization, text search and annotation support.
A LEADDocument instance be obtained using the following:
||Creates a new instance from a document stored in a remote URL.|
||Loads a previously saved document from the cache.|
||Creates a new empty document.|
In most cases, the LEADDocument is ready to use after it has been obtained. However, some documents such as PDF can be encrypted and require a password before they can be parsed and used. Most of the properties and methods of LEADDocument will throw an error if the document has not been decrypted. IsEncrypted can be used to check if the document is encrypted and if so, Decrypt must be called with a password obtained from the user to unlock the document. When that happens, the value of IsDecrypted becomes true and the document is ready to be used. Note that IsEncrypted will stay true to indicate the original state of the document.
Each document has a unique identifier that is set at creation time by the framework. This is stored in the DocumentId property. The ID is important when using the document with the cache system and is the only value needed to re-construct completely the document from the cache. The document ID can be set manually by the user through the LoadDocumentOptions.DocumentId, CreateDocumentOptions.DocumentId or BeginUploadDocument options used when loading, creating or uploading the document. If the value was left to null, then the factory will generate a new random ID to associate with.
Documents can contain large number of pages and huge amount of data. Storing all this data in the physical memory is not feasible in most situations. Therefore, the LEADDocument class was designed to use an external caching system to store previously requested document sections and document modifications.
DocumentDocuments derives from LeadCollection. You can use any of the collection methods to iterate through the documents. This collection is read-only however and you cannot add, remove or change the items. Instead, use Pages to add or remove pages that belong to a separate document to this one. The LEADDocument.Documents collection will automatically get updated to reflect what child documents are currently held in the document.
The metadata includes default values added by the service when the document is loaded or created, as well as any other data extracted from the document file itself such as author, subject and any keywords stored by other applications.
The following properties are part of LEADDocument and contain useful information:
DocumentId: The unique identifier of this document.
Name: The optional name of this document.
MimeType: The MIME type of the document.
CacheUri: The URL to the original document's image data if it was stored in the cache.
IsReadOnly: Determines if the document is read-only and cannot be changed.
FileLength: The length of the original document file or URL in bytes.
CacheStatus: The status of this document in the cache.
The LEADDocument class contains the following to manage global settings used throughout the document.
Images: Manages the raster and SVG image settings of the document.
Annotations: Manages the annotations settings of the document.
Text: Manages the text and OCR recognition settings of the document.
Barcodes: Manages the barcode settings of the document.
For an example, refer to LoadFromUri.