documentation update: link-targets & -popups, manual & custom fields widgets

This commit is contained in:
Ralf Becker 2005-11-11 07:04:36 +00:00
parent 1315d99b88
commit 1b78b1eed8

View File

@ -388,7 +388,8 @@ implement only a subset of XUL. Here are the main differences:</p>
a link to that methode = app.class.method is put around the label<br />
<b>3.</b> if set URLs in the content get activated<br />
<b>4.</b> name of form-element the label is for: gives focus to that element if the label gets clicked<br />
<b>5.</b> widthxheight if a popup should be used for the link, eg. 600x400
<b>5.</b> target for the link, eg. _blank<br />
<b>6.</b> width<i>x</i>height if a popup should be used for the link, eg. 600x400
</td>
</tr>
<tr>
@ -552,7 +553,11 @@ implement only a subset of XUL. Here are the main differences:</p>
<b>shows an image</b><br />
<b>Label</b> xml: <b>label</b>: the label is shown as tooltip (like html-title)<br />
<b>Name</b> xml: <b>src</b>: the name of the image to load, the image is search in the apps template-dirs<br />
<b>Options</b> xml: <b>options</b>: if set, a link to that methode = app.class.method is put around the image
<b>Options</b> xml: <b>options</b>: up to 4 comma-separated values:<br />
<b>1.</b> link to a methode = app.class.method for the image<br />
<b>2.</b> target for the link, eg. _blank<br />
<b>3.</b> imagemap<br />
<b>4.</b> width<i>x</i>height if a popup should be used for the link, eg. 600x400<br />
</td>
</tr>
<tr>
@ -735,6 +740,31 @@ implement only a subset of XUL. Here are the main differences:</p>
name contains no '.', it will be prefixed with the name of the template the widget is in plus a '.'
</td>
</tr>
<tr>
<td><b>Manual</b></td>
<td>
&lt;manual>
</td>
<td>no</td>
<td>manual</td>
<td>
<b>open the online help</b>: displays a small manual icon.<p>
<b>Name</b> xml: <b>id</b>: 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.
</td>
</tr>
<tr>
<td><b>Custom fields</b></td>
<td>
&lt;custom_fields>
</td>
<td>no</td>
<td>custom_fields</td>
<td>
<b>display custom fields</b>: the fields can be configured with admin.customfields.edit&appname={app}<p>
The indexes of the custom fields in content are prefixed with a hash (#).
</td>
</tr>
<tr>
<td><b>NextMatch</b></td>
<td>