Mercurial > p > roundup > code
diff doc/design.txt @ 3696:790363e96852
Sorting/grouping by multiple properties.
- Implement sorting/grouping by multiple properties for the web
interface. I'm now using @sort0/@sortdir0,@sort1/@sortdir1,... and
@group0/@groupdir0,... when generating URLs from a search template.
These are converted to a list internally. When saving URLs (e.g. when
storing queries) I'm using @sort=prop1,prop2,... and @group=... with
optional '-' prepended to individual props.
This means saved URLs are backward compatible with existing trackers
(and yes, this was a design goal).
I need the clumsy version with @sort0,@sort1 etc, because I'm
currently using several selectors and checkboxes (as the classic
template does, too). I don't think there is a way around that in HTML?
- Updated (hopefully all) documentation to reflect the new URL format
and the consequences in the web-interface.
- I've set the number of sort/group properties in the classic template
to two -- this can easily be reverted by changing n_sort to 1.
Richard, would you look over these changes? I've set a tag before and
(will set) after commit, so that it would be easy to merge out.
Don't be too scared about the size of the change, most is documentation,
the guts are in cgi/templating.py and small changes in the classic
template.
| author | Ralf Schlatterbeck <schlatterbeck@users.sourceforge.net> |
|---|---|
| date | Wed, 30 Aug 2006 20:28:26 +0000 |
| parents | 193f316dbbe9 |
| children | 0d561b24ceff |
line wrap: on
line diff
--- a/doc/design.txt Wed Aug 30 09:35:31 2006 +0000 +++ b/doc/design.txt Wed Aug 30 20:28:26 2006 +0000 @@ -1251,7 +1251,7 @@ /issue?status=unread,in-progress,resolved& topic=security,ui& - :group=priority& + :group=priority,-status& :sort=-activity& :filters=status,topic& :columns=title,status,fixer @@ -1275,11 +1275,11 @@ The example specifies an index of "issue" items. Only issues with a "status" of either "unread" or "in-progres" or "resolved" are displayed, and only issues with "topic" values including both "security" and "ui" -are displayed. The issues are grouped by priority, arranged in -ascending order; and within groups, sorted by activity, arranged in -descending order. The filter section shows filters for the "status" and -"topic" properties, and the table includes columns for the "title", -"status", and "fixer" properties. +are displayed. The items are grouped by priority arranged in ascending +order and in descending order by status; and within groups, sorted by +activity, arranged in descending order. The filter section shows +filters for the "status" and "topic" properties, and the table includes +columns for the "title", "status", and "fixer" properties. Associated with each issue class is a default layout specifier. The layout specifier in the above example is the default layout to be