Community
Participate
Working Groups
Current repository configuration dialog is quite busy and is overusing foldable sections. It would make sense to use multiple property pages instead (like in other Eclipse Platform UI). Foldable sections have some usability issues and force user fold/unflod those sections, when all unfolded also dialog either don't fit into the screen or user have to use scrolling and generally folding UI is unfriendly to work with without mouse and harder to observe and explore. There are other advantages of multi page properties. Those pages can carry additional information, for example, linking projects in the workspace and other advanced settings, such as configuration for the repository specific team vcs commit templates. Also, connector could contribute connector-specific pages that might be used for repository configuration and management (i.e. create new project, module, etc).
-1 on this suggestion until we have more input from either integrators or users. For all connectors other than the Generic Web Repository Connector I find the current UI much more simple than the multi-page UI, and it has the good benefit of encouraging connectors to have concise additions. For the Generic Web Repository Connector a multi-page UI would be better, but that is only because that connector does not follow our (yet undocumented) guideline of only having the user specify credentials and connectivity settings. So instead of having this percolate to all connectors the generic web repository connector could have customized UI. I don't see an accessibility problem for keyboard use since tab and arrow keys work for navigating and expanding the folded sections. Will bring this UI idiom up with the Eclipse UI Working Group when we do a review of the Mylyn UI.
(In reply to comment #1) > only because that connector does not follow our (yet undocumented) guideline of > only having the user specify credentials and connectivity settings. And it never will because it doesn't make sense for this particular case. > So instead of having this percolate to all connectors the generic web repository > connector could have customized UI. That is exactly what this bug report is for, because current API prevent necessary customizations. > I don't see an accessibility problem for keyboard use since tab and arrow keys > work for navigating and expanding the folded sections. That hurt. UI should allow key accelerators and provide Alt-key jumps.
No plans to do this.
