For large applications, I prefer the all-in-one approach, mapping subs to states/screens.

Only one place to break or upgrade. All states and expected inputs can be known to the program so it's easier to validate correct input between states and also to kick people back to previous screens if there is an error.

Usually, for integrating look and feel, we insert the output from the script into a template page from the site. Usually by having the designer place a special tag within it and this is where the output goes. This way they can change the main layout without program modifications.

-Lee

"To be civilized is to deny one's nature."

---

---

• 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.