Edit List
You can create your own tags using XMLNuke. It is possible go to beyond the HTML. Your application or document doesn't understand HTML - just XML tags. The final layout is produced by XMLNuke using XSLT transformation and snippets.
See below for the funcionality.
Sample 1
<editlist
module="module:somemodule"
name="ELDEMO"
title="Sample 1 - EditList"
cols="4"
new="true"
edit="true"
delete="true"
view="true"
custom1="true"
url1="module:somemodule2"
img1="common/editlist/ic_custom.gif"
acao1="select"
alt1="Select Item"
>
<row>
<field name="">1</field>
<field name="Name">ONE</field>
<field name="Description">You need ...</field>
<field name="Listing">Another field</field>
</row>
</editlist>
| Name | Description | Listing | |
|---|---|---|---|
| ONE | You need to check the radio on the left side and click in one button below to activate this function. | Another Field | |
| TWO | The user chooses if the buttons are showed or not. | Another Field | |
How it works?
- The Editlist is responsible to call the module defined by module attribute after the button is pressed
- The module always receives two parameters: action it can be: new, edit, delete, view or a name user defined which can be: custom1, custom2, custom3 or custom4
- The other parameter is the value of the first column. This value is hidden. The parameter name is valueid
Other Options
The same data can be showed in different modes depending on XSLT templates or editlist attributes.
In the sample below the EditList uses checkboxes to select the values.
| Name | Description | Listing | |
|---|---|---|---|
| ONE | You need to check the checkbox on the left side and click in one button below to active this function. | Another Field | |
| TWO | The user chooses if the buttons are showed or not. | Another Field | |
Read only mode:
| Name | Description | Listing | |
|---|---|---|---|
| ONE | Here you can't select anything. | Another Field | |
| TWO | The user chooses if the buttons are showed or not. | Another Field | |
See XML of this page.
