Note: I'm opening this issue to discuss this. I'm not sure yet about this, but now that we have the job items overview, this is starting to make more and more sense and it would allow for some UX improvements that would like to see.
Right now, we have two different views, both filter on the type explicitly. That was a lot easier to get started and initially, we didn't have the job items view, so the jobs view was still the main interaction point and i didn't want to "pollute" that.
Things to think about/would have to be implemented...
* Exposed filter for job type, show job type. Maybe a special state icon for them instead (loop, infinity, ...?). Legend would have to show it then.
* local action would move to jobs overview
* Status and others might need special cases for continuous, open should show them, what about active/unprocessed? Maybe we could expose the continuous type filter as part of state, would be consistent with showing it as state. We would definitely need a custom filter plugin then, as we'd dynamically filter on different fields.
* I'd like to have access control for all those things (filter, type, legend, local task) based on the existence of a translation provider (plugin) that supports continuous. When there are none, don't show any of that. Would avoid a lot of confusion for many users that couldn't use it anyway.
* We need to make sure to not show progress/words/tags for them (import: also not preload/calculate it), as there might be a huge amount of job items. Although progress could be argued about, maybe only show status of active ob items. not sure about performance.
* Should we make job items the first local task/menu link to indicate that is the main day-to-day overview (for reviewers)?
| Comment | File | Size | Author |
|---|---|---|---|
| #41 | merge_normal_and-2678332-41.patch | 34.62 KB | thenchev |
| #41 | merge_normal_and-2678332-40-41-interdiff.txt | 4.02 KB | thenchev |
| #40 | merge_normal_and-2678332-40.patch | 31.68 KB | thenchev |
| #40 | merge_normal_and-2678332-38-40-interdiff.txt | 3.93 KB | thenchev |
| #38 | merge_normal_and-2678332-38.patch | 31.8 KB | thenchev |
Comments
Comment #2
berdirSee screenshots in #2676118: Improving continuous job form., if we do not hide the add form, we need a better UI.
Comment #3
miro_dietikerMuch wanted. The current overview at admin/tmgmt is overlong and as a user i'm loosing overview in the current items listed.
Still not sure about the exact naming that will result on admin/tmgmt when the two are merged.
Is it then "Jobs" and will show items - or "Job items" and offer an alternate job tab? ;-)
We could also say "Jobs + Items" but that might be a bit creative.
Yeah, i think the job items should be the main action point and jobs are more hidden.
Comment #4
miro_dietikerAlso providing the tabs from before.
Would be great to have an exact resulting structure outlined as list or visually proposed.
Comment #5
berdirHuh? This is about merging the two *job* overviews. And moving job items before/above jobs. Then there is no label question, it's simply "Jobs", like now?
I don't know how you want to merge Jobs into job items or have it hidden behind that? I'm just talking about switching the order around.
Comment #6
thenchev commentedAre we going for something in this direction?
Comment #7
miro_dietikerHa! No idea where i was with my thoughts.
Yeah let's merge the job overviews first and then discuss how to continue.
Comment #8
thenchev commentedFor now showing job type as text. Do we want an icon here or maybe in the states we can add an ring around it to indicate its a continuous job so we can loose the job type, just a thought. Painted one around a state so we can see how it looks.
Moved.
Removed all for now for continuous.
Done.
Work in progress. Continuing with the 2 more steps and fixing tests.
Comment #10
johnchqueThe idea of adding a circle around the icon looks good, maybe we can use the same color of the icon to make it fit better. would be an option to avoid adding an extra column. :D
Comment #11
berdirwe also have to change the parent class to avoid that the data for this is loaded.
About the icon. All other states have no meaning for continuous. So I think a completely separate icon would be better.
Comment #12
thenchev commentedModified parent class.
Added an image for continuous. This is just an png, I have to configure gimp and online converters are horrible for svg. If someone wants to work on the svg that would be great :)
Comment #14
johnchqueNice icon idea, IMHO this one with this color would be a good idea for continuous.
I have uploaded the icon on a txt file, to use it just change the extension to .svg
Comment #15
thenchev commentedUsing the svg
Comment #17
johnchqueDiscussed with @Miro, this icon should be good for continuous jobs. (It is the same icon in gray color). Also change the extension to svg to use it.
Comment #18
thenchev commentedThis should fix some tests and added new image.
Comment #20
thenchev commentedUps wrong entity type id. Cache wasn't cleared properly.
Comment #22
mbovan commentedDiscussed now with @Denchev and we are not sure what are the possible job states for continuous jobs?
Is it:
- Only "Continuous" = Active - entity types and providers selected
- Unprocessed - a continuous job with no entity types or providers selected
- And possible and in the future "Paused" - a continuous job was active but then all entity types are unselected which makes a job "Inactive"?
What about Finished/Aborted? Do we want to support this for continuous jobs as well at some point of time?
Comment #23
thenchev commentedDidn't run the tests after the rebase have to see here if i broke something.
So first i have a question about custom access check for entity.tmgmt_job.add_form in tmgmt.links.action.yml. Do i have to extend LocalActionDefault and get some access check in or is there some other way?
Also we have Ignore status changes for continuous jobs that introduces new sates for continuous. Are we going in this direction now? Should we maybe first commit that issue and i work on top of that?
Comment #25
thenchev commentedAccess check for add continuous job link and tests.
Comment #27
thenchev commentedTesting if this fixes tests.
Comment #29
thenchev commentedComment #30
berdirNow we have an interesting problem. We have an update function that creates this view.
We need to make sure that updating from the previous beta version works. It doesn't need to result in the exactly same configuration, but it shouldn't break.
So we likely need to at least disable the update function that adds that view. And maybe do some more changes.
Test by installing beta2 (switch to that tag), then update to the latest version with your patch, run updates and see what happens.
If it fails, fix it. If it kind of works but the is missing some filter/fields that's OK. But please post a screenshot of that.
We have continuous exposed as job status now, lets use that instead of adding another filter. That should already just work.
This looks like a bad rebase, make sure you merge the latest changes.
did you check that it works when you add a new translator that has this ability, without clearing any other caches?
We might need addCacheTag('config:tmgmt_translator_list') on both the allowed and forbidden access result.
Instead of just removing this, we should check the job status filter now here. By default, it's shown, showing e.g. active jobs only should not show it, selecting continuous jobs should show it.
We lost this test, we still need to check that continuous jobs can't be submitted.
I guess it fails because we do have jobs now that can be submitted. You can fix that by switching to the continuous filter (I think submitting the form doesn't work with views, just copy the URL with the active filter).
Comment #31
miro_dietikerSome notes from my first test.
So i applied and reinstalled.
If i go to job overview, i see the state "Continuous" in the exposed filter, but neither a job nor a button to create it. The reason for this is that i didn't have any translator that supports ContinuousTranslatorInterface. I thought we want to hide the states then completely.
I still don't get how i can make the continuous stuff fully show up.
When adding a continuous job (Suddently the button still appeared, no idea why) i see "Google (unsupported)" although i have google applied with the latest patch to implement ContinuousTranslatorInterface.
The continuous icon is still green instead of grey like defined above. Also we start to have many icons - i'm losing overview.
I selected all source items and clicked the "Check for continuous jobs" button. And another item was created for an item that was already in a job.
Yeah, that item was previously added to a different translator but it still pending. So i have the item now twice on the pending job item list...
Also after bulk adding, i have the job item for "TMGMT Demo" (from tmgmt_demo) but the item does not show up on the sources overview as pending item. I guess the reason is that the job is in one of the new continuous job states. But that's wrong.
Comment #32
berdir* Yes, continuous should only be shown when there are continuous translators. This isn't even part of this issue, but I forgot to point that out in #2682771: Ignore status changes for continuous jobs. Lets fix it here.
* Everything should show up if you have a translator that supports continuous, which according to the tests, seems to be working fine.
* Yes, as already discussed, continuous jobs currently only check in their own context for existing job items. That's for #2679949: Never allow duplicate submission of an item while in process to generalize.
* Again yes, the active job item check is likely not including the new job state. Since that is also not related to this issue, lets fix that separately, with tests.
Comment #33
johnchqueAbout the icons I think the gray and turquoise color icons have been added in #2682771: Ignore status changes for continuous jobs to make the difference with the inactive state.
Comment #34
mbovan commentedI got the same problem. In the initial load source and target language are not properly set which tells Google that these "languages" are not supported. When you change a target language, there is an ajax update and languages are properly set - Google supports translations again.
There is a message in checkout settings for this: Google can not translate from Not specified to English..
Edit: I see this is at least a week old problem.
As we have two states for continuous jobs now (continuous and continuous_inactive), #2682771: Ignore status changes for continuous jobs added green (continuous) and gray (continuous inactive) icons.
Comment #35
mbovan commentedAgreed with @Denchev that I will check #30.1
Made some changes in update functions. It seems it's working fine, some filters are not correct/working (like open jobs for continuous jobs). The screenshot below.
Comment #36
berdirDon't renumber update functions. Just remove the content of the one we no longer have, and comment that it was removed as we no longer create this view.
Comment #37
mbovan commentedFixed.
Comment #38
thenchev commentedShould cover #30
and from #31 removed continuous from exposed filter when no continuous translators are available.
Comment #39
berdircan we make this available somewhere, e.g. in continuous manager, so we don't have to duplicate that code in multiple places?
What I meant is to keep the function and have the comment inside.
Comment #40
thenchev commentedCovers #39
Comment #41
thenchev commentedThis test should now fail because of the add continuous button not appearing after we install an translator that supports continuous.
Comment #43
berdirOk. So there's a problem with translator dependencies. They are missing and that results that in the test, we do not actually remove and re-create them.
However, after that it still fails, despite me seeing he right cache tags.
This could be a core bug. The attached patch passes for me with the also attached core patch. *Somehow*, in my testing, #cache of the links don't bubble up. Could be because above we have the content key which doesn't contain anything except #cache and children, I don't know. Note that the core patch is actually incomplete and is missing to properly merge cache tags of multiple local actions, but it's enough to confirm this.
Considering to comment this test out for now and open a follow-up. I can live with having to clear cache manually for now in this scenario.
Could use someone else confirming that the core change indeed fixes it.
Comment #45
thenchev commentedWith the core patch is works for me test is green and in the ui it behaves like it should.
Comment #46
thenchev commentedThought we wanted a follow-up for the add continuous job button?
#2685445: Add continuous job button not displayed when installing continuous translator
Comment #48
thenchev commentedRevering changes from #43
Test should be passing now.
Comment #49
miro_dietikerNot so sure about the icon situation. I'm much unsatisfied about our status usability. Too many icons now instead of simplification through a few icons.
But that can be a followup! :-)
Comment #50
miro_dietikerComment #51
berdirNice!
This looks good enough to me to commit it. We have some follow-ups.
beta to beta update is a bit tricky because the job state filter still has the group configuration which no longer works so well. I guess we can ignore that for now and just tell users to re-import the default view.
Comment #52
berdir