job000361
Closed
When adding a branch to a project provide the full (completed) depot path.
Most of the information is available and as the user types the branch name you can auto update the depot path.
Most of the information is available and as the user types the branch name you can auto update the depot path.
- Status
- Closed
- Project
- perforce-software-workshop
- Severity
- A
- Reported By
- Paul Allen
- Reported Date
- 9 years ago
- Modified By
- Thomas Gray
- Modified Date
- 9 years ago
- Owned By
- thomas_gray
- Type
- Feature
Increased priority, as this is happening more frequently.
I can't find the Job so I guess I must have emailed @matt_attaway and yourself. Another cool feature which is sort of related is to have a workspace setup for the user.
A simple button on the project home page that allows you to create a workspace and download a
.p4configfile. The button would create a workspace spec for the user; auto generate a name using the users ID and project name, then calculate the View and set the Host to 'null' as that would be unknown. You may need a popup to ask for the local 'root' for the workspace. Then we create a '.p4config' file for the user to download (filling out P4PORT, P4CLIENT, etc...).If you really want to push the boat out, then we could add a button to 'clone' the project using DVCS.
@paul_allen, I've got a fix for the path info - take a look at the project add/edit functionality around branch paths and let me know what you think.
I like it; simple and effective. I did a quick test and found two minor points:
Could you start the path with '//' to give a stronger indication it represents a Perforce depot path.
Perhaps even use 'Depot Path' as a <label> then a new line with the path in a fixed width <code> block.
When deleting the branch name the last character remains, would it be better to go back to 'branchid'?
Thanks for the feedback - I'll get that sorted asap.
Cleaning up open jobs - this one's been sorted for a while.