If you have some extra time and control over how the HTML design is done, you should also consider switching over to standards-based design using CSS. That would greatly simplify the HTML that your program has to produce (no more tables, font tags, or nbsps) and make it easier to change the design without touching the program or templates.

thanx for your replay
i want to make a dynamic content like a flash banner and adding effects to the page and itis code is indicates above
that code be possible ?
what is HTML::Template?

You want to serve a page that looks like your DreamWeaver page from a CGI/Perl script.

How the page looks in a web browser depends only on the HTML of that page. It does not matter at all how that HTML was produced on the server-side: It does not matter if it is hand-written in vi, done with DreamWeaver or by print statements in a Perl program. It does not matter if it is static HTML, or made by Perl, Java, COBOL, ASP .

So, yes, of course, you can write a Perl program that outputs HTML that looks exactly like your DreamWeaver file. The easiest way is to use a templating engine (HTML::Template is one such, just search for it on CPAN or here).

When you say "dynamic content" you have to distinguish between dynamic for the client, and dynamic for the server. Your flash banner is probably not dynamic content in terms of the server. What I mean is that the HTML (the part that the server produces) will always say src="banner.swf" , which is completely static. If the DreamWeaver page you made (which is static, because it is a static HTML file) already has all the dynamic content you want, you do not need to change that HTML dynamically on the server.

Examples for server-side dynamic content would be error messages (like "wrong password") that get inserted in the form, or rotating to a different flash banner depending on some clever conditions (although this can usually also be done on the client-side with JavaScript, or by the banner server).

I hope this is not too confusing for you. If this is your first project with Perl/CGI, I highly recommend you look at some of the tutorials here on PerlMonks. The most important concept to get a handle on IMHO is between what has to happen on the server, and what happens in the web browser. Separating these two parts cleanly can greatly improve maintainability of your application.

Update: fix CPAN link, GrandFather++

Not sure what you mean. But if you want to see what action1.pl might look like then here's a start:

#!Perl -w
use strict;

use CGI::Pretty qw(:standard :cgi-lib);
use CGI::Carp qw(fatalsToBrowser); # Remove for production code

$| = 1; # Unbuffered output

if (param('submit')) {
    print header ();
    
    my $name = param ('name');
    my $email = param ('email');
    my $password = param ('password');
    
    print "Name: $name<br/>\n";
    print "Email: $email<br/>\n";
    print "Password: $password<br/>\n";
}

exit 0;
[download]

Generates:

Name: wibble wobble<br/>
Email: wibble@wobble<br/>
Password: wibble<br/>
[download]

See CGI and the Tutorials' Web Programming for more information.

use CGI::Pretty qw(:standard :cgi-lib);

Why :cgi-lib?

$| = 1; # Unbuffered output

Why force separate network packets for each of the four prints?

Sigh. Cargo cult copy and paste from other code. :( Probably made sense in the other context, but not here.

---

DWIM is Perl's answer to Gödel

use CGI::Carp qw(fatalsToBrowser); # Remove for production code

I don't, unless I put more sophisticated error handling for end users on the browser. It may confused them but they still have a chance to copy paste what shown and hopefully send it to the appropriate person, instead of merely 500 Internal Server Error. End users don't have access to error.log.

---

Open source softwares? Share and enjoy. Make profit from them if you can. Yet, share and enjoy!

Potential black hats don't have access to the error logs either. Leaving development error output may let out something you don't want being leaked to potential attackers. Set up your web server to send an innocuous error page and leave the detailed errors for the developers' eyes only.l

What use is something like <strong></strong> or <marquee></marquee>? Or all the &nbsp;? Or the strange mixture of uppercase and lowercase tags? And no CSS but tables to format your page. And it does not even state against which version of HTML is it written. Even a simple and free program as Nvu knows how to do that.