On page /privatemsg first three select elements appear:

Current folder: [________] |  Select: [________] | Type: [________]

While "Current folder" means that just messages are displayed that are stored in a certain folder, "Select" means that chosen select options leads to marked messages. "Type" seems handle the display again.

At the bottom of the page up some buttons appear (depending on folder):

Mark as read | Mark as unread | Delete | Move to folder [________]

These action work on the "marked" messages.

My suggestion is that everything that has to do with marked messages should be in one place to make it easier. When I just saw the form the first time, I wondered if there was something wrong because the display hadn't changed. Later I saw that the checking of messages changed and that this would prepare the actions that are buttons at the bottom.
As a general usability rule, everything belonging together should be presented together.

This would lead to a page like this:

Current folder: [________] | Type: [________]

---------------------------------------------------------------------------------------
[ ] | Type            | From   | Subject                             | Date 
---------------------------------------------------------------------------------------
[ ] | private-message | MarcoR | My privatemsg usability-suggestion  | 2007-11-16 18:00
[ ] | private-message | MarcoR | My privatemsg usability-suggestion  | 2007-11-16 17:00       
[ ] | private-message | MarcoR | My privatemsg usability-suggestion  | 2007-11-16 16:50                      
---------------------------------------------------------------------------------------
Select: [________] Mark as read | Mark as unread | Delete | Move to folder [________]

I'm new to the privatemsg 2.0 branch. Looking into the code the first time, it seemed that buttons above and at bottom belong to different forms, while the same db query is used for "Select" and "Type" options, so I think patching will be very difficult........ What do you say, lords of the code?

Comments

berdir’s picture

Status: Active » Closed (won't fix)

No new features are added to old branches so I'm setting this to won't fix. If you are still interested in this feature, you are welcome to either change this issue to a more recent branch (meaning: 6.x-2.x-dev) or open a new issue.