[p4] Scripting P4win.
Jeff A. Bowles
jab at pobox.com
Mon Mar 31 19:20:55 PDT 2008
I think that there might be a different way to get this information.
1. The time/date/IP/everything (including command args) is written to
the Perforce server log, if you've turned on the right debugging flags, and
that should get you 90% of the information.
2. If you also have a "spec depot", you can have versioning of your
client workspace specs (and label specs) so that you can match things up, if
[Aside: I admit that it'd be easier to track as a trigger, but that's not
available to you for all operations - only the ones that modify forms such
as "client workspace spec" and "job" and "changelist".]
When in doubt, ask the support folks. They've heard it all (I assure you)
and might have a good way to save you
a bit of time for your project.
(ps. Howdy do, Rick! Hope you're well.)
On Mon, Mar 31, 2008 at 4:22 PM, Jim Tilander <jim_perforce at tilander.org>
> 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.
> On Sun, Mar 30, 2008 at 5:42 AM, Robert Cowham <robert at vaccaperna.co.uk>
> > Short answer is no.
> > Longer answer is:
> > - p4win is officially deprecated (currently minor updates only to work
> > new server versions) and all new work is going into p4v
> > - no event hooks currently provided, custom tools (and some flexibility
> > context sensitive right click menus) are possible
> > So it would be possible to wrap a sync action in a custom tool, but
> then you
> > need to train your users to do this rather than the bare sync action.
> > Others have chimed in with some useful suggestions.
> > Robert
> > > -----Original Message-----
> > > From: perforce-user-bounces at perforce.com
> > > [mailto:perforce-user-bounces at perforce.com] On Behalf Of Jim Tilander
> > > Sent: 29 March 2008 18:00
> > > To: Perforce Users
> > > Subject: [p4] Scripting P4win.
> > >
> > > Does anyone out there know of a way to add scripts to p4win
> > > events? I want for example hook into the sync commands, so
> > > that whenever a sync finishes it can trigger some external
> > > command with the appropriate information. Basically what I
> > > need is some plugin architecture for p4win that lets me
> > > override certain things.. I don't want to embark on writing a
> > > new client :)
> Beware of architect astronauts.
> perforce-user mailing list - perforce-user at perforce.com
Jeff Bowles - jeff.a.bowles at gmail.com
More information about the perforce-user