[
http://jira.magnolia-cms.com/browse/MGNLUI-106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Weder updated MGNLUI-106:
---------------------------------
Summary: Implement sorting in trees (was: Sorting must work in trees
as well)
Description:
We're currently sorting nodes in the tree view alphabetically. That's also how
it has been specified. However, I've been notified by Jan that this is actually
NOT how it should work, since the *manual sort order in the tree is very
important*. In particular, it can be used to rearrange items in navigation
menus and to structure the page tree in any way a customer wants.
But sorting in trees still makes sense. Here's how I've research and devised
how this could work:
* for every column except the "Page" or first column, items are sorted *within
their hierarchy level only* (see below) and depending on the value/column type,
i.e. alphabetically, by date and time or (e.g. in case of the "Status" column)
in a pre-defined, more semantical sort order.
* if you sort by "Page" column, we return to the manual sort order and do not
show any sort arrow any more (there's no sort direction there anyway)
Sorting within a single level in the hierarchy is typically how sorting is done
in trees.
h2. Details on sorting within a hierarchy level
Sorting in a hierarchy (or tree) sorts all elements on a particular level among
themselves and does so on every level. If you e.g. have the following tree,
sorted by (node) titles, thus alphabetically, and in ascending order:
{code}
A
|--A
| D
B
|--U
{code}
..., if you then reverse the sort direction, you'll get:
{code}
B
|--D
| A
A
|--U
{code}
The mechanics shall are the same as if you do sorting in a list: you simply
click in the column header to sort by the attribute represented by that column.
Clicking the same header again changes the sort direction.
was:
Currently, you may only change the sort order in lists. However, you should be
able to also specify the sort order in trees.
The mechanics shall are the same: click on a column header to sort by the
attribute represented by the column. Clicking the same header again changes the
sort direction. The default sort order shall be to sort by name/title and in
ascending direction.
Sorting in a hierarchy (or tree) sorts all elements on a particular level among
themselves and does so on every level. If you e.g. have the following tree,
sorted by (node) titles, thus alphabetically, and in ascending order:
{code}
A
|--A
| D
B
|--U
{code}
..., if you then reverse the sort direction, you'll get:
{code}
B
|--D
| A
A
|--U
{code}
Updated the issue with new insights. This is a tougher job, but worth while the
effort.
> Implement sorting in trees
> --------------------------
>
> Key: MGNLUI-106
> URL: http://jira.magnolia-cms.com/browse/MGNLUI-106
> Project: Magnolia UI
> Issue Type: Sub-task
> Security Level: Public
> Affects Versions: 5.0 Alpha1
> Reporter: Andreas Weder
> Priority: Major
> Fix For: 5.0
>
>
> We're currently sorting nodes in the tree view alphabetically. That's also
> how it has been specified. However, I've been notified by Jan that this is
> actually NOT how it should work, since the *manual sort order in the tree is
> very important*. In particular, it can be used to rearrange items in
> navigation menus and to structure the page tree in any way a customer wants.
> But sorting in trees still makes sense. Here's how I've research and devised
> how this could work:
> * for every column except the "Page" or first column, items are sorted
> *within their hierarchy level only* (see below) and depending on the
> value/column type, i.e. alphabetically, by date and time or (e.g. in case of
> the "Status" column) in a pre-defined, more semantical sort order.
> * if you sort by "Page" column, we return to the manual sort order and do not
> show any sort arrow any more (there's no sort direction there anyway)
> Sorting within a single level in the hierarchy is typically how sorting is
> done in trees.
> h2. Details on sorting within a hierarchy level
> Sorting in a hierarchy (or tree) sorts all elements on a particular level
> among themselves and does so on every level. If you e.g. have the following
> tree, sorted by (node) titles, thus alphabetically, and in ascending order:
> {code}
> A
> |--A
> | D
> B
> |--U
> {code}
> ..., if you then reverse the sort direction, you'll get:
> {code}
> B
> |--D
> | A
> A
> |--U
> {code}
> The mechanics shall are the same as if you do sorting in a list: you simply
> click in the column header to sort by the attribute represented by that
> column. Clicking the same header again changes the sort direction.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
