Improve user experience when navigating / selecting

[lauraporta]

Here a few points I noted when I was using datashuttle that could suggest enhancements in UX:

• in "Make a new Project" when looking at the file tree to select my local path destination, it is unclear that I have to click at the folder name to select it.
• I would really like to have a back button to go to the previous screen once I enter the menu.
• ssh connection: if I don't type in the password it says "password and salt must not be empty"... but where is the salt?
• I didn't expect that my local folder had to have the same name as the remote one 😮 If it is different it creates a new folder in the remote and searches for derivatives folder there
• In custom transfer, if I select funcimg it does not deselect all

[Vishisht3]

@lauraporta Hello, I came across this issue, and I believe I can help, my solution would be as follows:

1. Make folders highlight and/or show a button on hover
2. Just implement the code <Button title="Back" onPress={() => navigation.goBack()} />
3. If salt is not needed, omit salt field and error but for advanced modes, show inline help (tooltip or info icon)
4. Show dialog if names differ; let user confirm or remap
5. Auto-deselect “all” if “funcimg” selected and vice versa

If you could assign this issue to me, I can get started, I would love to contribute

[JoeZiminski]

Hi @Vishisht3 thanks a lot for this, those are nice suggestions. It would be great to pick one of the topics and open a PR on them, you can choose the one you would most like to work on initially. A few notes on this:

1. This is a weird feature / bug of textual, and it is quite annoying. You need to first click for the widget focus to register, and then click again to get the actual desired behaviour. I think the best approach here is to dig a little deeper into the textual event system and determine exactly why this is happening. Then, we can contact textual if it is something they might be able to help with on their end, or we can patch it on our end such that clicking twice is not necessary. This is a slightly more advanced issue.

2. Is navigation.goBack() a textual thing? That looks interesting. Otherwise, we could track the last-viewed tab and expose either a button (although space is limited with textual because it is hard to change the button size) or a keyboard shortcut.

3, 4 We need to discuss a little more, don't worry about these for now.

5. I think this is a nice issue to work on, this has come up multiple times now. If all / all_datatype is checked every datatype checkbox will need to be turned off, or if any datatype checkbox is turned on all will need to be turned off (and all_datatype).

[Vishisht3]

@JoeZiminski Sorry for the late response. I will get started on issue no. 5
My apologies, navigation.goBack() is a React thing. As you mentioned, using a keyboard shortcut would be the best way to go.
Thank you for the insights, this is a great opportunity to learn!

[JoeZiminski]

No problem no rush at all, sounds good!