Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FeatureRequest] Dev Env Settings Window Tool image selector table improvement #211

Open
janosmurai opened this issue Sep 17, 2024 · 2 comments
Labels
enhancement New feature or request hacktoberfest Issue to help with during Hacktoberfest2023

Comments

@janosmurai
Copy link
Contributor

janosmurai commented Sep 17, 2024

Add new columns to the current tool image selector table. The table currently looks like this:

image

The expected layout should look like this:

image

Columns

  1. Registry: The name of the registry where the image is stored. The cell should be empty if the image is local only.
  2. Namespace: The namespace inside the registry where the image is stored. If no namespace is used in the registry, or the image is local only, the cell should be left empty.
  3. Image name: The name of the image. (Without the tag)
  4. Tag: The tag of the image. Each tag available from a repo should be listed in a separate row.
  5. Availability: local, registry, local and registry

Navigation

The navigation input should remain the same, but the cursor should change. Instead of an asterisk, the line where the cursor resides should be highlighted.

For references to create the table see https://textual.textualize.io/widgets/data_table/

For the cursor and selection indicator see: https://textual.textualize.io/widgets/selection_list/


For axem internal use only:
Jira: https://axem.atlassian.net/browse/DEM-291

@janosmurai janosmurai added enhancement New feature or request hacktoberfest Issue to help with during Hacktoberfest2023 labels Sep 17, 2024
@meet0806
Copy link

Hi, @janosmurai I would like to work on this issue

@janosmurai
Copy link
Contributor Author

Hi @meet0806, sure, that would be great!

It's important to highlight though that the implementation should be based on Textual and not on the currently used UI elements. The currently used UI elements should be replaced with ones based on Textual, see #199 for more information. You can start working on this issue, but the solution can only be merged after the implementation of #199.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request hacktoberfest Issue to help with during Hacktoberfest2023
Projects
None yet
Development

No branches or pull requests

2 participants