selfoss
selfoss copied to clipboard
fossar
Mark all as read for a feed (feature request)
Hi,
I have some feeds that produce more than 400 articles a day (news). Some day, I can read some of them (articles) and mark the other as read as the day goes by. On some other days, I cannot.
The idea would be to have a "Mark all as read" that would mark all feed's items as read, and not just the one loaded in the browser. Indeed, with 100 articles loaded at a time, I sometime need to press "Mark as read" almost 10 times.
(This would not do the same as mark as read since it would mark all items from a feed as read in the DB, and not only those loaded in the browser)
Thanks, GLLM
Hi, I would like that too, but I am not sure how to incorporate it in the interface. If you or someone has a great suggestion I would love to implement it. :)
When writing my suggestion, I tought of 2 possibilities :
- putting in in the sources, not very good
- creating a top bar for a feed kind of managment just above the very first article. But this induces a bigger changes in UI ...
Well, Google Reader has a drop-down menu on the "Mark all as read" button to provide more options, so something like that could be a possibility.
Another approach that wouldn't need any UI changes at all would be to make the "mark as read" button behave differently when a modifier key is pressed. For example, clicking on "mark as read" marks the currently visible items as read, holding Ctrl while clicking on "mark as read" marks all items that apply to the current filter as read.
Of course that would at least have to be documented properly so that users could actually discover the feature.
Edit: Another option might be to implement #182.
@seanrand The idea of a drop down menu on the 'Mark as read' seems great ! :)
Moreover, it could enable implementation of other functions such as "Mark (all) as unread" ... which is sometime very handy when you click on mark as read by mistake !!
@seanrand I dont like the idea of changing the "mark as read" buttons default behavior. I actually would not click it until I dove into the source to see what it would actually do.
+1 for turning that button into a drop-down button though. That would be handy.
@MSylvia, well, the default behaviour when clicking would stay the same, just Ctrl+click would do something different... I don't really see a problem with that, as long as it's documented.
I guess you could even make the button text change when pressing Ctrl and hovering over the button, to show that it does something different now... might be a bit gimmicky though.
For the ctrl+click idea, I just made a quick jsfiddle to demo how I thought it might work: http://jsfiddle.net/AvuYa/
Actually, I kinda like this better than a dropdown. Downside is that it wouldn't work on mobile. Hmm.
Not fan of that one @seanrand, be it the way it works and the fact it's out of line for mobile ... :(
Regardless of the fact it does not always display what's being done... That's a quick try, OK. Just alpha ;)
@seanrand I like the idea / example, but... CTRL + Click on mac open a menu on a Mac (it's the same as the right click). One to keep in mind when adding this feature.
I am currently experimenting with UI modifications, so it will accessible from mobile as well.
It currently looks like this, the white knob is temporary:
The behavior would be, you click the "tag color box", which in my opinion does not necessarily need to produce the color picker pane immediately. Instead a menu will slide open below, providing various options, like the "mark all (of that tag) as red" button, which can also be used by other new feature.
I would highly appreciate your feedback on the approach. :)
Great idea @ochristi !!
In fact, this small pane dedicated to the tag/source could enable user to access many features :
- color picker
- mark all as read
- move up/down in list (to order tags :) )
- rename tag ...
As a feedback, I'd rather have this small "feature pane" the way the color picker looks : not changing the tags/sources list layout, but overlaying on the articles list on the right.
I guess if this "feature pane" idea is kept, we'll need an icon (currently the picked color) : could be a tool that appear when hovering the color icon black tool sign over colored background ?
GLLM
@ochristi : any news on the try you did previously & which looked quite good ! ??
I think extending the Mark As Read button to have a small down-arrow next to it:
-------------------
| Mark As Read | V |
-------------------
With the down arrow showing a small drop-down with "Mark All as read" as an option.
What's the sense about marking only visible/loaded entries anyway? Due to infinite scrolling, you can never be sure which entries are actually marked when you're not at the end of the list. Thus I recommend to send selfoss.filter here and altering \controllers\Items::mark() to understand those filters.
If this is desirable, I'll implement this.
@jantman Unfortunately, the button only marks the visible items as read. This feature request wants to mark every single one.
@jtojnar Ah ok, sorry, my mistake. Most of the feeds I follow provide fewer items than my pagination setting.
+1 this feature would really help. Just marked 4600 entries as read because I didn't check my feed for a few days, I would appreciate a "mark all read" too.
@PhrozenByte
What's the sense about marking only visible/loaded entries anyway?
Yeah, I do not think it makes much sense when infinite scrolling (auto_stream_more) is enabled. Changing the button to really only mark the items visible on the screen (e.g. using intersection observers) would be fine with me.
@girvo’s idea to add a submenu sounds reasonable too.