Get rid of this AJAX madness

Jose Reyero - January 5, 2009 - 01:58
Project:Localization server
Version:6.x-1.x-dev
Component:User interface
Category:feature request
Priority:normal
Assigned:Unassigned
Status:closed
Description

Though the UI is really beautiful with all these icons and stuff dinamically shown and hidden, I don't think it helps at all when you want to get the task done. Also it is quite error prone...

I'm missing some simple HTML administration page that allows bulk operations, pretty much like the node administration page, so you can see a list of translations / suggestions / untranslated strings, then you can fill in the blanks / checkboxes / whatever, then take a look at the page to see if everything is ok, then submit... Wouldn't it be great?

I see a lot of work has been put into the AJAX part which is very nice if you just submit or approve a single string but it turns out to be *really hard* when you have a full page listing of strings to approve or translate....

So please... let's try to do it the old fashion / usable way, at least for new features... This may eventually speed up development for the whole thing.

(Happy new year btw)

#1

Gábor Hojtsy - January 5, 2009 - 07:55

I am not sure I am getting it. The node admin page lets you do ONE thing with ALL nodes selected. I am not sure how it applies here. Do you intend to have "pick the first suggestion for each string regardless of its content"? How does this mode apply here? If you are in suggestion approval mood, you can just filter for suggestions to approve and pick the right suggestion for each string as you go. If your browser dies on the middle of the page, then fine, half of your work was already saved.

#2

Jose Reyero - January 5, 2009 - 12:12

I don't mean exactly like the node admin page, but something similar. Show all the strings along with suggestions, a check box for each (with 'select all' option) then with selected ones: approve / discard all.

Here's how the current UI works, at least for me, when you filter with 'has suggestion':
- You get a list of strings and current translations, then these blue stars to the right, that let you know you have suggestions but not even how many.
- You click on the star, then suggestions show up but the current translation is hidden. If:
a) I want to see the current translation to compare (sometimes the difference is subtle), click again on 'Translation' arrow and try to memorize before clicking again on the star because it seems you cannot see both (current translation and suggestions) at the same time.
b) Discard suggestion/s: then if more than one all the others are hidden, you have to click again on the star and discard for each of them (to discard 2 suggestions you need at least 4 clicks)
c) Approve suggestion, that's the only case that works almost right, just one click, then approved.
d) Edit suggestion before approving it. Then if there are three suggestions and the one you want is the last one, you need first to discard the first 2 before you can edit that one (2 clicks each)

I know this all can be improved. My point though is that it would need a lot more ajax work just to be as usable as a simple list with checkboxes and buttons.

When I mean it is 'error prone' is that with all this it is just a click and the thing is done, no possible roll back (and the approve/reject buttons are dangerously close). While using a normal form, you'd be able to check all your options, then review, then submit.

My two most common use cases (as translations admin):
- I want to quickly aprove all the suggestions available for strings with no translations yet after a quick look -> clicking nightmare.
- I want to quickly discard a list of useless suggestions someone has posted by uploading again a full .po file -> clicking nightmare

#3

Gábor Hojtsy - January 5, 2009 - 13:42

Well, we can always display the translation with the suggestions, it should not be hidden. When you edit an existing translation for example, we also keep showing the existing translation. Also, if you modify a suggestion to approve as translation, when you submit your modified text, all other suggestions are *automatically* marked declined, so there is no need to clicking around there whatsoever. We can build in similar logical byproducts, and also a "discard all" button on suggestions.

It was also suggested (look at our existing issues and comment on the existing issue please) that we should have an "automatically expand suggestions on page" option, so that you could work in an "approval" mode, when you don't need to click to see all suggestions, just need to decide.

#4

Jose Reyero - September 10, 2009 - 10:35
Status:active» closed

Well I just wanted to raise the issue of AJAX not always being the solution. I see we are making some great progress on the UI front, http://localize.drupal.org/node/117

So closing, thanks for replying.

 
 

Drupal is a registered trademark of Dries Buytaert.