Re: [Feedreader-development] Wishlist

[Karsten H. <mai...@kh...>]

Nicole Simon wrote:

> * Basic install:
> - refresh should be 1 hour not 15 min (or even better at least 2 hours)
> - javascript should be disabled
> 
> * description
> mark all news / mark all headlines read is confusing. one of them should be
> 'mark everything everywhere read'.
> 

If i remember correctly, "Mark all headlines read" appears just if you 
rightclick on "MyFeeds", right? If so i think we should name this 
something like "Mark everything read". Suggestions for the name?


> * OK / Cancel
> They are all wrong way. Usual behaviour ist to have 
> 							OK     Cancel
> 
> not other way round.

Jep, this strikes me regularly, too.

> 
> * Adding new Feed
> When standing on a folder, the add new feed should have this 
> folder set as suggestion.
> 

Good point.

> * Please enter name / in folder both don't have alt-shortcuts.
> 

Is this still in New Feed?
Do you need shortcuts there? See next point.

> * Focus is on 'Finish'. If I press Tab, I get to "Create Feed in Folder"
> but the next tab does not bring me back. Try pressing it, you need 10 times
> until you rereach Finish.
> 

I see.
How about:
If you enter this window the focus is in the edit field for the feedname.
Then you can Tab to the folderlist, then Tab to Finish.
Back can't get reached by Tab, you have to click with the mouse.


> * Toolbar button
> Standing on a feed, focus on the feed, not any headline. If you press alt-m
> headlines are not marked read.
> 

Please more details ;)
The focus is on the left in the treeview or right on the headlines?

Alt-M is not the shortcut for marking read. It's Ctrl-r.

> * Mark as unread and Menu Action have same shortcut

Does "Mark as unread" has a shortcut?! It exists only in the Popup-Menu 
or  if you put it on the toolbar (or am i wrong).
We need an icon for this.

> 
> * Wrong Tab result
> Standing on a feed, pressing tab. Expected result: first message is
> highlighted. Real result: headline 0 is selected.

Ok.

> 
> * Go back one message
> Cause 'jump to next unread' does not follow the actual structure where I
> stand but a kind of internal ranking (eine mir nicht nachvollziehbare

I have no blogs, just news feeds like Spiegel, Slashdot, etc.
Does this mean that e.g. you stand on the first headline then press 
Ctrl-Z, the fourth headline is activated, then press Ctrl-z the second 
is activated?
I've never seen this.

> Reihenfolge), I sometimes want to go back but can't see, where I was
> before. Backspace would be fine to jump one message back.
> 

We can implement this but Backspace is not the right key for this.
It will get eaten by the browser window, so we can't catch it if the 
browser has the focus.
Maybe Ctrl-b


> 
> or - better: make 'jump to next unread message' really a 'if you are in
> blog n, jump to next unread message means to next unread message in this
> blog or if none more available, to first unread in blog n+1' :o))
> 

Minus the confirmation window, i guess? ;)


Karsten