From 1b78b1eed8a5cc50031e4198c7e646de7b1c9039 Mon Sep 17 00:00:00 2001 From: Ralf Becker Date: Fri, 11 Nov 2005 07:04:36 +0000 Subject: [PATCH] documentation update: link-targets & -popups, manual & custom fields widgets --- etemplate/doc/reference.html | 34 ++++++++++++++++++++++++++++++++-- 1 file changed, 32 insertions(+), 2 deletions(-) diff --git a/etemplate/doc/reference.html b/etemplate/doc/reference.html index 2f8f396042..fe806bee17 100644 --- a/etemplate/doc/reference.html +++ b/etemplate/doc/reference.html @@ -388,7 +388,8 @@ implement only a subset of XUL. Here are the main differences:

a link to that methode = app.class.method is put around the label
3. if set URLs in the content get activated
4. name of form-element the label is for: gives focus to that element if the label gets clicked
- 5. widthxheight if a popup should be used for the link, eg. 600x400 + 5. target for the link, eg. _blank
+ 6. widthxheight if a popup should be used for the link, eg. 600x400 @@ -552,7 +553,11 @@ implement only a subset of XUL. Here are the main differences:

shows an image
Label xml: label: the label is shown as tooltip (like html-title)
Name xml: src: the name of the image to load, the image is search in the apps template-dirs
- Options xml: options: if set, a link to that methode = app.class.method is put around the image + Options xml: options: up to 4 comma-separated values:
+ 1. link to a methode = app.class.method for the image
+ 2. target for the link, eg. _blank
+ 3. imagemap
+ 4. widthxheight if a popup should be used for the link, eg. 600x400
@@ -735,6 +740,31 @@ implement only a subset of XUL. Here are the main differences:

name contains no '.', it will be prefixed with the name of the template the widget is in plus a '.' + + Manual + + <manual> + + no + manual + + open the online help: displays a small manual icon.

+ Name xml: id: optional name of the manual page (as index into $content or direct). + If no manual page is given, the link included the referer as _GET param. + + + + Custom fields + + <custom_fields> + + no + custom_fields + + display custom fields: the fields can be configured with admin.customfields.edit&appname={app}

+ The indexes of the custom fields in content are prefixed with a hash (#). + + NextMatch