[wishlist] Support the "occasional user" use case
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Gwibber |
Confirmed
|
Wishlist
|
Unassigned | ||
Bug Description
Hello, I feel like gwibber works great for the use case of someone who is constantly watching it to see what's going on. However I wanted to propose a different use case which implies several new features (nothing to major).
The use case is a person who wants to avoid distraction and checks the status a couple times per day, keeping it minimized other times. Here are the problems I've encountered while using gwibber like this:
Problem:
It's hard to tell which updates you read last, therefore which updates are new/unread
Solutions:
1. Create a marker line showing the message that was newest when the window was minimized or became hidden. Pidgin has a plugin that does this, it works nicely. The marker line moves when the window is hidden again.
2. Allow selecting a tweet so that when you switch windows and switch back some time later the message you selected is easy to locate.
3. Never scroll the window automatically, therefore whatever you were looking at when you minimized is what you will see when restored. New tweets are put on top of the stack and the scrollbar elongates so that you can scroll up to see new ones. This is good and helps with the next issue but probably isn't enough.
Problem:
When new tweets come in the window scrolls. If you wait a few hours between reading and want to catch up it might take several minutes. During that time when new tweets come in the window scrolls causing you to lose your place. Sometimes this happens several times before I get caught up.
Solution:
1. See number 3 from above
Just my humble opinion, thanks for the good work.
| Fernando Miguel (fernandomiguel) wrote | #1 |
| Changed in gwibber: | |
| importance: | Undecided → Wishlist |
| status: | New → Confirmed |
| Andrew Conkling (andrewski) wrote | #2 |
| Doug Warner (doug-warner) wrote | #3 |
| Tom Metro (tmetro+ubuntu) wrote | #4 |
Point one, is already address on bug 297233