[p4] P4Win Enhancements - Cris Holdorph - com.perforce.perforce-user

5 messages in com.perforce.perforce-user[p4] P4Win Enhancements

From	Sent On	Attachments
Ryan Gribble	18 Mar 2003 16:02
Cris Holdorph	18 Mar 2003 16:13
Jonathan Arnold	19 Mar 2003 14:30
Cris Holdorph	19 Mar 2003 15:35
Dave Lewis	19 Mar 2003 15:46

Subject:	[p4] P4Win Enhancements
From:	Cris Holdorph (hold...@unicon.net)
Date:	03/18/2003 04:13:39 PM
List:	com.perforce.perforce-user

I can't speak for p4win, but I wish this kind of functionality existed in the 'p4' program. We moved a large team of developers from cvs to perforce. A bunch of people were used to using 'cvs update' to figure out what files came up as a ? to identify which ones they needed to "cvs add". Luckily I found a work around script someone on this list came up with, but.... it would be so much nicer to have the functionality in the main client.

---- Cris J H

On Wed, Mar 19, 2003 at 10:03:21AM +1000, Ryan Gribble wrote:

Hello all,

We have made a couple of suggestions to perforce about improving the way P4Win handles "files not in the workspace" namely changing the icon/color of the files not in the workspace (currently it is too hard to see them in the file list) and also adding a command (similar to check consistency) that lists the files not in workspace in a listbox, with functionality to add the files from there (rather than just listing text in the status pane).

Anyone else who feels these improvements would be desirable could let perforce know, and add their names to the request.

This is the email we received back from Perforce:

------------- From: Steve Borrett [mailto:support at perforce.com] Sent: Tuesday, 18 March 2003 10:25 PM To: Wayne Donovan Subject: Re: Suggestion of Possible Improvement... (CALL#466598)

Hi Wayne,

Selecting "View | Local View of Client Tree" is a useful method of visually identifying files that exist in the Client Workspace path, but that don't actually exist in Perforce repository (referred to below as orphaned files). However, the diagram below will highlight that the orphaned file "Copy of Globals.bas" is not immediately noticeable that it does not exist. I think it would be advantageous to

make this icon orphaned files a more noticeable colour, say a medium-warning colour such as Orange, etc.

I agree that it is somewhat difficult to tell, without looking quite hard, the difference between the "not synced to client" and the "not a versioned file" type icons. The difference is only fairly subtle.I am not sure if a different colour, or a completely different icon would be the best solution here, but I shall certainly log this with the developers.

Also, it would be "nice-to-have" if the Perforce Client provided a list box that lists all files in the Workspace that are not in Perforce. This list box should also provide a method to add these files to the default or new changelist, plus provide a tick-box to show or hide files in the sub-folders.

By running the "Check Consistancy" command for the selected files you will get a list of edited files and those not yet added to Perforce. However, this list will appear in the status pane and doesn't provide any easy steps to sort out these files. I shall log your suggestion with our developers.

Hope the above suggestions prove to be useful in improving what is already a great product.

Glad you like it. Thanks for the feedback, please let us know if you have any more queries/comments.

regards,

Steve.

********************************** Steve Borrett Technical Support Perforce Software Europe **********************************

-------------

Software Quality Engineering UNiTAB Limited Brisbane, Australia