I tend to agree. I was very skeptical about p4web when we switched to Perforce,
but I'm now almost as comfortable in p4web as p4win or the command line. We have a
number of serious gripes, however, which affect its usability all of which have been
reported to Perforce for months, but none of which seem to have been fixed in 2001.1.

Opening multiple files for edit.

If you navigate to a depot directory in thew path browser which contains a lot
of files (say 500, for good measure) and you want to open 10 for edit, you select open
for edit in the left menu and hit run. You are given the option of opening all files in the
directory or selected files, but the checkboxes for the selected files default to
"checked", so you are forced to uncheck 490 checkboxes to accomplish your goal. I can't conceive
of why they default to "checked" in the absence of any more sophisitcated way to manage
multiple selections. This is one I really thought they could fix for 2001.1, but they
confirmed it won't be.

CodeWarrior/P4Web interaction

We have some Macs where files opened for edit from the CodeWarrior IDE show up
as opened for edit in p4Web's path browser, but not in any changelist in p4Web - default
or otherwise. I thought they were being opened into a different client or
something, but every lead has turned out a dead end. The result of this is that they simply
cannot be submitted without backing them up, reverting them, opening them from within
p4Web, copying them over, and submitting. It makes no sense for files which show up as opened
by the current user and client in the path browser not to also show up in the default
changelist. Users who have this problem simply cannot use the IDE perforce client at all. We
have not explored the MPW command line because our Mac users are militantly opposed to it
& they's rather use the above procedure.

Random slow behavior

We have a small number of Macs where p4web performs dramatically slower than
other identical machines for no discernable reason. This could be a machine config
issue, but we haven't found the cause. Not fixed in 2001.1 beta.

Anyone else have any similar experiences? When I report some of these to
Perforce I feel like the only p4Web for Mac user out there.

Thanks!