Discover the answers to Frequently Asked Questions about PICTools Document below.
- Open Windows Explorer and type ftp://ftp.jpg.com/ into the Navigation Bar.
- Right Click inside Windows Explorer to bring up the standard context menu.
- Find "Login As" and click it to login to FTP Server.
- Provide the user name: support and the password: 853ae90f
Each PICTools SDK contains a doc directory containing helpful documentation about PICTools. A high level QuickStart Guide provides an overview of PICTools, discusses the architecture, and offers simple to use suggestions for getting started and can be found on each PICTools SDK documentation pages. The PICTools Programmer's Guide is a more comprehensive description of how to use PICTools, and the PICTools Reference Manual provides specific API information required to successfully code your application. Links to these materials can also be found on the respective PICTools documentation pages listed below:
Reviewing the material in this order will make it easiest to understand. Each SDK also includes a simple code sample, delivered as a Visual Studio 2005 project for Windows toolkits, with makefiles for the Unix and Linux platforms. It also includes source code for the Apollo demo, which is a Windows application designed to highlight features associated with compression and decompression of many image types supported by PICTools, including:
- Camera RAW
- HD Photo/JPEG XR
- JPEG 2000
- JPEG LS
- Lossy and Lossless JPEG
The PICTools development kits are provided to developers as fully functional evaluation versions. The only difference between the evaluation version of a toolkit and a registered version are some registration codes that make these Pause dialogs stop appearing. To a developer writing application code, these dialogs can be useful to see what is happening "under the covers" with version and opcode numbering and dll naming information being displayed in the Pause dialog itself. The Pause dialogs will appear the first time a particular "opcode" is used during the run of an application and then very infrequently randomly after that. They cause the application code to pause for approximately 5 seconds. If the Pause dialogs make operation timing difficult, it is a fairly straightforward procedure to do an operation once, start timing, and then repeat it for the desired number of iterations. Another option to conduct timing tests is to perform some series of operations one time so that each of the operations in the timing test have been performed once by the application before the timing run is made.