Open kcpevey opened 2 months ago
"internal"/"External" isn't a good description of what these are.
The menu is currently defined in:
Some functions are implemented in https://github.com/nebari-dev/jupyterlab-nebari-mode extension. For compatibility when jupyterlab-conda-store extension is disabled or not installed it will open the Environment Management tab externally in new tab.
We can add the divider easily. We can add non-clickable "Internal"/"External" entries. We can:
The problem will be if an admin disabled https://github.com/conda-incubator/jupyterlab-conda-store and now it does not open in JupyterLab.
I think I would prefer to change the menu items to show [↗] as the label can be set separately for the scenario when jupyterlab-conda-store
is installed vs when it is not.
I agree internal/external seems like the wrong labels. Conda store (Environment Management) is external to Nebari as well. It just happens to be developed by Quansight as well, but it's a separate open source project the same as Keycloak (User Management) or any of the others.
Update: I realize you mean internal/external windows, but it wouldn't have been clear to me without the explanation above.
I think I would prefer to change the menu items to show [↗]
I love this idea!
Context
The services menu in JLab behaves differently based on which of the options you choose. Its disorienting for users when conda-store opens within the JLab window, but other options open in a new tab.
A solution would be to visually breakdown the services menu so users have a concept that the behavior is different.
Here is an initial design for this breakdown:
Value and/or benefit
Users have a visual indication that some services are different from others and therefore the result of clicking on them is not disorienting.
Anything else?
No response