[p4] Scripting P4win.

[Ivey, William]

I did not realize that. I seem to remember java as a
prerequisite once upon a time, maybe for some ancillary
tool. (I've been installing it mostly to get the extra
tools for P4Win so I haven't paid much attention to it
other than to play with it from time to time.)

> because it didn't Perforce up to expectations.

Heh, I kind of like the phrase that typo created.
Perforce has given me higher expectations.

-Wm

-----Original Message-----
From: Stephen Vance [mailto:steve at vance.com] 
Sent: Tuesday, April 01, 2008 3:26 PM
To: Ivey, William
Cc: perforce-user at perforce.com
Subject: Re: [p4] Scripting P4win.

FYI: P4V is not Java-based. The project to create the Java-based 
cross-platform UI was killed years ago because it didn't Perforce up to 
expectations. P4V is Qt-based.

Steve

Ivey, William wrote:
> I've never understood the emphasis on P4V myself. Since 97% of
> my users interact with Perforce only from Windows, and the rest
> use the command line or run scripts, the cross-platform aspect
> is pretty useless to us. (Our products are heavily cross-platform,
> not our developers.) A crisp, reliable GUI with native feel is
> much more important in terms of the developer's experience.
>
> Those who do use it (usually out of loyalty to all things Java
> based :-) don't make use of any of its special abilities. (I
> find the few things P4Win does better to be more useful, day to
> day.)
>
> I did like the admin tool, but it was buggy and I've gone back
> to the command line for admin tasks. (I'll probably try it
> again and see if the recent patches made it less frustrating.)
>
> Just my experience and preference.
>
> -Wm
>
>
> -----Original Message-----
> From: perforce-user-bounces at perforce.com
> [mailto:perforce-user-bounces at perforce.com] On Behalf Of Jim Tilander
>
> So what's it for, well. I'd like to track what each clientspec is
> doing, what kind of operations they've done and basically go back in
> time from the client's point of view. I guess I could do with just a
> server command that would dump the whole clientspec state for me. I
> basically don't want to roll out my own client, nor to "train" anyone
> to do a custom sync option (that way lies endless support :)
>
> As for p4win, the day that perforce stops distributing that piece of
> software is the day I stop using perforce. It's the one redeeming UI
> client, p4v is a sea of usability misunderstandings and confusion
> (hey, I get confused in there, and I fancy myself somewhat familiar
> with perforce, how can I expect a new user to have any chance?). I
> can't make odds and ends of that thing, and it made the fatal try to
> support multiple platforms within one (gui) toolkit. Cross platform
> only means that it's equally crappy on each platform. No, give me a
> native client, one that looks and feels like the platform I'm on.
>
> Furthermore, it is my opinion that p4win should be officially
supported.
>
> /j
>
> _______________________________________________
> perforce-user mailing list  -  perforce-user at perforce.com
> http://maillist.perforce.com/mailman/listinfo/perforce-user
>
>   

-- 
Stephen Vance
www.vance.com