I was in the same situation about 2 years ago, when I had to build a new component for a massive(ly old) web app. Instead of keeping with current practice (of placing thousands upon thousands of html as strings inside the perl code), I made a toolkit-like library (think gtk+ but for html), which used the popular (and then only) prototypejs.
I don't know if it's better than Catalyst, but it's certainly different, and you are more than welcome to take a quick look at it
on CPAN.
I've also put it to use on my
page, though it only a 30min job, if you want to see it in action.
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.