|
|||||||||||||||||||||||||||||||||||
|
Copyright (C) 2004,2005,2006 by Philipp Kindt 
|
Content Introduction Specifications Template syntax Handler types Introduction Donparser is an interface between HTML and Perl. It is used as "backend" of Pagenews - allmost everything uses it. The classic way of writing Perl CGIs is that a perl script sends some HTML to the browser. The donparser way is different: A .donparser - document is opened by a perl script that interprets it and sends the content to the browser. Theese documents are normal HTML files with some extensions that are just interpreted by donparser .donparser - Documents can be found in three folders:
Specifications Donparser document must have the ending .donparser. There is a header which is separated from the rest of the template by an empty line.(\n\n) The header is parsed and sent to the browser just like the rest of the template. The only difference between header and footer is that the header is not shown (and not editable) within the template editor of the web interface. It is designed to contain the template's configuration. If you ue the template editor only, you won't need it. The document is a html file mixed with donparser handlers. To edit a template, the best way is to open it in the webinterface's template editor. Template syntax This part shall explain the syntax of donparser handlers. You do not need to understand what the handlers do at this point. Donparser documents are normal HTML documents that include donparser handlers. These handlers are marked by brackets: [HANDLER]. Most times, handlers begin with the type of the handler. A valid example is [BROWSERPARAM myparam]. There are allso handlers without type definition, for example [DNSTANDARD_VERSION]. Handlers are replaced by the parser with their specific values during the parsing process. [DNSTANDARD_VERSION] would insert the curent version of Pagenews right into the HTML document, for example. Handler-in-Handler constructions are valid: [FUNCTION] [BROWSERPARAM functiontocall]] would call the perl function which is given by the browserparam functiontocall. ([BROWSERPARAM field] means that the value of an <input name = "field"> would be inserted to the document - see later) Donparser works from inner to outer handlers - that means you can be sure a handler within another handler is parsed before the handler that sourrounds him. even [FUNC[BROWSERPARAM completeit] myfunction] would work - for example if the form field "completeit" had the value "TION", the function "myfunction" would be called. Fancy, he? Most handlers have a type identifier: [TYPE myhandler arg1 arg2]... where TYPE can be for example "FUNCTION", "BROWSERPARAM,etc. Simple replacement handlers come without a type identifier: [DNSTANDARD_VERSION] for example What, if arguments have a whitespace within? Use the quote notation. [FUNCTION "myfunction" "arg1" "arg2"] is valid. You can leave away the quotes for the first argumentsm (=leftmost), but once you used them, you must go on using quotes for everything that follows on the right. For example, [FUNCTION "myfunction" arg1 arg2] would be invalid, [FUNCTION myfunction "arg1" "arg2"] is valid. Handler Types (When "calling template" is mentioned, the template which contains the handler is ment.)
<input type = "text" name = "myBrowserParam"> , and the form is submitted to a template which contains [BROWSERPARAM myBrowserParam], the handler will be replaced trough the value of your text-input field! Arguments can also be passed to templates by the URL, for example: news.cgi?myparam=myvalue&foo=bar
|
-> admin log-in
Powered by Pagenews DN 6.1.2 by Philipp Kindt