Implementing JavaScript in PDF

Creating JavaScript and Ajax based application for browsers and mobile gadgets is a common task for developers. As JavaScript and Ajax has significantly improved in the past decade, it has become the tool for developers to create online applications. Instead of simply building websites that display the needed data, browsers have become a "shell" where applications can be launched anywhere.

JavaScript and Ajax has enabled this feature that is has rivaled popular desktop applications. This is also true in mobile gadgets. Although it's still in development stages, the SDKs offered for various mobile platforms are very impressive.

But there is one small platform that JavaScript has yet to fully conquer: PDF documents. Originally created by Adobe in early 90s, it has become one of the preferred formats of file for eBooks and online transactions. Although it can be edited with the right software, its main advantage is that it can create an atmosphere of "unedited" document which is needed for online transactions. This type of file is yet to be extensively used with JavaScript.

Why would JavaScript developers care about PDF documents? The answer: Adobe is allowing it. The ability to implement JavaScript functions was first used in 2000 with Adobe Reader 4.0. Until 2004, major changes were added in order to transform a simple PDF document to a shell for multimedia. For example, 2003 allowed links and streams of object and 2004 featured embedding and XML forms. With these features since 2004, creating JavaScript and even Ajax based scripts for PDF is a possibility.

Implementing JavaScript and Ajax in PDF can actually have its advantages. The key advantage is actually on portability. Users can bring their PDF documents anywhere and launch them using a portable PDF Reader.

The scripts are already there in PDF format and users simply interact with the embedded functions. Another advantage of creating JavaScript on PDF is the capability of PDF to be lightweight and will not require any browsers for online interaction.

But there are some challenges in portability and sacrificing the use of browsers for faster data connection. Among them is security since there are some security protocols that are never implemented in PDF. Another challenge for developers is that some PDF readers are only capable of reading some functions, variables and objects. Adobe Reader can read virtually every function in JavaScript.

Others, on the other hand have limited the use of JavaScript to simple data input and embedding of multimedia format. This makes it difficult for developers who wanted to create an online application that can be launched on PDF. They may recommend a specific reader but users may just find this a bit too aggressive just to launch an online application in PDF.

The development of JavaScript in PDF can be considered in its infancy. But that only mean developers can further enhance the experience of users by providing interactive applications in PDF. Of course, this experience should be complemented by industry support as PDF readers are still limited on what JavaScript functions should be allowed in this file format.