XML parser introduced, ext-surfbar rewritten, more EL code:

[mailer.git] / templates / xml / admin_data_template.xml

diff --git a/templates/xml/admin_data_template.xml b/templates/xml/admin_data_template.xml
index 632b23c2889736c03c9dc64a2419482b52a8f752..c517d7ac234e1ab798ea08b122697dd7808e5ae0 100644 (file)
--- a/templates/xml/admin_data_template.xml
+++ b/templates/xml/admin_data_template.xml
@@ -31,16 +31,17 @@ MA  02110-1301  USA
        <!--
        Call-back function which should all following parameter handled over
        to. This will always be type of string but we like homogene XMLs.
+       Keep 'name' empty for numerical array indexes (array keys).
        //-->
        <admin-callback-function type="string" value="adminFooEntriesBar" />
        <!--
        Array index from HTTP POST data array for identifying every data row
        //-->
-       <post-data-identify-index type="string" value="id" />
+       <post-data-identify-index name="" type="string" value="id" />
        <!--
        Name of the database table where the entries should be read/write from/to.
        //-->
-       <database-table type="string" value="table_name" />
+       <database-table name="" type="string" value="table_name" />
        <!--
        The following three lists must have the same count of list entries, else an
        error may occur.
@@ -53,7 +54,7 @@ MA  02110-1301  USA
                A column name list entry. The type is always string, or do you have
                numerical column names?
                //-->
-               <database-column-list-entry type="string" value="foo" />
+               <database-column-list-entry name="" type="string" value="foo" />
        </database-column-list>
        <!--
        "Filter" call-back functions to call back for piping the fetched data
@@ -63,7 +64,7 @@ MA  02110-1301  USA
                <!--
                A call-back function list entry
                //-->
-               <callback-function-list-entry type="string" value="someFooCallback" />
+               <callback-function-list-entry name="" type="string" value="someFooCallback" />
        </callback-function-list>
        <!--
        Extra parameters (2nd, 3rd, ...) for above call-back functions. If an array
@@ -76,8 +77,9 @@ MA  02110-1301  USA
                int, float, bool, array. If the type 'array' is provided, the parser
                searches for a tag called "extra-parameter-<value>-list(-entry)", by
                <value> is the value from the 'value' attribute. Please check out the
-               examples below.
-               Keep 'name' empty for numerical array indexes (array keys).
+               examples below. In addition to that you need to maintain <value>_list
+               in all corresponding elements, see admin_edit_show_surfbar_urls.xml for
+               an example.
                //-->
                <!--
                A simple string example with a numerical index, int and float are similar.
@@ -110,20 +112,20 @@ MA  02110-1301  USA
        <!--
        Wether to 'edit/delete/change' (change) the entries (true) or just read them for displaying (false)
        //-->
-       <enable-modify-entries type="bool" value="false" />
+       <enable-modify-entries name="" type="bool" value="false" />
        <!--
        The table column which should be taken for the ids (see first parameter).
        This' type can again only be 'string' (remember why?).
        //-->
-       <table-id-column type="string" value="id" />
+       <table-id-column name="" type="string" value="id" />
        <!--
        The table column which should be taken for user ids
        This' type can again only be 'string' (remember why?).
        //-->
-       <table-userid-column type="string" value="userid" />
+       <table-userid-column name="" type="string" value="userid" />
        <!--
        Raw userid column ($key) to skip which is always an invalid (?) entry
        This' type can again only be 'string' (remember why?).
        //-->
-       <raw-userid-column-key type="string" value="userid" />
+       <raw-userid-column-key name="" type="string" value="userid" />
 </admin-entry-meta-data>