| 1 |
pod2text CGI::Perljax.pm > README |
| 2 |
|
| 3 |
CGI::Perljax |
| 4 |
|
| 5 |
Perljax - a perl-specific system for writing AJAX- or |
| 6 |
DHTML-based web applications. |
| 7 |
|
| 8 |
|
| 9 |
Perljax provides a unique mechanism for using perl code |
| 10 |
asynchronously from javascript using AJAX to access user-written |
| 11 |
perl functions/methods. Perljax unburdens the user from having to |
| 12 |
write any javascript, except for having to associate an exported |
| 13 |
method with a document-defined event (such as onClick, onKeyUp, |
| 14 |
etc). Only in the more advanced implementations of a exported perl |
| 15 |
method would a user need to write custom javascript. Perljax supports |
| 16 |
methods that return single results, or multiple results to the web |
| 17 |
page. No other projects that we know of are like Perljax for the |
| 18 |
following reasons: 1. Perljax is targeted specifically for perl |
| 19 |
development. 2. Perljax shields the user from having to write any |
| 20 |
javascript at all (unless they want to). 3. The URL for the HTTP GET |
| 21 |
request is automatically generated based on HTML layout and events, |
| 22 |
and the page is then dynamically updated. 4. Perljax is not part |
| 23 |
of a Content Management System, or some other larger project. |
| 24 |
|
| 25 |
|
| 26 |
INSTALL |
| 27 |
|
| 28 |
perl Makefile.PL |
| 29 |
make |
| 30 |
make test |
| 31 |
make install |
| 32 |
|
| 33 |
*If you are on a windows box you should use 'nmake' rather than 'make'. |
| 34 |
|
| 35 |
Installation will place Perljax into the system perl @INC path, but it |
| 36 |
is important that you make sure mod_perl uses this path (which is |
| 37 |
mod_perl's default behavior, and also assuming you use mod_perl, and |
| 38 |
not just run perl as a CGI). |
| 39 |
|
| 40 |
Example scripts are provided in the source script directory, and can |
| 41 |
also be seen on the project's website, http://www.perljax.us. |