Quick Start Tutorial
The content in the tabs beneath should have you up and running with PDFhelp in no time. If you are still having problems, contact us.
- Quick Start PDFhelp
- Generating Source Code
- End User Application
Getting Started
You can run the PDF Help example application either by double clicking on the jar file, or from the command line using: -
java -jar pdfhelp.jar
By default PDF Help will be run in Developer Mode. This means that files can be added to, and removed from the file list. When you have finished adding all the files you require to the list of searchable PDFs, you can use PDF Help to generate the Java Source Code that would be required to initialize, and run the application in end-user mode, using the files currently shown in your list.
Please note, if you are using encrypted PDFs or require support for JPEG2000 files you will need some additional files.
Below is a screen shot of the application running in Developer Mode.

You will see that a toolbar is enabled allowing you to add files from disk or URL, remove files, reset the list back to its default settings, and generate the source code required to run the application in end-user mode using the list of files currently on display.
Generating Source Code
When you are ready to generate the source code, click the "Produce PDF Help Initialization Code" button in the toolbar (its the button on the far right of the toolbar with the Java cup icon on it).
Below is a screen shot of the dialog box which will appear.

The PdfHelpPanel extends the JPanel so it can be used as any standard Swing Component. You simply have to add it to your applications container, for example a JFrame. The source code for a simple example PDF Help application is available here.
If you decide you want to base your application on this example, simply replace the default file list and constructor, with this custom generated code.
End User Application
By using the generated source code, the produced constructor automatically sets the application to run in end-user mode.
Below is a screen shot of the end-user application generated from the source code produced in this example. You will see that all the files are available in the file list, but the toolbar has been removed. This means the file list is locked down, and the user can no longer add or remove files.


