The two column layout does not work as job items list gets too long (high in this case) and translators usually do not provide such long/high output for the left pane with checkout info.
So I redesigned the UI in a way where each pane comes after another, while there are three main panes:
- Translator pane (place for checkout settings and info)
- Job data pane (job items and suggestions)
- Messages pane
See the attached screenshots for both - job in checkout and submitted job.
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | tmgmt-job_checkout_ux-2109757-5.patch | 7.49 KB | berdir |
| #5 | tmgmt-job_checkout_ux-2109757-5-interdiff.txt | 4.6 KB | berdir |
| #4 | tmgmt-job_checkout_ux-2109757-2.interdiff.txt | 3.69 KB | blueminds |
| #4 | tmgmt-job_checkout_ux-2109757-2.patch | 5.83 KB | blueminds |
| #1 | tmgmt-job_checkout_ux-2109757-1.patch | 4.38 KB | blueminds |
Comments
Comment #1
blueminds commentedand here comes the patch
Comment #2
miro_dietikerPersonally, i don't like the double-fieldset "job data" - "job items".
Guess it should be "job items" only and make suggestions a children of it.
Anything complex inside the items that is reason enough to add a separate container?
Comment #3
berdirWondering if the order should be the other way round. At least for submitted mode, there you mostly interact with the items (review them), the remote job info is interesting but not used as frequently I think.
And for submit, the same might be useful, a) for consistency and b) because it makes sense to check the job items + possibly add suggestions *before* you submit the job. So conceptually, that comes first.
And yes, we have a lot of nested fieldsets.. how does it look if we simplify that a bit?
Confused about the suggestions thing, is that how it's displayed by default or did you load them? If they're not loaded, you should only see the load button.
Comment #4
blueminds commentedRemoved the double fieldset. Updated ordering. A few fixes.
I experimented with the UI and conclusion is that putting whatever panes in columns does not make sense as all three panes are lists with lot of data. What we can do to increase the UX is to introduce tabs.
- Tabs for job in submittable state would be: Job items (that is to review the content going for translation), Translator settings (do all the needed configuration)
- Tabs for submitted job: Job items (the overview/status of the items), Translator info/actions (whatever info or poll mechanism, the mappings), Messages (local logging)
What do you think?
Comment #5
berdirNot sure about tabs, especially on checkout. Because the translator selection is very important, I don't want to hide that in a tab, nor do I want to hide the job items, especially as suggestions will get more useful later on. and possibly more things. I think this is just fine as as a review process: Check that the items are ok, possibly do something with them => After the job is complete , proceed to translator selection/settings.
We discussed this and made a few more changes:
- We improved the suggestions structure, the load button was moved out of the fieldset, which is no longer displayed by default. Also hid the add button if there are none to add and changed Title to label to be consistent with the list above.
- The no info thingy was also displayed on checkout, fixed that
- The label of the translator information thing used the translator label, I think it's not necessary to repeat that, instead using "Translator information" (collapsible) for submitted job and "Configure translator" (non-collapsible)
Comment #6
cgalli commentedApplied patch and tested. Works fine.
It is compact enough to show on one page for translators plugins without settings. Will certainly be helpful when a translator gives more choice.
We can try to use CSS to make the settings as wide as possible as to keep the 'Submit' button above the waterline as often as possible.
Comment #7
berdirCommitted and pushed.