comparison 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
comparison
equal deleted inserted replaced
3695:01ea89743311 3696:790363e96852
1249 An index view specifier looks like this (whitespace has been added for 1249 An index view specifier looks like this (whitespace has been added for
1250 clarity):: 1250 clarity)::
1251 1251
1252 /issue?status=unread,in-progress,resolved& 1252 /issue?status=unread,in-progress,resolved&
1253 topic=security,ui& 1253 topic=security,ui&
1254 :group=priority& 1254 :group=priority,-status&
1255 :sort=-activity& 1255 :sort=-activity&
1256 :filters=status,topic& 1256 :filters=status,topic&
1257 :columns=title,status,fixer 1257 :columns=title,status,fixer
1258 1258
1259 1259
1273 of issues with values matching any specified Multilink properties. 1273 of issues with values matching any specified Multilink properties.
1274 1274
1275 The example specifies an index of "issue" items. Only issues with a 1275 The example specifies an index of "issue" items. Only issues with a
1276 "status" of either "unread" or "in-progres" or "resolved" are displayed, 1276 "status" of either "unread" or "in-progres" or "resolved" are displayed,
1277 and only issues with "topic" values including both "security" and "ui" 1277 and only issues with "topic" values including both "security" and "ui"
1278 are displayed. The issues are grouped by priority, arranged in 1278 are displayed. The items are grouped by priority arranged in ascending
1279 ascending order; and within groups, sorted by activity, arranged in 1279 order and in descending order by status; and within groups, sorted by
1280 descending order. The filter section shows filters for the "status" and 1280 activity, arranged in descending order. The filter section shows
1281 "topic" properties, and the table includes columns for the "title", 1281 filters for the "status" and "topic" properties, and the table includes
1282 "status", and "fixer" properties. 1282 columns for the "title", "status", and "fixer" properties.
1283 1283
1284 Associated with each issue class is a default layout specifier. The 1284 Associated with each issue class is a default layout specifier. The
1285 layout specifier in the above example is the default layout to be 1285 layout specifier in the above example is the default layout to be
1286 provided with the default bug-tracker schema described above in section 1286 provided with the default bug-tracker schema described above in section
1287 4.4. 1287 4.4.

Roundup Issue Tracker: http://roundup-tracker.org/