in reply to Managing large CGI pages

I'm also a fan of here documents, and sometimes of embedded-code solutions such as Apache::eperl or Apache::embperl. What I find easiest to do is to write up the HTML with no code in it first (or ideally, have someone else do that for me), and then stick in variables, etc. later on. In order to keep the pages themselves clean looking, I find it a good idea to separate functions into a file or files that are then required, and have only variables and function calls within the HTML itself. It's very straightforward, and the whole thing basically becomes a template easily edittable by a non-coder.

Replies are listed 'Best First'.
RE: Re: Managing large CGI pages
by JanneVee (Friar) on Jun 08, 2000 at 02:27 UTC
    There is actually a drawback with eperl and embperl. You're mixing design with content and adding code. IMHO one should aim at separating the design, content and code. Sometimes the code is used to generate design. Sometimes for content generation. Even for both.

    But on the other hand Perl can look scary for a non-coder. That in turn just scream "don't touch me!". That leaves the trouble makers with coding aspirations.