in reply to Potential for a New Module?

Is there a reason why you need to create static pages, rather than creating the listed pages one page at a time? If not, I highly suggest HTML::Template. Simply passing it a sequence of AoH's (one for each page) will allow you to abstract the HTML from the data. Not to mention, all the saved bit space on your drives. ;-)

Each "navigation" link would simply contain a hidden sequence within the URI, defining what range of data the AoH should define and pass of to the TMPL_LOOP tags (for example). There's an excellent introductory document for this module here.

Hope this helps!

-fp

Replies are listed 'Best First'.
Re(2): Potential for a New Module?
by FoxtrotUniform (Prior) on Aug 06, 2002 at 22:48 UTC

    Not all of us need, or want, dynamic sites.

    That said, using a templating system is a really good idea. I'd like to see a system that chunks the input data into separate pages, then calls a callback function on each to HTML-ify them. This callback could use HTML::Template, Template Toolkit, XSLT, HTML::FromText, or anything else you care about. (This also has the advantage of working with things other than HTML. If I want to drop in a callback that generates LaTeX sections for a book, I can do so quite easily.)

    Of course, the more general the module gets, the closer it gets to a simple for loop:

    for my $page (@pages) { &process_page($page); }

    ...which isn't precisely CPAN material. :-)

    --
    F o x t r o t U n i f o r m
    Found a typo in this node? /msg me