[p4] P4Win vs P4V
brad.holt at autodesk.com
Wed Jul 5 08:44:48 PDT 2006
We've actually gone back and forth on this one over time. P4Win has
always been generally preferred but the pendulum has swung the other way
at times. A real decider for us was that P4V had the nice diff and
merge GUIs bundled whereas P4Win required a 3rd party utility for this
if you didn't like the all text differ that came with it. Similarly,
P4V included the really cool Revision Tree and Time Lapse View tools.
The good news now is that the hooks for these tools (even recently the
diff and merge) are available in P4Win. You just need to make sure that
the user also has P4V installed for these to be available.
Also, as you mentioned, P4V is definitely p4's strategic UI for the
future. P4Win seems to just be in maintenance mode, though it is nice
of p4 to enable the hooks to the cool new p4v stuff.
So for us the answer is for users to have them both installed (we
include them both in our installer image) and the users can decide for
themselves. The downside is that some submission aid tools that we had
written relied on the registry from P4Win, and these broke when folks
used P4V. Also, any extra help documentation and training gets more
complicated when you have to cater to all the different clients.
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of Marshall, Tony
Sent: Wednesday, July 05, 2006 5:20 AM
To: Robert Cowham; perforce-user at perforce.com
Subject: Re: [p4] P4Win vs P4V
>>Note that p4v does have safe automatic resolve - just calls it
Can you elaborate on this? I can't see such an option.
>>You can also link submitted changelists to jobs, just have to do it
>>View submitted changelist dialog and click Edit button (little
I don't see an Edit button on the Submitted Changelist dialog.
Perhaps I'm using an old version - 2005.2/94595.
From: Robert Cowham [mailto:robert at vaccaperna.co.uk]
Sent: 05 July 2006 13:15
To: Marshall, Tony [IT]; perforce-user at perforce.com
Subject: RE: [p4] P4Win vs P4V
I'd try p4v latest beta - it's got quite a bit better with latest
That said, it's still missing a couple of useful p4win features (e.g.
doesn't check for unchanged files, submit doesn't handle unchanged files
nicely, flexible filtering e.g. of submitted changelists and depot
Note that p4v does have safe automatic resolve - just calls it
You can also link submitted changelists to jobs, just have to do it from
View submitted changelist dialog and click Edit button (little
> -----Original Message-----
> From: perforce-user-bounces at perforce.com
> [mailto:perforce-user-bounces at perforce.com] On Behalf Of
> Marshall, Tony [IT]
> Sent: 05 July 2006 09:52
> To: perforce-user at perforce.com
> Subject: [p4] P4Win vs P4V
> What do Windows users tend to use most - P4Win or P4V? I
> thought that since P4V is cross-platform, it would be the
> strategic direction that Perforce would go when developing
> the product. So I recommended that we use it in our team
> before evaluating both of them. However, I'm finding that
> P4Win has useful features that P4V (2005.2) doesn't - e.g.
> Safe automatice resolve, linking submitted changelists to
> jobs, viewing workspace files not in the depot. That's really
> perforce-user mailing list - perforce-user at perforce.com
perforce-user mailing list - perforce-user at perforce.com
More information about the perforce-user