aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJoey Hess <joey@gnu.kitenet.net>2010-04-02 17:37:38 -0400
committerJoey Hess <joey@gnu.kitenet.net>2010-04-02 17:37:38 -0400
commit1faf9b08e16bde9b4b0d72620fcef79c715e64de (patch)
tree24741c7b122ec97b99d162510d582a84a178ebe0
parent9e7dcefd7ed9424de20706f63c7bab5182c5df78 (diff)
downloadikiwiki-1faf9b08e16bde9b4b0d72620fcef79c715e64de.tar
ikiwiki-1faf9b08e16bde9b4b0d72620fcef79c715e64de.tar.gz
idea
-rw-r--r--doc/todo/allow_plugins_to_add_sorting_methods.mdwn8
1 files changed, 8 insertions, 0 deletions
diff --git a/doc/todo/allow_plugins_to_add_sorting_methods.mdwn b/doc/todo/allow_plugins_to_add_sorting_methods.mdwn
index 67d85f6f8..e1e05e81c 100644
--- a/doc/todo/allow_plugins_to_add_sorting_methods.mdwn
+++ b/doc/todo/allow_plugins_to_add_sorting_methods.mdwn
@@ -63,6 +63,14 @@ NIH'd sorting mechanisms:
>>>> is required to have params. They should be optional,
>>>> to match the documentation and because most sort methods
>>>> do not need parameters.
+>>>>
+>>>> I wonder if it would make sense to add some combining keywords, so
+>>>> a sortspec reads like `sort="age then ascending title"`
+>>>> In a way, this reduces the amount of syntax that needs to be learned.
+>>>> I like the "then" (and it could allow other operations than
+>>>> simple combination, if any others make sense). Not so sure about the
+>>>> "ascending", which could be "reverse" instead, but "descending age" and
+>>>> "ascending age" both seem useful to be able to explicitly specify.
>>>> --[[Joey]]
## Documentation from sort-hooks branch