451112 - Reviewers should be able to approve suggestions faster

Status: RESOLVED WONTFIX

(Webtools Graveyard :: Verbatim, enhancement)

Description

[Rubén Martín [:Nukeador] ❌ [away till Aug 31st]]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; es-ES; rv:1.9.0.1) Gecko/2008072820 Firefox/3.0.1
Build Identifier: 

The UI should be modified to allow reviewers approve lots of suggestions at once or in a fester way without having to edit string by string. Maybe Ajax could helps us with this problem.

Reproducible: Always

Comment 1

[Israel Saeta Pérez]

I suggest using checkboxes, "Select: All, None, With Suggestions, Opposite, etc." links and form buttons, like Gmail does, to get that.

Comment 2

[Wil Clouser [:clouserw]]

On pages like http://sm-cms01.mozilla.com:8081/en/languages/es/junk/messages.po?translate=1&view=1 you can click "View Suggestions" when suggestions exist to view them.  We were planning on putting the accept/reject AJAX icons that are visible on the edit page next to the suggestions on that page.

How does that sound instead of checkboxes?  I'm not sure how to map suggestions to checkboxes (e.g. if you have multiple suggestions per string what does "select all" do?)

Comment 3

[Israel Saeta Pérez]

You're right -I hadn't thought about strings with multiple suggestions... About the AJAX icons approach, for now I can think of some of its

* Advantages: You can accept/reject any suggestion with inmediate UI feedback.
* Disadvantages: It can be slower for slow computers and/or connections.

Comment 4

[Rubén Martín [:Nukeador] ❌ [away till Aug 31st]]

Then we need a "Expand all" option to see all suggestions at once and maybe "Validate all unique suggestions", the validations should happen without having to reload the page.

Comment 5

[Israel Saeta Pérez]

I agree with the "Expand all" and "Validate all unique suggestions" buttons, but I think we should always provide a non-AJAX method (with reloading) as fallback.

Comment 6

[Fred Wenzel [:wenzel]]

Closing out Pootle bugs from Verbatim component:

We're running Pootle trunk, and it's not a feature to be implemented on our end, but this might already be fixed.