Mercurial > p > roundup > code
comparison doc/upgrading.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 | 503d4c10f1f8 |
| children | 0cc9b954f1f1 |
comparison
equal
deleted
inserted
replaced
| 3695:01ea89743311 | 3696:790363e96852 |
|---|---|
| 10 then you don't need to do anything. If you're upgrading from 0.5.6 to | 10 then you don't need to do anything. If you're upgrading from 0.5.6 to |
| 11 0.6.8 though, you'll need to check the "0.5 to 0.6" and "0.6.x to 0.6.3" | 11 0.6.8 though, you'll need to check the "0.5 to 0.6" and "0.6.x to 0.6.3" |
| 12 steps. | 12 steps. |
| 13 | 13 |
| 14 .. contents:: | 14 .. contents:: |
| 15 | |
| 16 Migrating from 1.1.2 to 1.X.X | |
| 17 ============================= | |
| 18 | |
| 19 1.X.X Sorting and grouping by multiple properties | |
| 20 ------------------------------------------------- | |
| 21 | |
| 22 Starting with this version, sorting and grouping by multiple properties | |
| 23 is possible. This means that request.sort and request.group are now | |
| 24 lists. This is reflected in several places: | |
| 25 | |
| 26 * ``renderWith`` now has list attributes for ``sort`` and ``group``, | |
| 27 where you previously wrote:: | |
| 28 | |
| 29 renderWith(... sort=('-', 'activity'), group=('+', 'priority') | |
| 30 | |
| 31 you write now:: | |
| 32 | |
| 33 renderWith(... sort=[('-', 'activity')], group=[('+', 'priority')] | |
| 34 | |
| 35 * In templates that permit to edit sorting/grouping, request.sort and | |
| 36 request.group are (possibly empty) lists. You can now sort and group | |
| 37 by multiple attributes. For an example, see the classic template. You | |
| 38 may want search for the variable ``n_sort`` which can be set to the | |
| 39 number of sort/group properties. | |
| 40 | |
| 41 * Templates that diplay new headlines for each group of items with | |
| 42 equal group properties can now use the modified ``batch.propchanged`` | |
| 43 method that can take several properties which are checked for | |
| 44 changes. See the example in the classic template which makes use of | |
| 45 ``batch.propchanged``. | |
| 15 | 46 |
| 16 Migrating from 1.1.0 to 1.1.1 | 47 Migrating from 1.1.0 to 1.1.1 |
| 17 ============================= | 48 ============================= |
| 18 | 49 |
| 19 1.1.1 "Clear this message" | 50 1.1.1 "Clear this message" |