If you do make it up into a tutorial, perhaps you might focus a bit more on "separation of concerns".
At the moment it's a little difficult to read the Javascript code. Maybe I'm just biased, but since CGI::Ajax can't do all the Javascript you need, I just don't see the point in using it at all. Perl handles the server side nicely, why not use one of the many excellent Javascript tooklits to handle the client side?
There are large comment blocks over each Javascript function, perhaps you could move all the Javascript into a separate file? If you use a modern JS/Ajax toolkit such as jQuery (or Dojo or Ext) you're Javascript code will be much shorter and more concise.
Perhaps your tutorial could deal with issues such as:
- how to serve standard RPC wire-formats (JSON, SOAP, REST) in Perl,
- use of unobtrusive, browser-degradable javascript
- some of the animation effects provided by modern JS/Ajax toolkits to improve the popup/tooltip presentation.
-David
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.