Ability to sort differently read and unread

[jazz@…]

I configured Gregarius to have unread items sorted from oldest to latest thus I can read them chronologically. But when I need to view read items, I have very old items first.

I would like to be able to sort read items from the latest to the latest while keeping the reverse ordering for unread items.

[mbonetti]

What do others think of this? I personally read all my feads latest first, so I'm not quite sure how I should handle this.

[mdodoo]

If we added another combo box to the top of each page next to the Read-Unread box, it would make it easier to switch being sorting methods. This could be a reasonable alternative to making yet another configuration option, in my opinion.

[gregarius@…]

I'm in favour of this as well

I'm sure I've asked for this before, but I can't find the hypothetical old ticket now...

I'm sure I've requested this though, because I remember saying that what gregarius seems to be doing is choosing the 10 oldest items in feed, then display those items in ascending order by date. I'd rather see it chose the 10 newest items; after that, whether they were displayed in ascending date order (the same as my unread feeds) or in descending date order (newest first) wouldn't matter much to me..

Hrm, I think I phrased it much better that time though.

Note that I'm only talking here about views (feed/folder/tag/vfolder) where all items are marked as read - if there are unread items, I only want to see them, and I want oldest first, because I'm picky like that..

[mbonetti]

Right. I'm not quite fond of another combobox, though: the interface is cluttered enough already, imo. So this'll be YACO or any other smart way you can suggest.

(What aboout a tiny "View properties" icon that, when clicked would display a dialog much in the vein of the item properties dialog, where one could set sort order, show read/unread, number of items to display... all this cookie or ajax based?)

[gregarius_trac@…]

I like the idea of the "view properties" box, so that it can be configurable per user, but the admin should also have the option to set the default for all users.

Perhaps splitting the options into a couple of different pages reduces the clutter? Most applications the size of gregarius have that many config options. I mean look at WP (though it's larger), it has pages and pages of config options.. That's what the admin side does, isn't it? configure stuff? ;-)

But yeah, to get back to my original point, "View Properties" would be nice. It seems everyone has their own way of viewing, and we should give them that.

[mbonetti]

in [878]. Note that this could have some nasty side-effects. Please report anomalies to the list.

Actually, the problem here is that we fetch read and unread items in a single query in most situations. We are defaulting to the old datedesc setting, but the best solution would be to run two distinct queries for read and unread items in ItemList::populate(), apply the right sort order then merge the lists.

Oh and I still think a feed properties dialog would be nice, but that wont make it into 0.5.2