-
The new grid UI is growing on me (disclaimer: I like marmite) but there are a couple of niggles that make it slightly painful to use. The TaskGroup nesting is nice, and has led to me aggressively using task groups in my dags. However, there's a couple of things that bug me with the task group rows. The first is already raised as an issue, as it's clearly an actual bug (#24410). The second I'm raising in the discussions since I wouldn't presume to be the greatest UI guy, but, the problem is that it's really hard to distinguish the task-squares from the group-squares. Look at the (redacted, sorry) dag below. Quick: In the middle 1100 group, how many (failed) tasks are there? I've been using the grid for a while now, and I still see 4 tasks, and 2 failures, but it's actually only 3 total / 1 failure. A primary reason for this confusion is that the "top" task group doesn't get a line above it, so it kinda looks like it belongs to the group above it. However, I was wondering if (as well as adding the line above it) whether or not it was worth distinguishing the group rows some other way. I was notionally thinging right-angle triangles, e.g. something like (please excuse the crude hand-edit of the screen grab): In this case, it becomes immediately clear which are groups and which are not. One alternative approach that has occurred to me is to resurrect the outlined/not-outlined behaviour of the old tree view. In the old tree, it was used to distinguish between scheduled/manual dag runs; perhaps here we could outline the group tasks? Thanks! |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 4 replies
-
One other thing that would help massively (but I assume it's already been raised elsewhere, even though I can't find it), would be to left-align the grid squares, so there wasn't a massive gulf of white space between the row labels and the grid... |
Beta Was this translation helpful? Give feedback.
-
I tihnk separating group squares from task squares is something that might be useful (and it's been raised some time with the "border" that @bbovenzi added). I agree that task "box" could be visually distinct. I'd say (and that was my idea before) is not to change the shape but make it look like there are multiple boxes or a bit "bulky" (maybe a subtle bottom-right shadow for the box would be nice) But as usual design-by-committee is bad idea and @bbovenzi has an upper-hand with those "ui look & feel" thingies |
Beta Was this translation helpful? Give feedback.
I tihnk separating group squares from task squares is something that might be useful (and it's been raised some time with the "border" that @bbovenzi added). I agree that task "box" could be visually distinct. I'd say (and that was my idea before) is not to change the shape but make it look like there are multiple boxes or a bit "bulky" (maybe a subtle bottom-right shadow for the box would be nice)
But as usual design-by-committee is bad idea and @bbovenzi has an upper-hand with those "ui look & feel" thingies