Changes between Initial Version and Version 4 of Ticket #4885
- Timestamp:
- Jan 4, 2013, 8:59:01 PM (11 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #4885 – Description
initial v4 1 Problem Statement: 1 Problem Statement: 2 2 3 When a user adds a new Subversion Path via the "Add Path" dialog, the user must provide the precise path details (example: I do this by browsing to the desired repository path, copy + pasting the path details, and trimming unnecessary characters). If the path is mistyped, or a path is not-precise due to unnecessary characters (example: extra '/' at the end), the path may be invalid. 3 4 … … 6 7 7 8 Enhancement: 8 * In addition to the current technique of going through the "Add Path" process (where a path is just typed in), enhance the interface by providing either: 9 1. Validate a Path 10 2. Browse for a Path 11 12 9 * In addition to the current technique of going through the "Add Path" process (where a path is just typed in), enhance the interface by providing either: 10 1. Validate a Path 11 1. Browse for a Path 13 12 14 13 Discussion of Options: 15 1. Validate a Path:16 If a user types a path in, give them the option to "Validate Path"... which would check if the path they entered is valid or not. If invalid, perhaps give the user some output to help diagnose the problem.14 1. Validate a Path: 15 If a user types a path in, give them the option to "Validate Path"... which would check if the path they entered is valid or not. If invalid, perhaps give the user some output to help diagnose the problem. 17 16 18 Of course, the extent of this 'diagnose output' could be curtailed due to security concerns. Which is why #2 is recommended below since it provides the same functionality as browsing the repository via the Trac web based system. This prevents providing any additional, unnecessary details about the system Trac is hosted on.17 Of course, the extent of this 'diagnose output' could be curtailed due to security concerns. Which is why #2 is recommended below since it provides the same functionality as browsing the repository via the Trac web based system. This prevents providing any additional, unnecessary details about the system Trac is hosted on. 19 18 20 19 … … 22 21 23 22 24 2. Browse for a Path: 25 Currently Trac's "Browse Source" toolbar button takes users to a website where users can browse a repository via their web browser. 23 2. Browse for a Path: 24 Currently Trac's "Browse Source" toolbar button takes users to a website where users can browse a repository via their web browser. 25 Using the "Browse Source" idea, the "Add Path" process can become more interactive. If a user wants to "Add Path": 26 1. User clicks "Search for Path to Add" 27 1. Present a browser popup window/use javascript to use the same window. This lets a user navigate to the desired path 28 1. Users selects a path in the browser window 29 1. The path selected shows up in the "Add Path" dialog 30 1. User pushes "Add" and path is added 26 31 27 Using the "Browse Source" idea, the "Add Path" process can become more interactive. If a user wants to "Add Path": 28 0. User clicks "Search for Path to Add" 29 1. Present a browser popup window/use javascript to use the same window. This lets a user navigate to the desired path 30 2. Users selects a path in the browser window 31 3. The path selected shows up in the "Add Path" dialog 32 4. User pushes "Add" and path is added 33 34 35 36 Recommendation: 37 Option 2, AKA: "Browse for a Path" 38 32 Recommendation: Option 2, AKA: "Browse for a Path" 39 33 40 34 Rational: 41 * Option 2 can also prevent common mistakes: 35 * Option 2 can also prevent common mistakes: 36 1. When adding a path, users may sometimes not include the "repository" portion of the path entry (when it *is* needed) 42 37 43 44 1. When adding a path, users may sometimes not include the "repository" portion of the path entry (when it *is* needed) 45 46 Example: suppose there are 2 repositories: 47 svn_repo_a 38 Example: suppose there are 2 repositories: svn_repo_a 48 39 and svn_repo_b 49 40 50 41 and directories: 51 a___________directory_in_this_repository(appearing in svn_repo_a)52 a_different_directory_in_this_repository(appearing in svn_repo_b)42 `a___________directory_in_this_repository` (appearing in svn_repo_a) 43 `a_different_directory_in_this_repository` (appearing in svn_repo_b) 53 44 54 45 When browsing, the browser window would know the repository name and the directory name the user is currently viewing: … … 57 48 58 49 These entries are thus generated and placed into the svn Autz config file: 50 {{{ 59 51 [svn_repo_a:/a___________directory_in_this_repository] 60 52 [svn_repo_b:/a_different_directory_in_this_repository] 53 }}}