IMO, there's a lot of merit to using the clients' browsers (assuming a homogeneous set such as might be found in a corporate setting) and some well chosen CSS to provide all the display elements you need.

Then, you can rely on CGI or friends to render the data... which you can obtain as required using DBD, DBI or other db modules. The catch is, you still have to get the user input. So -- along side your Perl-controlled browser -- why not use a wxPerl window whose capabilities handle the minimal requirements for input only, thus simplifying the UI at the requestor end?

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.