[p4] P4Win vs P4V
RMartin at harmanbecker.com
Fri Jul 7 07:02:23 PDT 2006
Oh, I had a lot of them!
But I didn't look intensive at 5.2 or 6.1, because .... P4Win is better ;-)
I'll give it a shot if I have some more time.
Sure P4V becomes better in every release, but it is still far away from P4Win.
Did you tried the latest P4Win feature of capturing the ouput from a customized tool
to output pane? - Great!
> -----Ursprüngliche Nachricht-----
> Von: perforce-user-bounces at perforce.com
> [mailto:perforce-user-bounces at perforce.com] Im Auftrag von
> Zoltan Grose
> Gesendet: Donnerstag, 6. Juli 2006 08:50
> An: perforce-user at perforce.com
> Betreff: Re: [p4] P4Win vs P4V
> I've never had a data issue a refresh didn't solve.
> I've always assumed p4v was designed to poll less frequently
> than p4win does to make for better network performance
> (fewer, larger requests over constant polling). That was one
> factor that doomed SourceSafe for us; it simply didn't
> performance in non-LAN environments.
> I have an OSX and a Windows box and I load p4v on both of them.
> Honestly, I do 99% of my interactions thru the IDE
> integrations anyhow. But we're a small shop so there may be
> p4* features that we simply never use.
> On Jul 5, 2006, at 4:10 PM, Chris Weiss wrote:
> > I must admit, I'm suprised at the number of people who are
> using P4V -
> > I've found the refresh bugs to be pretty much fatal and
> assumed they
> > were in the app, has no one else run into these? Specifically, the
> > file trees in both the Depot Tree and Workspace views not
> updating to
> > reflect the current state of the local machine or files
> that were just
> > checked in (in certain cases, I'm forced to actaully exit
> the app and
> > reload to get an accurate local view). This is P4V 2005.2 (Jan 10
> > build) against P4D 2005.1
> > On 7/5/06, Jeff Grills <jgrills at junctionpoint.com> wrote:
> >> I think it's pretty clear that p4win is at least heading towards
> >> being officially deprecated since it's no longer part of
> the standard
> >> p4 Windows installer, but p4v is part of that installer.
> It used to
> >> be the other way around.
> >> j
> >> -----Original Message-----
> >> From: perforce-user-bounces at perforce.com
> >> [mailto:perforce-user-bounces at perforce.com] On Behalf Of Jason
> >> Williams
> >> Sent: Wednesday, July 05, 2006 1:45 PM
> >> To: Mark Allender
> >> Cc: perforce-user at perforce.com
> >> Subject: Re: [p4] P4Win vs P4V
> >> If you're on a non-Windows machine, P4V is about the only
> >> solution that I know of. (Whatever happened to TkP4 or was it
> >> P4TK?).
> >> Every time I've tried to use P4V, I've found it very
> unintuitive when
> >> compared with P4Win. It may accomplish the same thing,
> but it seemed
> >> to take a lot more effort (clicks, etc.). I seem to recall the
> >> terminology being different between the two clients as well.
> >> And since there hasn't been any official word of P4Win being
> >> deprecated, there hasnt't been a need to switch.
> >> --Jason
> >> _______________________________________________
> >> perforce-user mailing list - perforce-user at perforce.com
> >> http://maillist.perforce.com/mailman/listinfo/perforce-user
> > --
> > -Chris
> > _______________________________________________
> > perforce-user mailing list - perforce-user at perforce.com
> > http://maillist.perforce.com/mailman/listinfo/perforce-user
> perforce-user mailing list - perforce-user at perforce.com
Diese E-Mail enthaelt vertrauliche und/oder rechtlich geschuetzte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtuemlich erhalten haben, informieren Sie bitte sofort den Absender und loeschen Sie diese Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet.
This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the contents in this e-mail is strictly forbidden.
More information about the perforce-user