hansva commented on issue #6529:
URL: https://github.com/apache/hop/issues/6529#issuecomment-3871113260
Never mind, we are currently showing all files.
We need a clear visual way to distinguish between files that can be opened
inside the application and those that cannot.
There is already an indicator, but it is not clear to the end user:
- Files that cannot be opened use a generic file icon.
- Files that can be opened use a specific file-type icon.
However, all menu actions are still available for every file, which is
misleading and incorrect.
This leaves us with two possible approaches:
1. Hide files that cannot be manipulated in the application.
2. Keep all files visible, but create a much clearer visual distinction for
non-openable file types.
Considerations:
- Discoverability vs. clarity trade-off
Keeping everything visible improves transparency but risks confusing the
end user.
- UI clutter
Showing all files could make the project view noisy and harder to navigate.
- File awareness
Users may still want to see that certain files exist, even if they can’t
open them.
- Git functionality
Users may want to use Git features (diff, history, status) on files that
aren’t openable.
- Project completeness
Showing all files gives a full and accurate picture of the project
structure.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
