This is just one thing to think about...

Your UI involves multiple interactions. By that I mean the script has to do some processing in order to provide each step . E.G. In order to populate the 2nd drop-down, the script has to process the results of the 1st drop-down. Etc...

Since you're describing multiple interactions, you're going to have to either reload the page multiple times or do some ajax magic. Or you could have one page per list.

So, the slickness of your UI depends on how complex you're willing to make your code. If you want to keep it simple, you might want to make it multiple pages. (Those multiple pages could still be generated by a single script though..)

In reply to Re: CGI: Form contents dependent on drop down lists by pileofrogs
in thread CGI: Form contents dependent on drop down lists by Olaf

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.