v2 FileDialog - UX

[tznind]

@tig rather than discuss in the PR #2927 (comment) I thought I would go over some of the decisions I made when writing FileDialog.

I wanted to challenge myself to create the best ux possible for this dialog.

I would like to ensure all this works correctly with the new key handling. And if there is a way to work 'with the api' rather than against it that would be ideal.

Caption in TextField

To save real estate the search box shows the 'label' within the box itself (as long as there is no text typed)

Windows

Terminal

Tab Completion

I wanted tab completion to work 'as good as on command line directly'. This means when you start typing a path and hit it auto completes.

If there are multiple things that match the Up/Down key - cycle those.

Navigation

I wanted up/down/left/right to move you to a sensible part of the dialog.

So for example when in the PATH section pressing down should move to the Table. Unless there are multiple autocomplete options to cycle in which case they should cycle.

There are other things like if you are at the top line of the table and press up the focus will move to the path.

I could go on but want to highlight the goal here which is to make the ux be reactive and sensible about how it interprets the key press based on its current state.

Summary

Happy to talk through any and all of these decisions, identify any ways they could change to work better with new API for keypresses and/or they could inform the API development.

[tig]

To be clear, this comment...

All of the navigation complexity in file dialog is complex and confusing. I'm curious why you didn't just depend on the tab stop tab index functionality.

was not abou the functionality or look & feel. I love it.'

It was about the code, esp the NavigateTo stuff and alll the event handlers.

I see all that and wonder "why doesn't the library just make that easy?"