On Tue, 22 Sep 2009 11:47:06 +0200, "A.L.E.C" alec@alec.pl wrote:

We need to implement sorting by message index. It should be simple on PHP side, but I don't know how to make sorting switch in UI. Currently we have sorting:

• by <message list column> ascending
• by <message list column> descending

and we need:

• by message index ascending
• by message index descending

So, 3-state switch in message list header (http://trac.roundcube.net/ticket/1485936) is not sufficient. Second option, use status column header for this is in my opinion not intuitive and we'll use probably this for different purposes in the future (e.g. column selection). I don't like also a third option, adding 'No.' column. Any ideas?

The message threading patch implements this using three clicks on the Date column sorts by index (for most IMAP servers index ~ date). This is useful when used with X-REFERENCES2/X-REFS where the 'natural' sort order is 'most recent message in thread'.

Chris

List info: http://lists.roundcube.net/dev/

I think we should not confuse end users with too many sort options.
People reading this list knows what it all means, but in a situation
with a lot of end users that arent that well informed, they really
dont know the difference is between 'sorting by message index' or
'sort by date header'. They'll just click until it looks good, and
leave it. I know from practice that they more often than not pick the
option that isnt the best for them (or for the server). Even a 3
state button is kind of strange to an end user. Cause what does
'unsorted' mean? Try and explain that to someone that doesnt know IMAP
servers or email details.

Possible option. By default pick either sort by date or sort by
message index, and let the user set the other option in a config
setting. Squirrelmail for instance has an option in setting 'Sort by
received date'. As an admin, I can then choose to hardcode that option
for every user and not allow them to change it.

Regards,

Cor _______________________________________________ List info: http://lists.roundcube.net/dev/

Cor Bosman wrote:

Possible option. By default pick either sort by date or sort by message index, and let the user set the other option in a config setting. Squirrelmail for instance has an option in setting 'Sort by received date'. As an admin, I can then choose to hardcode that option for every user and not allow them to change it.

Ok. So simple, I like it.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Hi,

On Tuesday 22 September 2009 18:50:37 A.L.E.C wrote:

Chris January wrote:

...

...

So, 3-state switch in message list header (http://trac.roundcube.net/ticket/1485936) is not sufficient. Second option, use status column header for this is in my opinion not intuitive and we'll use probably this for different purposes in the future (e.g. column selection). I don't like also a third option, adding 'No.' column. Any ideas?

The message threading patch implements this using three clicks on the Date column sorts by index (for most IMAP servers index ~ date). This is useful when used with X-REFERENCES2/X-REFS where the 'natural' sort order is 'most recent message in thread'.

As I said, 3-state switch does not allows to sort ascending and descending. I've got a fourth option. Clicking on date column header, but: - 1 click: date asc

• 2 click: date desc
• 3 click: index asc (+ column re-name to "Date (Index)")
• 4 click: index desc (+ column re-name to "Date (Index)")

I think the solution Cor Bosman proposed in another part of this thread is good. This one would also be acceptable for me, with one change: "Date (Index)" should be called "Date (Server)".

Patrick.

Key ID: 0x86E346D4 http://patrick-nagel.net/key.asc Fingerprint: 7745 E1BE FA8B FBAD 76AB 2BFC C981 E686 86E3 46D4

List info: http://lists.roundcube.net/dev/

A.L.E.C wrote:

"Use message index for sorting by date".

Implemented in r2983. Enjoy.