[Chapter 19] 19.6 Form Generation
Author: Randal Schwartz, Tom Christiansen & Larry Wall
Date: 1999-07-02T01:36:18Z

#

| Chapter 19 CGI Programming |

## 19.6 Form Generation

Perhaps you're tired of typing your program's parameter to your browser. Just make a fill-out form instead, which is what most folks are used to. The parts of the form that accept user input are typically called widgets, a much handier term than "graphical input devices." Form widgets include single- and multiline textfields, pop-up menus, scrolling lists, and various kinds of buttons and checkboxes.

Create the following HTML page, which includes a form with one text-field widget and a submit button. When the user clicks on the submit button,[7] the ice_cream script specified in the ACTION tag is called.

> [7] Some browsers allow you to leave out the submit button when the form has only a single input text field. When the user types a return in this field, it is treated as a submit request. But it's best to use portable HTML here.

    <!-- ice_cream.html -->
    <HTML>
        <HEAD>
        <TITLE>Hello Ice Cream</TITLE>
        </HEAD>
        <BODY>
        <H1>Hello Ice Cream</H1>
        <FORM ACTION="http://www.SOMEWHERE.org/cgi-bin/ice_cream">
        What's your flavor? <INPUT NAME="favorite" VALUE="mint">
        <P>
        <INPUT TYPE="submit">
        </FORM>
        </BODY>
    </HTML>

Remember that a CGI program can generate any HTML output you want, which will then be passed to any browser that fetches the program's URL. A CGI program can, therefore, produce the HTML page with the form on it, just as a CGI program can respond to the user's form input. Moreover, the same program can perform both tasks, one after the other. All you need to do is divide the program into two parts, which do different things depending on whether or not the program was invoked with arguments. If no arguments were received, then the program sends the empty form to the browser; otherwise, the arguments contain a user's input to the previously sent form, and the program returns a response to the browser based on that input.

Keeping everything in a single CGI file this way eases maintenance. The cost is a little more processing time when loading the original page. Here's how it works:

    #!/usr/bin/perl -w
    # cgi-bin/ice_cream: program to answer *and generate* ice cream
    # favorite flavor form (version 3)
    use CGI qw(:standard);
    my $favorite = param("flavor");
    print header, start_html("Hello Ice Cream"), h1("Hello Ice Cream");
    if ($favorite) {
        print q("Your favorite flavor is $favorite.");
    } else {
        print hr, start_form; # hr() emits html horizontal rule: <HR>
        print q("Please select a flavor: ", textfield("flavor","mint"));
        print end_form, hr;
    }

If, while using your browser, you click on a link that points to this program (and if the link does not specify `?whatever` at the end of the URL), you'll see a screen like that in Figure 19.2. The text field is initially filled out with the default value, but the user's typed input, if any, will replace the default

#### Figure 19.2: A basic fill-out form

Now fill in the `flavor` field, hit Return, and Figure 19.3 shows what you'll see.

#### Figure 19.3: Result of submitting the form shown in Figure 19-2

19.5 Less Typing |  | 19.7 Other Form Elements