Andrew Speer > WebDyne-1.223 > wdrender

Download:
WebDyne-1.223.tar.gz

Annotate this POD

Website

CPAN RT

New  1
Open  0
View/Report Bugs
Source   Latest Release: WebDyne-1.233

Name ^

wdrender - parse and render WebDyne pages

Synopsis ^

wdrender [OPTIONS] FILE

Options ^

-h, --help Show brief help message.

-v, --version Show version information.

--handler

Use a different WebDyne handler module. Currently the only other handler module available is WebDyne::Chain.

--header

Show HTTP status headers (default). User --noheader to disable.

--error=text[|html]

Show text error messages. User --error=html to HTML error message.

--outfile=<filename>

Send output to <filename> instead of STDOUT

--header_in="Header: Value"

Set simulated input header name to value. Can be set multiple times

--header_out="Header: Value"

Send output header with value (if header output enabled). Can be set multiple times

--status=value

Send status code x (e.g. 200,500,404) with header (if header output enabled)

Description ^

The wdrender command displays the HTML that would be generated from a psp page using the WebDyne perl module.

By default wdrender will use the internal WebDyne handler when building the output, but can optionally use other WebDyne modules (such as WebDyne::Chain) by using the --handler option..

Notes ^

The wdrender command will attempt to build the HTML as faithfully as possible from the command line environment, but may not be able to exactly duplicate the HTML generated under a real Web Server. As an example if a psp page takes advantge of the Apache request handler when generating HTML, the wdrender commend will not be able to duplicate that environment.

Examples ^

wdrender widget.psp

Display the HTML that would be generated by WebDyne from the widget.psp file.

wdrender --handler=WebDyne::Chain widget.psp

Display the HTML that would be generated by WebDyne from the widget.psp file, but this time using the WebDyne::Chain handler. In this case the example would fail, as WebDyne::Chain expects to get a list of modules it will chain the page throught. Normally it would get that from the Web Server configuration file, but the WebDyne::Chain module can take the list of modules from the environment also. So a better example would be:

WebDyneChain=WebDyne::Session wdrender --handler=WebDyne::Chain widget.psp

Author ^

Written by Andrew Speer, andrew@webdyne.org

Copying ^

Copyright (C) 2008-2010 Andrew Speer. Free use of this software is granted under the terms of the GNU General Public License (GPL)

syntax highlighting: