Add example protocol for row buttons templating (which changes old row buttons protocol as well).
Detailed documentation will follow.
diff --git a/ListsProtocol.wiki b/ListsProtocol.wiki
index 785bbde..9a57636 100644
--- a/ListsProtocol.wiki
+++ b/ListsProtocol.wiki
@@ -259,20 +259,46 @@
"link": "http://my_row_edit_link"
},
"row_buttons": {
- "edit": {
- "caption": "Edit this User",
- "classes": ["class_1", "class_2"],
- "type": "redirect_simple",
- "parameters": {
- "link": "http://edit1",
- "new_window": true
+ "<dest_column>": {
+ "buttons_def": {
+ "edit": {
+ "caption": "Edit this user",
+ "type": "redirect_simple",
+ "classes": ["class_1", "class_2"],
+ "parameters": {
+ "link": "http://www.google.com",
+ "new_window": True
+ }
+ },
+ "delete": {
+ "caption": "Delete this user",
+ "type": "redirect_simple",
+ "parameters": {
+ "link": "http://www.youtube.com",
+ "new_window": True,
+ }
+ }
},
- "append_to_column": "key"
+ "template": "Template for {{ edit }} and {{ delete }}",
+ },
+ "<dest_column>": {
+ "buttons_def": {
+ "add": {
+ "caption": "Add this user",
+ "type": "redirect_simple",
+ "classes": ["class_1"],
+ "parameters": {
+ "link": "http://www.libero.it",
+ "new_window": True
+ }
+ }
+ }
}
}
}
}
]
+}
}}}
So, _data_ is an object indexed by key. In the example, you can see what the first iteration (fetching data from backend) should return. The key is actually an empty string. This key should represent the *GAE key of the last entity in the former iteration*. That is, if the last entity fetched is "key_test7" (as in the example), the next iteration should contain "key_test7" as the key of the array of objects in the _data_ object. So, the _data_ returned is indeed an *array of objects*, which has an empty string as index (if it's the first batch) or the GAE key of the last entity fetched in the former batch. Each object (which actually represents a row in the final list) has two objects inside:
