Bug 106255 - combined view needs improvements
Summary: combined view needs improvements
Status: CONFIRMED
Alias: None
Product: akregator
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR wishlist
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-05-25 10:01 UTC by Pierre Habouzit
Modified: 2021-03-09 04:11 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Pierre Habouzit 2005-05-25 10:01:38 UTC
Version:            (using KDE KDE 3.4.1)
Installed from:    Debian testing/unstable Packages

In the current state, combined view has some annoying usability issues.

1/ it's slow
2/ it does not shows if an article is read/unread/new
3/ it's not possible to tag an article


(2) is trivial, with the right css :
  make the text grey + changing the color of the articles title would do it nicely

(3) it's not possible to mark an article as read/unread/new/keep/... in the combined view, and that makes that view beeing the less usable, whereas it is the (IMHO) more readable. I dont really now how to achieve those taggin methods, maybe with some fancy icons in the article title ?

(1) it occurs because there is often too much articles in that view. I believe that either 
 -a- new+unread+tagged articles should be show by default in that view
 -b- or a classic [prev] page [1] [2] [3] ... [n] [next] navigation should be used

-a- is IHMO the safest thing to do, since -b- would hide articles that are modified in the past (I often have older articles updated, and they arent necessarily on top of the list). but maybe there is a -c- option that allow the number of articles shown to be limited, that I can't imagine ;)
Comment 1 Robert Buchholz 2007-08-11 05:06:31 UTC
What is the priority of this bug?

Especially the third point about not being able to mark one article read or important is quite unpleasant, at least for me.
Comment 2 Justin Zobel 2021-03-09 04:11:25 UTC
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.