Add unique colors to "Workers", "Task Stream" etc buttons or reorganize to more easily find each

[kpasko]

Since the arrangement shifts depending on the size of the jupyterlab window, it is often difficult to locate a particular view/tab. Adding a unique color, (e.g. "Progress" is always teal, "Profile" is always purple, and the like) or some other disambiguation would be a nice addition.

[jrbourbeau]

@kpasko is the order always the same? I.e. "Progress" is the fix button, "Task stream" is the second button, etc.

[kpasko]

Sadly no, the ordering is different each time

[jrbourbeau]

Maybe keeping the same order would solve the "where is the X plot?" issue

[ian-r-rose]

We get the list of charts from individual-plots.json endpoint in the distributed dashboard. They are given as an unordered JSON object, but we could sort the keys before displaying them.

Since different spins of the dashboard might expose different dashboard charts, it's tough to assign predictable button colors in full generality here. We could add a suggested color field in distributed, though (perhaps selecting from the dask brand colors?) and pick them up when rendering the options

[kpasko]

Would help, although I still thing a visual cue would be nice if laid out as-is.

locating "6" in an m x n grid where both m and n can change is still not always straightforward.

If they were consistent and simply displayed as a vertical list (a la files / terminals tabs) that would do it.

color is just a cognitive thing of "okay i always click red, blue, and brown", but i understand your point about staying consistent when different flavors roll out

[mrocklin]

+1 on sort order, which should be easy.

We could do colors, maybe by theme. Memory-related plots could be darker orange, processing-related plots could be lighter orange, etc.. I agree that this is a decision that we would want to make on the dask/distributed side.

Alternatively, maybe we should zoom out a bit and ask what the right way to lay out these choices is. The "field of buttons" choice made sense early on, but may no longer make sense. Does anyone have any thoughts for alternative ways to provide these options?

[mrocklin]

Maybe something more like the vanilla JLab menu would make more sense

[kpasko]

The vanilla style makes sense to me. It could also eliminate need for color coding by having category sections — i.e replace {dask, extension manager,…} in referenced img with {memory, processing,…} or the like. // Extra bonus points if in addition to above categories there was a collapsible “layouts” section allowing you to CRUD and toggle visibility of preferred dashboard layouts

…

On Sun, Jul 18, 2021 at 8:29 AM Matthew Rocklin ***@***.***> wrote: Maybe something more like the vanilla JLab menu would make more sense [image: image] <https://user-images.githubusercontent.com/306380/126072992-b8ac9bad-2a71-43f7-9ad9-013adbe2484d.png> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#179 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABI2Z4X3T7XXWP3PBNAVT3TYLXMHANCNFSM4ZNCYDHA> .

[mrocklin]

If we could clone Ian then I would be all in favor of implementing a saveable layouts option :)

…

On Sun, Jul 18, 2021 at 11:22 AM kpasko ***@***.***> wrote: The vanilla style makes sense to me. It could also eliminate need for color coding by having category sections — i.e replace {dask, extension manager,…} in referenced img with {memory, processing,…} or the like. // Extra bonus points if in addition to above categories there was a collapsible “layouts” section allowing you to CRUD and toggle visibility of preferred dashboard layouts On Sun, Jul 18, 2021 at 8:29 AM Matthew Rocklin ***@***.***> wrote: > Maybe something more like the vanilla JLab menu would make more sense > > [image: image] > < https://user-images.githubusercontent.com/306380/126072992-b8ac9bad-2a71-43f7-9ad9-013adbe2484d.png > > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > < #179 (comment) >, > or unsubscribe > < https://github.com/notifications/unsubscribe-auth/AABI2Z4X3T7XXWP3PBNAVT3TYLXMHANCNFSM4ZNCYDHA > > . > — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#179 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACKZTGSJUEMAITJE54GFMLTYL5T7ANCNFSM4ZNCYDHA> .