Print2Flash Application Programming Interfaces
There are two kinds of Application Programming Interfaces (APIs) supported by Print2Flash:
- APIs for programmatic conversion of documents to Flash (SWF) or HTML (SVG) format. There are two APIs for this:
- API for manipulation of converted Flash or HTML documents: scaling, scrolling, controlling the document toolbar, etc. It is called Document API.
APIs for programmatic conversion of documents to Flash or HTML
APIs for programmatic conversion of documents to Flash/SWF or HTML/SVG are available in Server mode of Print2Flash.
Document types supported for conversion with APIs
Basically you can convert any printable documents for which there is an application installed on your computer capable of printing these documents and registered in Windows for programmatic printing. The kinds of documents available for conversion include (but not limited to):
- Microsoft Office documents: Word (.doc, .docx), Excel (.xls, .xlsx), PowerPoint (.ppt, .pptx);
- PDF documents (.pdf);
- Text documents (.txt);
- RTF documents (.rtf);
- HTML pages (.htm, .html);
- Image files (.png, .jpg, .tiff, .tif, .bmp, .gif);
- OpenOffice documents: Writer (.odt), Calc (.ods), Impress (.odp), Draw (.odg), Math (.odf);
- Microsoft Outlook message documents (.msg);
- Microsoft Project documents (.mpp);
- Adobe InDesign documents (.indd);
- Autodesk AutoCAD documents (.dwg).
If an application is not registered in Windows for programmatic printing of documents of the given type but has an API for printing, you still can convert them with Print2Flash using this API and Print2Flash printing jobs.
Print2Flash OLE Automation API
Print2Flash OLE Automation exposes a set of objects which have properties and methods allowing you to convert documents to Flash or HTML format and control document features. Please see About Print2Flash OLE Automation API help topic for more information on Print2Flash OLE Automation API.
Print2Flash OLE Automation API samples
We have several samples demonstrating using of Print2Flash OLE Automation API from various programming languages: ASP, ASP.NET/C#, Delphi, Java, PHP, VBScript, Visual C++. These samples are contained in the Print2Flash SDK that can be downloaded from our download page. The samples are located in the Automation\Samples folder of SDK archive file. Please refer to ReadMe.htm file located in each sample folder for sample installation and usage instructions.
Enhanced Batch Processing
Enhanced Batch Processing is essentially a Windows command line conversion tool. You may invoke a command that converts a document or an entire folder with documents to Flash or HTML format. The command line syntax is very simple and allows you to control a lot of conversion options. You may invoke Enhanced Batch Processing commands either manually from Windows Run window or from your programs written in any language that supports invoking Windows command line commands. These include Visual Basic, .NET (VB.NET, C#, J#), C/C++, Java, Delphi, PHP, Ruby, Python, Perl, BAT files and others.
Please see Enhanced Batch Processing help topic for more information on Enhanced Batch Processing:
Print2Flash Document API
Print2Flash Document API lets you control converted Flash or HTML documents: scale them, show or hide toolbar buttons, scroll the documents, print them, etc. Usually such actions can be performed by user using the document toolbar. However, you may also invoke such actions from a web page or your Flash or Flex movie in which you embed the document. You may even hide the standard toolbar and implement your own toolbar calling Print2Flash Document API functions. Please see Print2Flash Document Application Programming Interface help topic for more information on Print2Flash Document API:
Print2Flash Document API samples
We have several samples demonstrating using of Print2Flash Document API from various containers embedding the documents: from a web page, from a Flash movie and from a Flex application. These samples are contained in the Print2Flash SDK that can be downloaded from our download page. The samples are located in the DocumentAPI folder of SDK archive file. Please refer to ReadMe.htm file located in each sample folder for sample installation and usage instructions.